Welcome to The Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads

How To Catch A Bhop Scripter Using Macrodox.


DIAMELO
 Share

Recommended Posts

Other Guides/Rules:

Main Admin Training Guide

Jailbreak Admin Guide

Jailbreak Bible

How to catch a hacker

Guide on what NOT to do

HLDJ/Mic Rules

Rules for Racism

Guide on getting proof for bans

Guide To Make A Ban/T-List Report

 

WAIT FIRST OFF THE COMMAND IS: "mdx_stats playersname" or "mdx_stats @all" in console.

 

First you need to know whats the best legit stats you can get for 66 tick and 100 tick (depending on their fps) - If you dont know what fps_max is go look at it on the bhop thread.

66 tick-30-34 FPS = 40-60% sync if they're just starting and not very good at bhop and timing, but for someone like me, shortkid or OTHERS(idk) is 60-90%, and for 300 fps and other such its hard to even get 60% but its pretty possible with experienced players.

100 tick = 300 FPS = 50-75% sync is the best people can do, 49-54 FPS = 70-90% is the best.

 

Some of our CSS servers now have a new plugin for checking players fps, simply type "get_fps_max playersname" in console to see someones fps.

 

Now after you know what's the common sync(perfect jumps) for both of the ticks, now its on to seeing macrodox stats that are legit and what a scripter one looks like.

 

BUT FIRST! Lets go over what the different parts of an mdx log mean...

 

 

So here is your basic in game log you get from using the above commands ("mdx_stats playersname" or "mdx_stats @all"):

 

 

RANDOM PLAYER NAME HERE <117><STEAM_0:0:46843391><> Avg: 6.692027/412.148437 Perf: 0.741834 bhop_forest_v1 730.840637 2223.033203 1.031250 Last: 8 4 3 10 9 6 9 6 7 7 9 9 5 7 6 7 5 9 6 4 5 7 8 5 6 6 7 5 6 5

 

RANDOM PLAYER NAME HERE <117><STEAM_0:0:46843391>

First piece of info in the log is of course the players info (ingame name and steamID)

 

<> Avg: 6.692027/412.148437

Next up is Avg (or average), what this shows is <Average: Jumps/Speed>, so from this log we see this player was getting an average of 6 jumps per hop (in other words when the player scrolled his mouse wheel did 6 scrolls from the time he got off the ground until he landed) and had an average speed of 412 velocity.

 

Perf: 0.741834

Now its on to Perf: (or perfect), which shows a players perfect jump ratio. The way this pretty much works is Perf: 1.0000 = 100% perfect jump ratio (virtually impossible to get), or as we see in this log Perf: 0.741834 = 74% perfect jump ratio.

Perf: 0.9440369 would be 94% perfect, Perf: 0.875430 is 87% perfect, Perf: 0.120390 is 12% perfect, and so on and so on. The perf jump ratio is determined by mdx using the last 15 jumps a player does while bhopping and just tells us how many of those jumps were timed perfectly. This is pretty much one of the first things we look at when determining if someone is scripting because a script is made to always time the jumps perfectly 100% of the time.

 

bhop_forest_v1 730.840637 2223.033203 1.031250

This stuff you don't really have to worry about, all it shows is what map this log was pulled on and the numbers after the map name are the map cords (shows where exactly the player was on the map when the command was used)

 

Last: 8 4 3 10 9 6 9 6 7 7 9 9 5 7 6 7 5 9 6 4 5 7 8 5 6 6 7 5 6 5

Final piece of a log is Last: which shows the jump or scroll pattern of the player. Pretty straight forward, shows how many scrolls the player gets every time he or she jumps.

 

 

 

1. Basic/common Scripter

 

This is a script:

Yoloswag<46><STEAM_0:1:26188236><> Avg: 1.362531/439.909759 Perf: 0.903099 bhop_mist_4 -1485.163085 796.353393 -539.000000 Last: 1 2 1

1 2 4 1 1 2 1 2 1 1 1 1 1 2 1 1 1 1 1 1 1 1 1 2 2 1 1

 

Pretty much if you see someone getting 1-2 scrolls every jump, it basically means they're using spacebar, in no way is it possible to get 1 scroll per jump and manage to achieve such a high Perf, that's basically what a common script looks like.

 

