[SchlumPF*]

suggestions:
-add a file to configure the plugin (a lot amxx users cant edit even simple things in plugins)
-rather check on nick-change and connect whether the users nick is forbidden to make this plugin even saver

[M1R0n,M']

Originally Posted by SchlumPF* suggestions: -rather check on nick-change and connect whether the users nick is forbidden to make this plugin even saver

Updated to 1.1v , im make this suggestions.

[SchlumPF*]

you should stick to one stile of naming vars, different stiles look like copying code ^^
set_task(1.0, "Event_NewRound", id) -> Event_NewRound(), read hawks tutoriala bout tasks

[1337]

good but u should make txt file to take blocked nicks there

[deejayu]

Originally Posted by 1337 good but u should make txt file to take blocked nicks there

yEahp i agreeh.

[M1R0n,M']

Originally Posted by SchlumPF* you should stick to one stile of naming vars, different stiles look like copying code ^^ set_task(1.0, "Event_NewRound", id) -> Event_NewRound(), read hawks tutoriala bout tasks

Updated.

[grimvh2]

doesnt this already exists?

[M1R0n,M']

Originally Posted by grimvh2 doesnt this already exists?

Dunno, I searched but failed to find one.

[grimvh2]

Originally Posted by M1R0n,M' Dunno, I searched but failed to find one.

I tought it does, but i cant find it also so Gj then ;)

[fysiks]

There is no reason to run the check on a new round and client_infochanged(). They have to change their info to get to a new name anyways.