03.07.2015, 15:10
You can never actually traverse into the memory space of another AMX, at least not for executing code. You could make functions to (almost) directly read variables there, but that's about it.
If you find a way to run the bytecode of a function from another AMX, references to variables and such will get completely mixed up and further calls to other functions will result in access violations.
If you find a way to run the bytecode of a function from another AMX, references to variables and such will get completely mixed up and further calls to other functions will result in access violations.