Just as a side note when you mdx_stats someone in game and all you see is 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 in their log DO NOT BAN UNTIL YOU ARE SURE THAT THE REST OF THE INFO IN THE LOG CONFIRMS SCRIPTS!!!!

 

This is not a script:

0 random person <1168><STEAM_0:1:0123456789><> Avg: 1.008559/129.790130 Perf: 0.000598 cs_crackhouse 10344.063476 -787.099548 96.031250 Last: 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1

 

Looking at this log we all see the obvious long line of 1s at the end, BUT THATS NOT ALL WE LOOK AT FOR SCRIPTERS. Before you choose to ban or post a report make sure you look at the rest of the log. When it comes to nothing but 1s the perf has to be at least 50+% perfect. If you still can't understand how Perf: works then check to make sure that their average speed is at least higher than 270 velocity.

 

This is a script:

0 random person <1168><STEAM_0:1:0123456789><> Avg: 1.079559/346.786120 Perf: 0.694998 cs_crackhouse 10344.063476 -787.099548 96.031250 Last: 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1

 

Now here we have another mdx log that looks pretty similar at a quick glance, but if you actually take your time and look at the key parts of the log you can see that this was actually a scripter. All 1s and perf is close to 70% perfect with an average speed of 346 velocity (speed is a key part in this you want to make sure the player is actually moving and is not just stuck in the ground). Make sure you check the player's stats more than once but give some time between checks to make sure that there is some changes in the stats.

 

You could also just take the easy way and ask me, shortkid, or any advisor really.

 

 

THIS IS SOMEONE WHO JUST JOINED THE SERVER AND HASN'T EVEN STARTED MOVING:

0 hg | diamelo [a]<1202><STEAM_0:1:17365275><> Avg: 5.000000/250.000000 Perf: 0.333299 cs_crackhouse 10479.033203 982.968750 64.949783 Last: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

 

I'm also going to add this in too, when you enter a server and see logs like this it just mean the player hasn't actually started to jump or even move.

 

 

 

2. Hyperscrollers/Macros

 

First off here's what a really fast macro would look like.

0 MrFlysome<153><STEAM_0:1:49058787><> Avg: 34.184318/237.838088 Perf: 0.348786 bhop_monster_jam 5911.254394 -3586.626464 3780.766601 Last: 15 37 36 33 37 36 41 37 41 16 37 37 37 36 8 40 36 37 42 36 9 22 23 37 16 44 39 37 37 44

 

In general what a macro does when its used to bhop is spam "space". Macros can be made to spam "space" pretty fast, giving us the result of multiple jumps well into the 20-30 range in scrolls per hop, like we see in the example above.

 

Now a hyperscroll is when the player has a mouse that has a built in feature to sort of "unlock" the mouse wheel allowing it to spin freely with little friction, usually hyperscrolls and macros will look about the same when used on our servers so you really don't have to bother with determining what the player is using.

 

Here is an example log that suggest the player is most likely using a hyper scroll

 

0 MrFlysome<153><STEAM_0:1:49058787><> Avg: 22.864912/237.838088 Perf: 0.348786 bhop_monster_jam 5911.254394 -3586.626464 3780.766601 Last: 15 20 23 22 25 21 31 27 31 16 24 17 21 23 8 30 26 25 22 28 9 20 23 17 16 24 29 27 27 34

 

You can see that the jumps we're seeing are about 10 scrolls less, this is typically what you will see on our servers. When you see someone in game with scrolls within the range of 17-25+, constantly while bhopping, it is very safe to assume that that player is using a hyper scroll or macro. Which ever it is does not really matter at this point because like I said on our servers (talking about DM servers here) you won't really see much of a difference between the two.

Remember proper procedure for this is warn/kick/ban.

 

 

 

 

3. MDX Bypassers

 

Onto the fun part (confusing part), of spotting people that use hacks that bypass macrodox, usually these are not detectable but there is some where they think hitting a 10-20% increase in sync wont get them caught, they are wrong, now its hard to get stats and explain exactly why its a script, so we would like if you could just report anyone that you think might have bullshit stats to me, shortkid or any CSS advisor.

 

