StrafeAnalyzer VS cstrike15_src

pure movement: cowhop spicy's strafe analyzer https://github.com/spicy/StrafeAnalyzer

CS:GO and other source games have had loads of serious vulnerabilities. I've found a few myself just by looking at the leaked source code:

https://github.com/perilouswithadollarsign/cstrike15_src

The engine code is very old, and CS:GO itself was not developed by valve but by Hidden Path Entertainment initially as a port of CS: Source to console and they didn't really do a great job.

yes

I get where you're coming from and nothing is perfect but from a purely technical standpoint the hitboxes now are better than what most other games have. Also thanks to the leaked 2017 CS GO source code we know exactly how the post rework hitboxes (including the pose parameter bug fix) work and you could go over the code yourself if you wanted to.

If you look at the leaked source code here: https://github.com/perilouswithadollarsign/cstrike15_src (in the engine/net_chan.cpp file) you see that I am not an attention seeker and I am genuinely trying to make a packet injection tool. I am trying to follow this guide here: https://blog.ret2.io/2021/07/21/wtf-snapshot-fuzzing/ to fuzz csgo to find security vulns, but I am having trouble reverse engineering that said struct which I mentioned in my post.

Thanks for that. You dont even have to get too far in the code to see that there's a function to ignore players - https://github.com/perilouswithadollarsign/cstrike15_src/blob/f82112a2388b841d72cb62ca48ab1846dfcc11c8/game/server/NextBot/NextBotUtil.h

I'm surprised I haven't found a complete and detailed explanation of the matchmaking rank system following the 2015 leak given that this is, along with anticheat, one of the most criticized aspects of the game. Do you know of a source that did this and explained how it works?

MAX_THREAD_IDS is defined as 128 in a file with a copyright notice of 2005, which was when the very first consumer dual core processors started getting released:

https://github.com/perilouswithadollarsign/cstrike15_src/blo...

Entirely reasonable that no one in 2005 would even consider the possibility of 128 core processors. I bet nobody reconsidered or even looked at that code ever since, until it started breaking because of today's extremely parallel cpus starting to get somewhat affordable for consumers.

Like CS:GO, lol. People even started forking it.

I have no Idea really but I do know the csgo codebase was leaked some time ago https://github.com/perilouswithadollarsign/cstrike15_src maybe this can be of use ?