[Toster v2.1]

Description:
If you own a bhop server you probably already have one of Exolent's plugins to stop bhop scripts. Sadly over time the top15 still gets full of players with clan tags like "[t3h-scripter]" etc who are most likely using cheats to bhop. This plugin will stop most of them.

How auto-bhop cheats work:
The ones I'm familiar with wait for the user to press the jump key (or +jump in the console) to enable bhopping. After that they check each frame if the user is on the ground and if he is they make the player jump. When the user releases the jump button (-jump) auto-bhopping is disabled so he can move around freely again.

What the plugin does:
After the server receives a client's command to jump it executes the -jump command on the client repeatedly until he hits the ground thus disabling most auto-bhop cheats before he jumps off the ground for the second time. (One -jump would be sufficient to stop the cheat but the user could easily shortly release the jump key and press it again to re-enable it. Also sending it just before the user hits the ground would be too late in most cases if the ping is high enough. To avoid this -jump is sent each frame from the moment the player jumps until he hits the ground)

What the plugin does not do:
It does not stop halflife/cs bhop scripts since they just send the jump command repeatedly. Use Exolent's plugin to detect those.
It does not stop any general purpose scripts/applications that simply hit the space bar on OS level. (Most of those don't work too well anyway)

Possible issues:
If your game server modification/plugin needs the user to hold the jump button in mid-air for some functionality, it will not work.

[eD.]

Nice, good job.

[Toster v2.1]

4 days without comments.. Is this a bad sign? Maybe I should change the title to sth like "The Ultimate BHop-Cheat Disabler" to attract some attention?

Anyone tasted it in an actual server? Does this method cause lags/higher latency of any sort? Any bugs? (Currently I've only tested this in LAN with some friends, works great against BunnyFlop, FighterFX etc. Does not seem to cause any problems while bhopping normally.)

Any feedback would be appreciated

[grimvh2]

When no1 reply's it means it isnt bad or ridiculouse but its also not spectecular :p
Ill take a look at the code.
Not much code. Why is this version better then exolent's version?

[ConnorMcLeod]

IMO using client_cmd is a poor way, but if it works...

Also, why are you hooking postthink rather than prethink, and why don't you use engine forwards instead or registering FM ones ?

[Toster v2.1]

Finally some replies

@grimvh2: Read the description.. It doesn't stop scripts (that's what Exolent's plugins do) (scripts as in.. a couple of lines of text in client's config file), it stops cheats (as in those applications which inject a dll in the cs client or patch the memory).

@ConnorMcLeod: Yeah, I don't like using client_cmd either, but it's the best way I could think of.
Using postthink because if I were to use prethink it would detect that the user is still on ground as soon as he jumps and -jump wouldn't be sent at all.
Not sure why using FM. As far as I can remember most scripters said it was better in most cases for some reason. Should I use engine?

[grimvh2]

Originally Posted by Toster v2.1 Finally some replies @grimvh2: Read the description.. It doesn't stop scripts (that's what Exolent's plugins do) (scripts as in.. a couple of lines of text in client's config file), it stops cheats (as in those applications which inject a dll in the cs client or patch the memory).

I see.

[Bello]

wow In truth that if it works i tasted with a friend who has the script...

Toster You can make a plugin for blocked commands the cheat low recoil?

like this :

"alias +antirclbind "+attack; +lookdown;"
alias -antirclbind "-attack; -lookdown;"" .
We also have " cl_pitchspeed 5"

this: bind "mouse1" "+attack;moveleft;moveright;up;down;"

You can create a plugin for blocked these binds?

[Toster v2.1]

I can, but it doesn't mean I will. Stopping those involve slowhacking. Unlike this plugin it would require to change client's settings.

[ConnorMcLeod]

All you have to do is to detect the change of cl_pitchspeed client value, then kick him.