using debugg on CE closes game, any work around?

[lisa]

Ok I have started to play around with
Grand Fantasia
I can use CE without issue to find addresses but as soon as I try to do a find out what accesses this address, it starts debugger and game crashes.

Also can't work out how to find the window process.
Ie for Runes of Magic it is Radiant Arcana
I did find in client.exe for RoM a reference to Radiant Arcana but it was line 22800 or around there anyway. I checked task manager and still came up with nothing.


Interestingly I have addresses for hp/mp/skill charges but they arn't static, which isn't interesting the interesting part is I kill the game and start a fresh game and the addresses are still for the same things. I'll do more testing but I may not even need to find static addresses for them.
--=== Update ===--

Nope restarted game again and addresses changed, ohh well.

[Administrator]

Ok I have started to play around with
Grand Fantasia
I can use CE without issue to find addresses but as soon as I try to do a find out what accesses this address, it starts debugger and game crashes.

Probably caused by anti-debugging. Try doing the non-injected method and see if that helps. Also check the debugging options for CE as there are several configurations for preventing detection of debugging (which vary depending on your OS).

Also can't work out how to find the window process.
Ie for Runes of Magic it is Radiant Arcana
I did find in client.exe for RoM a reference to Radiant Arcana but it was line 22800 or around there anyway. I checked task manager and still came up with nothing.

Try installing winspector. Lock onto the window, then bring up the 'properties' for that window. You're looking for the class name.
Alternatively, you can use MicroMacro. Try running this at the script prompt:

Code: Select all

exec printf("Class name: %s\n", getWindowClassName(findWindow("whatever")));

Interestingly I have addresses for hp/mp/skill charges but they arn't static, which isn't interesting the interesting part is I kill the game and start a fresh game and the addresses are still for the same things. I'll do more testing but I may not even need to find static addresses for them.

That is because dynamic addresses will be assigned the first unallocated memory region when being allocated. Sometimes (quite often), when you restart the software, it will just so happen to fit quite nicely in the region(s) it had just given up.

[lisa]

exec printf("Class name: %s\n", getWindowClassName(findWindow("Grand Fantasia")));

worked for me =)

DJO_CLASS

[lisa]

Failed to get debugger to work I had CE 6.0 I just got CE 6.1 and managed to get debugger working.

Start of a long winding road lmao

[MiesterMan]

Failed to get debugger to work I had CE 6.0 I just got CE 6.1 and managed to get debugger working.

Start of a long winding road lmao

I just wanted to say thanks again, this worked for me. And I really like some of the new features 6.1 has that 6.0 didn't. I don't know how you got the debugger to work but I used the VEH debugger and it's working like a charm.