I don't use FollowPlayer Function since mine's a herbs-farmer bot but here it is anyways...
Already posted earlier about these Action Function Addresses in [Only registered and activated users can see links. Click Here To Register...]
Address Action 1 = Start Action Function (At the moment this is 0x49FF80)
Address Action 2 = Perform Action Function (Varies. Depends on the action)
Address Action 3 = Finish Action Function (At the moment this is 0x4A0590)
To trace the [Address Action 2], I check all the addresses that calls the [Address Action 1] and make break point to each. I perform some actions in the game client and wait for the breakpoint. In the breakpoint, the [Address Action 2] is called a few lines after the [Address Action 1].
For CastSkill and RegAttack functions, I did some further tracing (before and after the [Address Action 1]) to get some addresses for functions that will simplify the OpCodes.
These are the Current Addresses that is calling [Address Action 1]:
The PUSH Column determines the type of Action. You will find them before the Address Action 1 is called.
Also if you trace down MoveTo Function through KEYBOARD MOVE, you will notice the 'Switch function' in the code which will give you this list of Case Index and corresponding Directions:
This is how I repeatedly crash the PW Client.
So far I am getting results so I think my theory is somewhat correct :D
And yes ollydbg is a cool debugging tool!
Already posted earlier about these Action Function Addresses in [Only registered and activated users can see links. Click Here To Register...]
Address Action 1 = Start Action Function (At the moment this is 0x49FF80)
Address Action 2 = Perform Action Function (Varies. Depends on the action)
Address Action 3 = Finish Action Function (At the moment this is 0x4A0590)
To trace the [Address Action 2], I check all the addresses that calls the [Address Action 1] and make break point to each. I perform some actions in the game client and wait for the breakpoint. In the breakpoint, the [Address Action 2] is called a few lines after the [Address Action 1].
For CastSkill and RegAttack functions, I did some further tracing (before and after the [Address Action 1]) to get some addresses for functions that will simplify the OpCodes.
These are the Current Addresses that is calling [Address Action 1]:
The PUSH Column determines the type of Action. You will find them before the Address Action 1 is called.
Also if you trace down MoveTo Function through KEYBOARD MOVE, you will notice the 'Switch function' in the code which will give you this list of Case Index and corresponding Directions:
This is how I repeatedly crash the PW Client.
So far I am getting results so I think my theory is somewhat correct :D
And yes ollydbg is a cool debugging tool!