[NouveauJoueur]

By installing plugins and start cheating with it.

[Xp3r7]

Yea, I dont get how people are doing this with SM, Mani, ES, etc either.

Ive always had a copy of Mani or SM on my local machine for LANs and Ive never cheated at any game ever!

Valve just released an update to CSS today so maybe this whole "using server side plugins" bug will be fixed in the next update across the board.

[NouveauJoueur]

It's not a bug, it's a feature ...
You can run plugins client side, means you can run cheat plugins client side too ... So checking if someone is running any plugins means reduct the number of cheats and exploit on your server, if you want ppl to keep cheating, just disable this feature by editing the sourcecode, cause it's not a bug and wont be fixed by VAC.

Kigen said that those cheats wont be VAC banned cause it's valve fault if those cheats plugin can run client side.

[nbtc971]

Should we remove crash_prevent_b1.smx to use this?

[FuhrerMike]

Originally Posted by Xp3r7 Yea, I dont get how people are doing this with SM, Mani, ES, etc either. Ive always had a copy of Mani or SM on my local machine for LANs and Ive never cheated at any game ever! Valve just released an update to CSS today so maybe this whole "using server side plugins" bug will be fixed in the next update across the board.

Exactly this, some of us actually OWN large servers and like to test things on a local machine before using them. Moving away from the ignorant responses, is there a portion of this plugin that I can disable checking for SM?

[retsam]

Why not just disable the plugin altogether if youre using it on a "test" server?

Anyways, its public Action:CheckPlayer(Handle:timer,any:value) and public ConVarDone(QueryCookie:cookie, client, ConVarQueryResult:result, const String:cvarName[], const String:cvarValue[], any:value)

stuff I believe youd have to comment out...

[Jamster]

I don't mean to be a HUGE dick but from a technical standpoint it's usually best to test your stuff on local dedicated servers rather than local listen servers. SM and other stuff can be weird setup on non-dedicated servers. I can understand why the feature is present in the plugin to be honest from a cheating vector point of view.

[FuhrerMike]

Originally Posted by retsam Why not just disable the plugin altogether if youre using it on a "test" server? Anyways, its public Action:CheckPlayer(Handle:timer,any:value) and public ConVarDone(QueryCookie:cookie, client, ConVarQueryResult:result, const String:cvarName[], const String:cvarValue[], any:value) stuff I believe youd have to comment out...

Because then I would have to enable it each time I wanted to test something, thanks for your help though.

I don't mean to be a HUGE dick but from a technical standpoint it's usually best to test your stuff on local dedicated servers rather than local listen servers. SM and other stuff can be weird setup on non-dedicated servers. I can understand why the feature is present in the plugin to be honest from a cheating vector point of view.

I have yet to encounter any problems, but I do understand the feature, I simply wish to disable it.

[Xp3r7]

I use this on a few servers but I have yet to see it kick an "unnamed" player.

A bug maybe?

[gH0sTy]

Originally Posted by FuhrerMike Exactly this, some of us actually OWN large servers and like to test things on a local machine before using them. Moving away from the ignorant responses, is there a portion of this plugin that I can disable checking for SM?

In

PHP Code:

/*
************************** CLIENT PLUGINS ********************************
*/ 


replace

PHP Code:

CreateTimer(5.0, CheckPlayer, client, TIMER_REPEAT); 


with

PHP Code:

//CreateTimer(5.0, CheckPlayer, client, TIMER_REPEAT);