[Lord_Destros]

Also, the plugin doesn't restore client settings if you do amx_hacker.

[adidas]

verry good plugin nice +++++karma !!!
hmmm zoom fov cheat

[pikachu]

Originally Posted by YamiKaitou Wrong... Can you be certain that you are changing the client cvars back to the values that the client had them originally? Also, you do change the values of the cvars with you use the second command. Also, this will not always work correctly. Code: server_cmd("amx_ban %s",playername) Actually, it never will. You are forgetting the length of the ban. Try this Code: server_cmd("amx_ban ^"%s^" 0",playername)

This plugin has been running as designed on my server for over two years...I c no flaws.

[pikachu]

Originally Posted by Lord_Destros Also, the plugin doesn't restore client settings if you do amx_hacker.

actualy if you run the first command on a previously banned client it will restore the player's settings. but the client has to be unbanned first and return to your server. I forgot to mention that the plugin does unbind all settings of the player before banning if using the amx_hacker command.

[Lord_Destros]

Originally Posted by pikachu actualy if you run the first command on a previously banned client it will restore the player's settings. but the client has to be unbanned first and return to your server. I forgot to mention that the plugin does unbind all settings of the player before banning if using the amx_hacker command.

And that is a slowhack, hence the plugin probably won't be approved if those settings are left on.

[YamiKaitou]

Originally Posted by pikachu This plugin has been running as designed on my server for over two years...I c no flaws.

The command amx_ban requires at least 2 parameters. The client's name and the ban length. I tested the amx_ban command before I made my post. I tested it on 1.76d, everytime I didn't specify the length, it gave me the usage for it. It may be working for you if clients have a space or something in their name. So, if there is a space, the space seperates the args, resulting in you sending part of the client's name in as the ban length and/or reason.

actualy if you run the first command on a previously banned client it will restore the player's settings. but the client has to be unbanned first and return to your server. I forgot to mention that the plugin does unbind all settings of the player before banning if using the amx_hacker command.

And that would be against the rules of posting plugins here

[Bugsy]

I just went to test it out and after using an amx_scan command and then an amx_hacker command (both on myself) I was unable to control my player. It said it found a hack on me that is obviously false.

I then disabled the plugin (and changed maps) and tried restarting CS to get my settings back but it didn't work. I finally re-enabled the plugin and did an amx_scan on myself and let it fully complete and then I had my commands back. (By commands I am referring to cl_forwardspeed, cl_backspeed etc.)

You should add a section to public_disconnect to reset all of the players cvars back to the default value just incase the player disconnects during a scan. This way if a player disconnects while in a scan, the plugin can put the values back to normal.

[YamiKaitou]

Originally Posted by Bugsy You should add a section to public_disconnect to reset all of the players cvars back to the default value just incase the player disconnects during a scan. This way if a player disconnects while in a scan, the plugin can put the values back to normal.

Can't do it with the function client_disconnect. Reason being is because once that function is called, the client has already left

[vvg125]

Yea... unless the client configuration part is removed, this plugin has 0 chance of approval.

[Hawk552]

The method is totally unacceptable.

Unapproved.