Jump to content

Recommended Posts

20 hours ago, MarkCX said:

35B46979CB78EE7AE7B517A2FDBAF6385F87F05C

I do recall one day that you were in the RDM zone changing your resolution to try to PVP on an obscure size, I can attest that from past experience if you swap your resolution there is a rare chance that while your game is frozen changing resolution there's a small chance that it can read your mouse and keyboard movements and it gives off that internet lag feel where you just keep walking forward until everything catches up. It's possible that this sort of thing happened or this could be resolution related due to how the engine handles when settings are being changed especially the resolution. I remember from personal experience atleast when I first started playing GMod on my older laptop that when I would change my resolution I would continue to click buttons and try to move around and whenever my game would unfreeze and change I would be in an entirely different position due to me lagging away. 

I do remember someone named @Slippery Banana that had also triggered this same exact thing. Maybe we could ask him how he was able to trigger this sort of flag.  

Aside from all this information Rubik has stated and confirmed that this is possible to trigger due to lag, obviously we don't know anything with 100% accuracy and everything has flaws nothing is perfect. I can attest that Ego is one of the dumbest people when it comes to being tech savvy no offense, he doesn't even know that you can copy and paste an image from discord but rather drags the image to his desktop to then repost to "copy paste". 

As for now unless more information gets brought up I will leave this as a +1 for a reduced or full unban

Here is some more information, 

Ego (STEAM_0:0:636762791) was triggered for a TYPE1 Aimbot which resulted in them being manual banned without actual investigation. - 6/23/2025

Slippery Banana (STEAM_0:0:91559600) was triggered for TYPE1 Aimbot which resulted in no ban due to the investigation concluding with no findings. - 4/1/2025

Out of both of these triggers they both have some similarities, in both of the flags it states they were looking at y=270 with the other values being 0. Out of all the other TYPE1 triggers they all show values for each position. In most cases the triggers will show very precise positions due to the fact that they are usually locking onto a player or their vicinity, I don't think players are at y270 even if they are in the RDM Zone. I will also add for Slippery's case he had players nearby him but Ego did not so this seems like some sort of false flag if anything, I don't understand how a soft aim would lock anything if nobody was nearby. Aside from that, my question is how do we assume someone is cheating but not the other with no factual proof? Usually when someone is triggering this sort of flag we can clearly see that they are cheating. 

This information has been left in the staff chat for other staff to investigate themselves since I feel like I shouldn't be exposing the works of Quad0. 
 

Edited by MarkCX
extra added info
15 minutes ago, MarkCX said:

Here is some more information, 

Ego (STEAM_0:0:636762791) was triggered for a TYPE1 Aimbot which resulted in them being manual banned without actual investigation. - 6/23/2025

Slippery Banana (STEAM_0:0:91559600) was triggered for TYPE1 Aimbot which resulted in no ban due to the investigation concluding with no findings. - 4/1/2025

Out of both of these triggers they both have some similarities, in both of the flags it states they were looking at y=270 with the other values being 0. Out of all the other TYPE1 triggers they all show values for each position. In most cases the triggers will show very precise positions due to the fact that they are usually locking onto a player or their vicinity, I don't think players are at y270 even if they are in the RDM Zone. I will also add for Slippery's case he had players nearby him but Ego did not so this seems like some sort of false flag if anything, I don't understand how a soft aim would lock anything if nobody was nearby. Aside from that, my question is how do we assume someone is cheating but not the other with no factual proof? Usually when someone is triggering this sort of flag we can clearly see that they are cheating. 

This information has been left in the staff chat for other staff to investigate themselves since I feel like I shouldn't be exposing the works of Quad0. 
 

So with all this information, my theory is that when the players are lagging and looking up in the air they could be accidentally looking at someone in Kingdom or Admin Land which would trigger this sort of deal. 

14 hours ago, Slippery Banana said:

Ive said this before in Titsrp gen chat and thought I should move it here as some were curious about what happened with me in the previous post. I in fact did trigger the same 'TYPE 1' protocol as I was informed by a staff when I reconnected after a crash. From my experience, it does seem to be some issue with connection/response to the AC software aswell because all I had open was Crosshair X, a well known crosshair program which to my current knowledge is not against rules and also not detectable by any sort of AC as it's just an overlay, like discord overlay etc etc (if it's against the rules, pls inform soo I don't use it again).
 

But from what happened to me, I recall being in the rdm zone and triggered it somehow when my client stuttered then crashed whether it was the same way Ego did or not... I do not know. But still changed my view of 100% accurate considering I triggered it and only had a crosshair software open. Then, I reconnected to see a msg saying I somehow I triggered the protocol from some smod or admin.

 