Heres a mdx stats from a hacker that bypassed mdx with 300 fps

0 catapult<122><STEAM_0:1:5327214><> Avg: 3.782154/528.870666 Perf: 0.920077 bhop_darkness -1524.804077 4164.516601 86.517425 Last: 2 2 3 5 5 2 3 3 4 7 3 3 4 3 7 6 4 4 5 3 3 2 4 4 6 2 4 4 4 4

 

Now, just to explain it, they bypass macrodox by sending "legit jumps" and "fake scrolls" so basically they hold down space, and usually the hack (if setup properly) will give you a 10-20% sync increase over legit, making you seem really good at timing but usually its easily detectable because if you saw this guy get 80-90% sync every time on 300, that's a ban because it just isn't possible. FPS plays a big role in spotting someone with a mdx by-passer, once you under stand which FPS is used with each tick then it gets easier.

 

Like it was explained at the top of this thread, different ticks have different FPS settings that can be used to improve timing.

Each FPS has its own range of possible Perf.

33-tick = nothing really, bhop is pretty hard on this tick no matter what fps you use.

 

66-tick = fps_max 30.95 / 31 / 34 / 34.1 <<<<<< These first 4 are usually used to improve timing and can get a good bhopper any where from 50% perf to 80+% perf.

300 FPS << With this fps on 66 tick you will hardly ever see anything over 60% perf (if you ever see anyone constantly get way over that with 300 then that is someone you want to keep an eye out for).

 

100-tick = fps_max 49.245 / 53.9398177 / 54 <<<< These first 3 are whats used to improve timing in 100tick servers and can get a good bhopper anywhere from 50% perf to 90+% perf.

300 / 0 / 9999999999999 <<<< These are used mostly by casual bhoppers or some "pros". Perf on either of these fps settings will very rarely reach 70% perf when used by a legit player. (note: fps_max 0 just unlocks your fps so there is no cap, just like using 99999999)

 

200-tick = fps_max 300 / 0 / 99999999999 <<< This tick you don't have to worry about in HG servers since we currently don't host a server with a tick this high.

 

Ok once you got all that fps - tick stuff down then it'll be a bit easier to determine who is cheating and who isn't.

Don't forget to use the get fps command when trying to check a player for by-pass scripts. "get_fps_max playersname"

In addition to getting a players fps and mdx logs, when ever it comes down to someone possible using one of these scripts we ask that you also submit a demo, just like the demos we ask for other hackers it needs to be in their first person view.

 

 

 

 

 

 

 

 

Ok so here we're going to look at some logs along with their fps info, one will be a lot more obvious than the other..

 

 

 

 

random guy<83><STEAM_0:0:12345678><> Avg: 2.014602/348.354553 Perf: 0.948784 mg_awp_submarine_v2 9104.972656 1072.932495 -1194.774902 Last: 1 3 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 1 3 2 1 3 2 2 1 3

random guy's (STEAM_0:0:12345678) fps_max is 999

 

Alright so seeing that this log was pulled from the mg server we know that the tick rate is 66 and the player was achieving over 90% perf with an average jump pattern of 2 and average speed of 348 velocity. Looking at this info alone without the fps it is already pretty obvious that this guy is scripting because if you have a mouse wheel that is this bad where if you scroll it only sends 2 scrolls per jump you would know that this is just as impossible to time as using just your spacebar. This log pretty much shows how a simple by passer works, it just has to send a random jump pattern greater than 1 to get by mdx.

 

 

So this is where I would advise everyone to speak to someone with a lot of mdx/bhop knowledge before taking any action against someone.

 

By-pass script:

another random guy<3><STEAM_0:0:12345678><> Avg: 5.872811/871.279876 Perf: 0.942433 bhop_badges -5420.829101 15000.332031 1376.031250 Last: 6 6 5 5 5 5 6 6 7 6 7 6 6 5 6 6 6 5 7 5 6 7 6 6 5 5 6 6 5 6

another random guy's (STEAM_0:0:12345678) fps_max is 300

 

You can see this log was from someone using a by-passer, we can determine this by looking at the player's fps_max. Impossible for someone on 100tic with 300 fps to reach a constant 94% perf.

 

