[iggy1]

Quote:

Originally Posted by Kyosaur AmxLoad(AMX*): This is called when a new AMX instance is loaded into the server. This will be called for every filterscript/gamemode! Because of this it isn't a good idea to store a single AMX instance for the entire plugin, instead use a queue/list/vector. In this function we also register our custom native functions we wish to provide PAWN with

Could someone tell me why this needs to be done please? (storing instances of amx) A small example or explanation would be great if possible? Is that just for calling publics in an amx file, Or must it always be done regardless if your calling publics from the plugin or not?

I have had a look in other plugins but still not sure if or why i need to use this.

Thanks in advance.

EDIT: I know i need to use AmxLoad(AMX*) to register the natives to the amx, just wondering why i would need to store the amx in a container.

EDIT2: I think i get it now, if an amx is unloaded most data that it pointed to, in the plugin becomes redundant. Going to have to re-download the documentation.