[Black Rose]

Code is not random. Bugs don't just occur. They always have a cause.
After I fixed those two errors I found I haven't found anything else and I also haven't been able to create any bug.

[maqi]

Woops Thanks for that one. That solves one problem.

Theres still that random occurrence ( which is not random ), but im not able to recreate it at this point either.

[Black Rose]

If you really want to get to the bottom of it, add a lot of server_print() or amx_log(), printing all the variables.
That way, you can retrace the steps of that bug to the origin.

But if the plugin does nothing and the original message is showing then you most likely have an error in the log because your plugin halted before completing the function.

[maqi]

Thank you so much for everything, you helped a lot. Thanks for fixing a couple of my oversights i wasnt able to see

One last question while we are at logs, would it be too much to log every message, that would really be usefull ?

[Black Rose]

Depends on what you mean. I wouldn't log it permanently but if it's for debugging purposes and you intend to delete the logs whenever you're done with the debugging it's completely fine.

Do it for a while and see how much space it will take up. That's all you have to worry about. CPU/RAM is hardly the bottleneck in a chat logging situation. The hard drive is much slower.

[maqi]

Then better no We have a lot of chat messages going on And i meant permanently not for debugging.

Thanks once again. All the best

[edon1337]

Originally Posted by maqi I dont get if you are saying i shouldnt or that it wont work. Because that part is working perfectly

Take a look at this thread.

[siriusmd99]

Originally Posted by maqi I agree with you, but i fixed that mistake. My question is why is the say message ever happening if my plugin is essentially this: PHP Code: public plugin_init()      register_clcmd( "say", "SayRegistered" ); public SayRegistered(id)     return PLUGIN_HANDLED

Maybe you have a plugin like all chat or something like this that sends a message artificially and then returns handled.
Solution is to put it above all plugins in plugins.ini and see what happens.