> GLIntercept works by overriding the call to wglGetProcAddress, wrapping the real function pointer in some assembly and then returning it to the application be

> GLIntercept works by overriding the call to wglGetProcAddress, wrapping the real function pointer in some assembly and then returning it to the application being debugged. I used to code Counter-Strike cheats for fun[0] back in the 1.6 era and this is how the simplest ones worked. For example, wallhack hooked glBegin and, if the mode was GL_TRIANGLE_STRIP or GL_TRIANGLE_FAN (used for models mostly), it disabled GL_DEPTH_TEST which in turn rendered models over the walls. More advanced cheats needed to hook onto the game code to extract information from memory and call/intercept game functions, but it was mostly the same. There was a thriving community where all kind of information was shared, including how to bypass anticheat programs, but it died in an incident long after I was gone (I miss you, GameDeception). Very fun memories :) [0] Really. I never shared any of those cheats or used them online. It was just the fun of learning how a system was made and then breaking it.