Has anybody had problems reversing Dialbo3.exe with IDA? I have not downloaded the game client yet, and am wondering if anybody has had problems with the RAM and process scans Bilz is doing while you are reversing?
I heard rumors that they are using Warden for diablo3 now.
+ you can debug using the emulator so theres no warden involve.
and i'm not sure that warden is even loaded on the beta.
also unless you hook D3 functions and modify the code, they don't really have anyway to match your injected code if it's private. Atleast it's how i understand warden
You really don't have to worry for static reversing like you do with IDA.
If you are gonna debug it the only thing i've noticed is that it pops an assert if you try to login with a debugger attached.
I've been using WinDbg to debug the running game client code with no issues (other than the fact that there is some horribly inefficient code).
I can have WinDbg launch the app, or I can attach to it after I login. I've had no issues with doing either. I have not experienced the "assert" that Nesox mentioned in the previous post.
Bookmarks