Advertisement
Guest User

No Heroes protects cheaters

a guest
Jul 27th, 2018
5,763
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 6.73 KB | None | 0 0
  1. oh you guys have got to be kidding me...
  2.  
  3. [QUOTE="Savage, post: 192085, member: 1"]I'm not see the "snapping" behavior here.
  4.  
  5. I should also note that our anti-cheat mod is particularly good at detecting that type of thing (unnatural movement of the aimpoint is one of the easiest things to detect), and throws off warnings in the logs if it even suspects a player's aim is snapping abnormally between targets (to avoid false-positives, our system waits for multiple detections before issuing a perma-ban).
  6.  
  7. I just ran 30 days worth of anti-cheat logs, and his Steam ID did not show up once.
  8.  
  9. Looking at the verifiable info we do have, which includes:
  10.  
  11. 251+ days of playtime on our servers without a cheat detected (by us or VAC)
  12. A 10+ year old Steam account (I've found in 10+ years of hosting TF2, old, established Steam accounts are rarely put at risk of a VAC ban)
  13. Statistics that are not outside of the norm in any way
  14. I don't see much more here than a skilled player.
  15.  
  16. I'll let other admins chime in once they take a look at the videos, but as stated previously, we always err on the side of caution, as most of these types of claims are born more out of frustration than actual cheating.[/QUOTE]
  17.  
  18. I'm going to pick apart this specific section right here
  19.  
  20. [QUOTE="Savage, post: 192085, member: 1"]I should also note that our anti-cheat mod is particularly good at detecting that type of thing (unnatural movement of the aimpoint is one of the easiest things to detect), and throws off warnings in the logs if it even suspects a player's aim is snapping abnormally between targets (to avoid false-positives, our system waits for multiple detections before issuing a perma-ban).[/QUOTE]
  21.  
  22. I'm just going to assume the anti-cheat plugin you use is SMAC or based on it. Now their's a HUGE problem with saying that SMAC is 100% reliable at catching aimbots, IT is reliable at catching the people that have aimbots that are set for 180degrees BUT it detection point or where it first starts to look is at 45 degrees as of 2011 ( https://forums.alliedmods.net/showpost.php?p=1475747&postcount=20 ) ("Right now only snaps over 45° are counted as a detection. Is this what you mean?" - SMAC Programmer) Basically what this means is that someone can have a 30fov aimbot and rarely if ever trigger the aimbot detection let alone trying to pickup the detection of a 5 fov or less aimbot. On the other hand the angle has to be that big (45 degrees) otherwise any player that drops a packet or 2 is basically screwed in terms of detection.
  23.  
  24. Here is a 2nd source from 2014(https://www.github.com/mukunda-/rxg-plugins/blob/master/misc/smac_aimbot.sp )("#define AIM_ANGLE_CHANGE 45.0 // Max angle change that a player should snap")
  25.  
  26. Now lets get into the specifics on whether or not Wizardry is cheating.
  27.  
  28. https://youtu.be/6zRIggEXKrc?t=1m52s
  29.  
  30. Between 1m 52s to 2m 9s there is multiple instances of snapping that are not human. Namely the snap from the medic to they pyro at ~1m 55s there are many many reasons this is suspicious
  31. 1. you have the approximately 8 degree snap
  32. 2. shooting a pyro over a medic
  33. 3. shooting a pyro over a medic YOU ARE ALREADY SHOOTING
  34. (now you might ask yourself why would a cheat do this? their's many reasons and many settings to a lot of aimbots here it could be just because the pyro is closer, it could be the cheater programmed the cheat to favor a specific player OR favor shooting specific classes in a dumb order)
  35.  
  36. Now the part that's really suspicious here between 1m 55s and 1m 56s you see wizardry's aim snap to and from the pyro to a wall (there is a player behind said wall but I believe that part is purely coincidental) that snap is a sign that Wizardry is using silent aim on wizardry's screen he shooting toward the wall BUT on the server side it keeps getting conflicting view angle packets from wizardrys client 1 saying he's shooting toward the wall the other saying he's shooting at the pyro and it alternates causing the weird flicks. You can see these same strange flicks between 2m 8s and 2m 9s again.
  37.  
  38. Now let's get to several other strange time stamps in this video
  39.  
  40. https://youtu.be/6zRIggEXKrc?t=2m20s shooting at pyro, tracks pyro falling down. around 2m 21s snaps to the demo on the tracks rather than shooting the pyro near him? And then snaps right back up to above the bridge that the pyro just fell below... Immediately after snapping to the medic and as soon as the demo comes into a plausible viewangle back to the demo climbing the stairs...
  41.  
  42. 2m 23s to 2m 29s is 100% legitimate gameplay this is how the player normally behaves and looks around
  43.  
  44. 2m 30s suddenly snaps to the pyro, now watch right around 2m 32s (I would recommend slowing the video down to 0.5 speed for this) wizardry is tracking this pyro as they're falling as soon as the pyro would no longer be visible on his screen behind the ramp he starts to flick away BUT the pyro suddenly reappears and he instantly flicks right back to the pyro and then to the engineer.
  45.  
  46. 2m 37s to 2m 59s is legitimate gameplay or his crosshair was already close enough it's indistinguishable
  47.  
  48. 3m 0s the snap to the pyro is not legitimate and the entire snapping behavior around 3m 3s to 3m 6s is 100% silent aim
  49.  
  50. Finally we can say with 100% certainty that it isn't related to Wizardry's connection to the server or anything else cause as seen in his down time i.e. when no enemies are around but he's still looking around He never snaps around. Which can be seen between these timestamps 3m 24s and 3m 34s and to add insult to injury on that the demo is being played at over 200% speed at this point and his aim angle changes slower than it did at 29% speed when snapping to players.
  51.  
  52.  
  53. [QUOTE="Al-Truistic, post: 192086, member: 1041"]I reviewed the demo as well. I didn't see anything that triggered me to double check what I was seeing. In fact toward the end he was doing a lot of blind firing at openings, where no one was even close.[/QUOTE]
  54.  
  55. "In fact toward the end he was doing a lot of blind firing at openings, where no one was even close."
  56.  
  57. Toggle keys exist, people don't have to cheat fulltime to be cheaters.
  58.  
  59.  
  60. -Comanglia
  61. Fresh Meat Prolander Anti-Cheat Admin
  62. HLpugs.tf Anti-Cheat Admin
  63.  
  64. I've also assisted a few different leagues AC teams in the past.
  65.  
  66. // edit
  67.  
  68. Honestly if you guys don't see it you're either willfully ignorant or you're actively protecting a cheater.
  69.  
  70. Willful ignorance is what I'm hoping for here, and I see strong evidence of that in this right here.
  71.  
  72. [QUOTE="Savage, post: 192085, member: 1"]
  73. 251+ days of playtime on our servers without a cheat detected (by us or VAC)
  74. A 10+ year old Steam account (I've found in 10+ years of hosting TF2, old, established Steam accounts are rarely put at risk of a VAC ban)
  75. Statistics that are not outside of the norm in any way
  76. [/QUOTE]
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement