Closed swoopae closed 3 years ago
This is a cheat, not an exploit.
It is exploiting faulty game code, so it is an exploit..
It is exploiting faulty game code, so it is an exploit..
No, it's not, it injects into CS:GO and executes 3rd party code. How hard is to understand that to execute an exploit you don't modify the internals?
You don't need to execute third party code to abuse this, simply having a lower frame rate than the server tickrate causes the same thing, just on a lesser scale. The server code is FLAWED, therefore this is a bug. What don't you understand? Obviously you are another generic hack-vs-hack user who tries as hard as they can to keep this from getting patched
It is exploiting faulty game code, so it is an exploit..
No, it's not, it injects into CS:GO and executes 3rd party code. How hard is to understand that to execute an exploit you don't modify the internals?
Still an exploit, just like the server crashers that were around in 2018 - yes they had to inject code too, yet EVEN VALVE called it an exploit on their OWN changelog page and Reddit.
Don't bother commenting if you have no idea what you are talking about.
When your frame rate is less than the server tick rate you're causing a significant bottleneck unless you lower your frame rate on purpose.
So beacuse it's in an unlikely scenario it shouldn't be reported and patched by Valve? What the hell is your point? Good one bud.
As for the proof, look in the game's leaked source code, we're not here to hold your hand. Kind of sad you don't want to see less hackers in CS:GO and refuse adding 2 entire files to a repo that you know Valve checks regularly and therefore fix a game-breaking exploit.
btw:: exploit verb [T] (USE UNFAIRLY) to use someone or something unfairly for your own advantage
When your frame rate is less than the server tick rate you're causing a significant bottleneck unless you lower your frame rate on purpose.
Wrong - when the framerate drops below the tickrate the engine compensates by creating more CUserCmd's, which also triggers the same code path leading up to the engine holding back outgoing CLC_Move messages, thus queuing them to be read in one server frame - read the engine source code or GTFO if you have no idea what you are talking about.
Still not patched as of December 2020.
README.md is self explanatory.
This exploit basically makes CS:GO unplayable in low to mid trust-factor and as it is invisible to Overwatch, you can't just report the enemy for using it because nothing will happen. It's one of the reasons CS:GO is the cheater hellhole it currently is. This is the only repo I've seen that actually gets Valve's attention, so I'm trying my luck at finally getting this fixed.