Of course you could say "oh maybe this guy isn't even reaching 300 fps and is only getting like 60 or 100 fps so his perf could come from that!" well this isn't possible. When your fps is this unstable that your pc can not keep a solid 300 fps and is just jumping around all over the place it only makes timing much much harder.

 

Legit bhopper:

different random guy<86><STEAM_0:1:123456789><> Avg: 5.638675/1003.413757 Perf: 0.952509 bhop_arcane_v1 1475.742553 357.770935 14400.031250 Last: 6 6 3 6 4 6 5 6 6 6 6 5 5 5 6 4 5 5 6 5 7 5 6 7 6 6 6 5 7 5

different random guy's (STEAM_0:1:123456789) fps_max is 49

 

Now looking at this log it looks very similar to the first one but what makes this one legit is the fps_max the player is using.

 

Looking at logs like this where the player is reaching 80-90+% perf is when it is absolutely important that you find what fps the player is using, on any server.

 

 

In the end do not hesitate to ask us about any suspicious logs or players.

 

 

 

 

 

**Original by Aimer.**

  • Like 10
Link to comment
Share on other sites

  • 3 months later...

I know I'm being annoying and replying to an old topic again, but I wanted to ask a few things.

 

Firstly, thanks for this, I'll be sure to keep this in mind if I ever think I see a scripter.

 

Now the questions. As you might know, I've only been playing on the minigames server lately.

 

So:

 

1. What do things like boosters [trigger_push] do to this? I would assume you'd be getting screwy reports, like another random guy<3><STEAM_0:0:12345678><> Avg: 2.872811/1537.279876 Perf: [is this what would make you tell? The ratio of perfect jumps?]0.942433 mg_YOLO_multigames -5420.829101 15000.332031 1376.031250 Last: 4 3 5 5 5 5 6 6 7 6 7 6 6 5 6 6 6 5 7 5 6 7 6 6 5 5 6 6 5 6

another random guy's (STEAM_0:0:12345678) fps_max is 300

 

2. What about low gravity? It's much easier to get perfect, or maybe not perfect but to gain speed when jumping with low gravity. Woudn't that look something like another random guy<3><STEAM_0:0:12345678><> Avg: 3.872811/1239.279876 Perf: [i still didn't change this, I don't know what low gravity would do to it.]0.942433 mg_lt_galaxy_v5 -5420.829101 15000.332031 1376.031250 Last: 6 6 5 5 5 5 6 6 7 6 7 6 6 5 6 6 6 5 7 5 6 7 6 6 5 5 6 6 5 6

another random guy's (STEAM_0:0:12345678) fps_max is 300

 

3. What about iceskate? another random guy<3><STEAM_0:0:12345678><> Avg: 1.000000/1523.279876 Perf: [?]0.942433 mg_all_in_one_velocity_v1 -5420.829101 15000.332031 1376.031250 Last: [?]6 6 5 5 5 5 6 6 7 6 7 6 6 5 6 6 6 5 7 5 6 7 6 6 5 5 6 6 5 6

another random guy's (STEAM_0:0:12345678) fps_max is 300

 

While these may be easily check-able by paying attention to what multigame is being played, how much could these screw up the stats and confuse a watcher? Are the averages taken from the entire session, or from a certain time ago? What about the perf percentages?

Link to comment
Share on other sites

trigger push and lowgrav don't mess with perf as its how well you timed the jump. Those guys were cheating FYI.

 

Lol, thanks for the quick response, but I had to laugh because I just copied and pasted those stat thingies from the OP and changed the numbers. [Or did you already know that and you meant that if I saw those stats the people with them would be cheating?]

Link to comment
Share on other sites

Lol, thanks for the quick response, but I had to laugh because I just copied and pasted those stat thingies from the OP and changed the numbers. [Or did you already know that and you meant that if I saw those stats the people with them would be cheating?]

 

ahh didn't see that those were from op, if you see those kinda stats from someone on 300 fps something fishy is going on.

Link to comment
Share on other sites

  • 1 month later...
  • 3 months later...
  • 3 years later...
  • 11 months later...
Guest
This topic is now closed to further replies.
 Share