This site has been incredibly useful to me over the years, but I've never really had a great deal of time to give anything back. That's changed now, but I'm finding it really hard to break into the whole "hacking games for widescreen/surround support" (I can't find anything relating to the actual process on the site - sorry if I missed something). I've been programming for a while now, but I've never really done anything in the way of reverse engineering. I've been reading around what I think I need to know from Google, but in the end it doesn't really get me anywhere since I'm mostly clueless on how people even start a hack. I've had ideas that I've tried out, but I could really use some pointers from the gurus that frequent this site. I'm sure I'm not the only one who would like to get into this, but doesn't really know where to start, so any pointers could potentially get a few more game fixers going around here. Once I've acquired the know-how, I'd be happy to write a tutorial article for this site.
So, to get the ball rolling, here's a couple of questions that come to mind:
- What method do you use when starting a hack? I've always assumed it's just searching for known values in memory, and changing things in game to see what addresses change...but surely alot of things change when resolution does, and this surely wouldn't help you identify something obscure like HUD positioning...right?
- Recommended tools for this sort of thing? I've played briefly with TSearch, and seen OllyDbg mentioned.
Any help, big or small, would be greatly appreciated. Thanks.
Note to self/others: Useful thread I (eventually) found (thanks squ1zzy): http://www.wsgf.org/forum/8483/squ1zzy-some-knowledge
Another with a few gems of wisdom: http://www.wsgf.org/forum/5965/correct-fovand-unstrectched-values-artmoney
Article on FoV calculations: http://www.wsgf.org/article/fov-calculations-complicated-math-version-developers