When you run the plugin, its executes/run/works/do things, you need to know how it is doings things, what function is called before what, why it is being called, and why it is not being called. To do that, to accomplish that, to put a lot of server_prints, and put more server_prints, until you get to know all information that do you need to understand what the plugin is doing, when you are using it, this is called debug. See
[TUT] How to use an efficient debug system, which do not overload your final code, but it use, what I could call 'advanced concepts'. However, on the thread beginning and contents, you can find various others tutorials and links to understand things.
You cannot forget also to read the
Amx Mod X documentation, to get to know what your functions do, and why they do. And
the tutorials to know more about how things get done. But if some documentation is missing or you do not understand,
search, search, search, search, the forums, until you find some thing as example or a plugin which uses that function where you maybe can know what is does when you see what plugin code running.
Also, when you get a plugin and modifies it, do not remove thing on the fly unless you
are sure they are
useless. And to know if they are useless,
to debug the code, to read the
Amx Mod X documentation, to read
the tutorials and
search, search, search, search.
__________________