I have been playing the server since 2021 or 2022, since my appeal to be unbanned which was accepted and never cheated once on this game. Also, you can survey any former veteran raider/player and they probably will all tell you there is no chance I was cheating LOL. I'm terrible. Ps, this does not mean he wasn't cheating(I myself don’t think he was)... but it makes me wonder if myself or others will face the same consequences after playing the server for years. As requested from some players knowing I triggered the protocol, and much love to the community.

2025081.JPG?ex=6891d28c&is=6890810c&hm=aspacer.pngspacer.pngspacer.pngspacer.png

  • Like 2

I'm not going to lie here. The joking shit probably hurt your credibility just a tad but Im also in the opinion that if I believe I didn't do shit wrong I would have probably done the same thing in your situation. (That's not me condoning it. Just me being honest about myself)

 

As Blue mentioned I'm thinking that having time to actually watch for it would be more beneficial rather than hard banning outright in the future. 

 

+1

Update upon further investigation.

What Vbov made a point earlier was how it was a Yaw pitch detect, something similar to spinbot [As 270 would mean he was 'Spinbotting'] And I may have an explanation for this.

When Garrys mod crashes, or incurs a fatal error, or even when the Source Engine dies clientside, what happens to try and recover it [Especially during graphical or major system changes] The game is set to try and retrieve the last player state, and Visually it can often make the player spin Rapidly, in game the player could also erratically spin.
I've seen this before a few months back before I was ever staff, I was talking to a friend who was fucking around with Linux and they were complaining about there laggy game, they tried upping there resolution from 1600x900 to 1920x1080, they begun spinning at mach fuck, and said "oh SHIT" and there gmod crashed.
Now this wouldn't have tripped the Anticheat, as no shooting was detected, thus no tick detect could've been 'checked'
However Ego could've had something similar, game fucks hardcore because he fucked his resolution, His game tries restoring last player state, via Spinning to try and recouple like a rocket going off trajectory in the atmosphere, and thus he started shooting [By clicking or holding click]
And physically he could've been still but HIS Garrys mod was shooting OUTSIDE of the directed fields, hence why there were 0 players nearby but it still tripped because it did something physically impossible by regular means

Next time Ego, don't make your entire brand cheating, I've given you the benefit of the doubt due that it could be possible.

25 minutes ago, Sanzu Zahard said:

Update upon further investigation.

What Vbov made a point earlier was how it was a Yaw pitch detect, something similar to spinbot [As 270 would mean he was 'Spinbotting'] And I may have an explanation for this.

When Garrys mod crashes, or incurs a fatal error, or even when the Source Engine dies clientside, what happens to try and recover it [Especially during graphical or major system changes] The game is set to try and retrieve the last player state, and Visually it can often make the player spin Rapidly, in game the player could also erratically spin.
I've seen this before a few months back before I was ever staff, I was talking to a friend who was fucking around with Linux and they were complaining about there laggy game, they tried upping there resolution from 1600x900 to 1920x1080, they begun spinning at mach fuck, and said "oh SHIT" and there gmod crashed.
Now this wouldn't have tripped the Anticheat, as no shooting was detected, thus no tick detect could've been 'checked'
However Ego could've had something similar, game fucks hardcore because he fucked his resolution, His game tries restoring last player state, via Spinning to try and recouple like a rocket going off trajectory in the atmosphere, and thus he started shooting [By clicking or holding click]
And physically he could've been still but HIS Garrys mod was shooting OUTSIDE of the directed fields, hence why there were 0 players nearby but it still tripped because it did something physically impossible by regular means

Next time Ego, don't make your entire brand cheating, I've given you the benefit of the doubt due that it could be possible.

First of all the reason I mention spinbotting because of this simple reason. WHEN you're spinbotting YOUR first person view does get changed, BUT. Every spinbot has this feature where it allows you to look freely look around without having your pov/camera go crazy, what i think the anticheat DOES is that it checks your thirdperson view against your firstperson view ( i can't seem to explain it better but imagine it as your real view and your fake view, if you ever spinbotted before and tried to shoot you would shoot at the point where your real view was, even tho your fake view is looking at a different spot) Gmod indeed sets your last state before crashing. But it doesn't visually make you spin, or spin at all. IT only sets your pov to the last pos. Which could indeed trigger the anticheat because it changes your view (sets it back to the old one) instantly while your newest view is still a thing. Also you do not need to shoot to trigger the anticheat, a spinbot wouldn't need to shoot at all infact it won't shoot for you it only makes you spin so you are harder to hit. Also you're going harsh on Ego for making jokes about him cheating which I do find a bit harsh because overall it is jokes. 

I'm going to go ahead and unban you based on the majority +1's. Generally speaking, Quad0 bans are handled by SA and feedback from staff is not always considered due to the fact that they do not have access to all of the information surrounding the case. Also the absolute fury this seems to have caused is weighing on my conscience a little, I hear you guys.

  • Like 3
  • reckduck 1
  • point 1
  • Thumb Down 1
Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...