Hadradavus
Somewhat Threatening Sniper
Name 0Exn
Summary Racist weapon name + potential aim assist
SteamID
[U:1:1563879029]
https://steamcommunity.com/profiles/[U:1:1563879029]
https://stats.skial.com/#summary/player/SteamID/All/[U:1:1563879029]
https://www.skial.com/sourcebans/index.php?p=banlist&advType=steamid&advSearch=[U:1:1563879029]
https://www.skial.com/sourcebans/index.php?p=commslist&advType=steamid&advSearch=[U:1:1563879029]
When did this happen? Just Now
Which server did this happen on? 2FORT NY
Any other information
Originally I was filing this report for a simple racist weapon name, which was applied while they were in the server. The weapon, however, seemed to have been restored immediately after, as upon checking their inventory, a weapon with the offending name wasn't present, although there was one message in the chat commenting on it. Evidence image here. (not using a proper embed/link since I'm too lazy to figure it out lol). Feel free to disregard this bit unless the brazen act alone is deemed worth deploying the hammer.
However, upon spectating them to see if they kept the weapon name, I found their aim looked to be very suspect. Upon extended observation, it appears that pretty much every shot has a very robotic series of snaps/micro-flicks doing a lot of heavy lifting. With a prescribed ping of around 70 in the scoreboard and altogether little observed lagginess on their end, I figured it was worth the inclusion. Unless they're the jitteriest aimer on planet Earth and having more lag than I thought, something very suspect is going on there. Demo available here. Noteworthy ticks (keeping within the first few-thousand ticks, which imo are already rich with potential evidence, though it goes on for a total of a little under 19k):
120: engages engineer. Very strange-looking baby flick for a full meatshot.
330: Attacks pyro with pistol. Aim locks to center mass, and hits a precise chain of shots in that clip at a pretty decent range.
~365: Another apparent lock-on to the pyro, followed with super-bouncy track.
680: Engages soldier. Aim slides to where he is by 717, then 750 robotic flick for a meatshot.
1090: Attacks pyro with pistol again. Over aims, then aim adjusts ~1125 with another extremely precise slide to center mass.
~1180: Very peculiar pistol shot; it adjusts left, as if compensating for random spread
1235: Robotically smooth track on pushing engineer
1440: Fights engineer. Hits a glancing shot, followed by some very jittery mouse movements, then at ~1480 has a one-tick wide compensating mouse movement to try and nail a follow-up. The second shot is also a glance, and the engineer survives for the moment.
1600: Finishes off engineer with pistol. Continued very jittery, yet precise aim. By ~1690, he hits an extended-range longshot on the engineer following a series of odd mouse movements to secure a kill.
~2000: Attempts to kill pyro. Very jittery pistol aim adjustments continue, although they're not able to take out the pyro before burning to death.
3900: Engages engineer. Once again, extremely jittery aim continues
4160: Attacks another engineer. Very staccato tracking, which ends with a meatshot at ~4190.
6500: More engineer killing, and more stuttery point-tracking
7400: Anticipates and then kills ambushing engineer. Once again, jittery flick to body to secure kill
7770: Ambushes engineer. Hits shot at around 7790, with many small jitters.
11700: Engages (you guessed it) an engineer. Jittery back-to-back solid hits continue
12120: Kills engi with a shot, then a flick to them, then a flick back to where they were aiming before, in a very short span of time.
The remainder of the demo has several more kills that generally fit the bill of "robotic-looking flicks into double meatshots" in the last few thousand ticks, hence why I front-loaded the extended fight with annotations, as well as it having most of their pistol usage. I'm willing to be proven wrong, but it seemed very off to me altogether.
Summary Racist weapon name + potential aim assist
SteamID
[U:1:1563879029]
https://steamcommunity.com/profiles/[U:1:1563879029]
https://stats.skial.com/#summary/player/SteamID/All/[U:1:1563879029]
https://www.skial.com/sourcebans/index.php?p=banlist&advType=steamid&advSearch=[U:1:1563879029]
https://www.skial.com/sourcebans/index.php?p=commslist&advType=steamid&advSearch=[U:1:1563879029]
When did this happen? Just Now
Which server did this happen on? 2FORT NY
Any other information
Originally I was filing this report for a simple racist weapon name, which was applied while they were in the server. The weapon, however, seemed to have been restored immediately after, as upon checking their inventory, a weapon with the offending name wasn't present, although there was one message in the chat commenting on it. Evidence image here. (not using a proper embed/link since I'm too lazy to figure it out lol). Feel free to disregard this bit unless the brazen act alone is deemed worth deploying the hammer.
However, upon spectating them to see if they kept the weapon name, I found their aim looked to be very suspect. Upon extended observation, it appears that pretty much every shot has a very robotic series of snaps/micro-flicks doing a lot of heavy lifting. With a prescribed ping of around 70 in the scoreboard and altogether little observed lagginess on their end, I figured it was worth the inclusion. Unless they're the jitteriest aimer on planet Earth and having more lag than I thought, something very suspect is going on there. Demo available here. Noteworthy ticks (keeping within the first few-thousand ticks, which imo are already rich with potential evidence, though it goes on for a total of a little under 19k):
120: engages engineer. Very strange-looking baby flick for a full meatshot.
330: Attacks pyro with pistol. Aim locks to center mass, and hits a precise chain of shots in that clip at a pretty decent range.
~365: Another apparent lock-on to the pyro, followed with super-bouncy track.
680: Engages soldier. Aim slides to where he is by 717, then 750 robotic flick for a meatshot.
1090: Attacks pyro with pistol again. Over aims, then aim adjusts ~1125 with another extremely precise slide to center mass.
~1180: Very peculiar pistol shot; it adjusts left, as if compensating for random spread
1235: Robotically smooth track on pushing engineer
1440: Fights engineer. Hits a glancing shot, followed by some very jittery mouse movements, then at ~1480 has a one-tick wide compensating mouse movement to try and nail a follow-up. The second shot is also a glance, and the engineer survives for the moment.
1600: Finishes off engineer with pistol. Continued very jittery, yet precise aim. By ~1690, he hits an extended-range longshot on the engineer following a series of odd mouse movements to secure a kill.
~2000: Attempts to kill pyro. Very jittery pistol aim adjustments continue, although they're not able to take out the pyro before burning to death.
3900: Engages engineer. Once again, extremely jittery aim continues
4160: Attacks another engineer. Very staccato tracking, which ends with a meatshot at ~4190.
6500: More engineer killing, and more stuttery point-tracking
7400: Anticipates and then kills ambushing engineer. Once again, jittery flick to body to secure kill
7770: Ambushes engineer. Hits shot at around 7790, with many small jitters.
11700: Engages (you guessed it) an engineer. Jittery back-to-back solid hits continue
12120: Kills engi with a shot, then a flick to them, then a flick back to where they were aiming before, in a very short span of time.
The remainder of the demo has several more kills that generally fit the bill of "robotic-looking flicks into double meatshots" in the last few thousand ticks, hence why I front-loaded the extended fight with annotations, as well as it having most of their pistol usage. I'm willing to be proven wrong, but it seemed very off to me altogether.
