I use ollyDbg its a pretty good debugger. The function isn't called directly, its done by call eax or somthing so there isnt a way to know where or even if its called at all. There is a lot of stuff in the exe that is never used but you can edit the memory to force it to execute, of course the game will crash after doing so since the stack is buggerd up.
Im thinking a level editor might not be possible because it seems to be in exactly the same format as AO path files, the offsets are added onto a base pointer in a table of function pointers which do some pre-hardcoded stuff :/
Also the shift table used to decode cam files is created by using some other hardcoded lookup table.. so thats not looking too good either.
|