Need someone to check this for technical errors & give feedback

xd kk; There's still a lot of work to be done on it. It's probably not the easiest thing to read because I got a little lazy in regards to writing it.

You guys can contribute sections if you'd like.

Thanks,
I'm going to do a chapter of applied reversing on like Quake or ET; my PC isn't exactly 'high-end' with it's shot onboard graphics mdoule

If you want to suggest any sections, feel free to.

'As a reverse engineer or hacker you likely won’t be dealing with them too much unless you have to start working with anti-debug stuff'

I use them quite often when exception hooking, for example purposely setting pointers to null in places where the game doesn't check them and they could give me an advantage(render loops etc).
setting pages to not executable and stepping through them(on modern hardware there is barely a performance hit when stepping through them)

Alright, I'll look into it. What do you mean by setting pointers to null to catch an exception? Like, to detour the rendering of a specific objects? I would think that be an odd method of doing so but it's interesting and I'll definitely think about changing it. That line was more related to reverse engineering the target opposed to attacking it.

It sounds as though you have a couple interesting ideas when it comes to hacking methods; if you want to write about some of them I'll add them to the section when I start writing it. I'd really appreciate it. (By hacking methods I mean like - installing a HWBP & VEH to detour, buffer overflows, or like what you just explained.)

Thanks for your feed back.

Modern Warfare 2(1.0.182 executable used for AlterIW):

so 0x1747E08 is the address for the glass_debug cvar.
Find references gives 1 more result besides the one above:

Which is part of the rendering code.

Now we can set up an exception handler, set 0x1747E08 to point to NULL and we have ourselves an exception in the rendering loop =)

For extra fun you could even restore ECX to what it was supposed to be and have the game execute like normally =)

oic what u did thur. Hmmz, interesting idea. I presume then that the handler would unset the zero flag to skip the jump? I never thought of causing exceptions for the purpose of hijacking control of a thread but its a good idea. Why can't you just detour the routine at 0x00479790? It seems that it could be the constructor of the cvar objec\struct(I didn't see enough of the snippet to determine.)

btw: Changed the wording:
"As a reverse engineer studying a target, you likely won’t be dealing with them too much unless you have to start working with anti-debug stuff but because they are an incredibly powerful tool for attacking your target if used appropriately, we will go over them. "

Also added a section on the stack frame which should've been after the calling conventions.

I couldn't agree with you more.
Regarding your last point about the handler: I thought the same thing, lol. It was what a pulled from serveral undocumented NT internals websites(windows doesn't have an official documentation.) I really should change it to void* or something I just wanted to remain consistant with the other documentations.

It is a very dry read, agreed. I think I'm going to go over it and try to make it more interesting. Once I get to the section where we actually go through the process of reversing a target it will be a hella more fun.

Naming conventions are always dependant on what the developer's taste is; so I understand your prespective on that.

I will also try to jam more background information to avoid confusing the reader. It's just there's a lot which would need to be discussed.

I guess when you write a piece of code you always look at it as if it were self-explanatory but you make a good point and the vtable should be explained more.