Quote:
Originally Posted by iktov2
Check that tutorial that Tri posted about packets. You don't need to know how to do anything with packets, but it briefly explains tracing functions from the Send() api.
Basically all I did was BP send() and do something in-game, then trace it back from there and recorded all functions I went through. Then went back and looked at each function as I repeated the action in-game. If it triggered a BP from the action I did in-game I would look at the arguments being passed through the function and try to make sense of them.
Then just slap them into the .dll and give it a shot.
I've found it to be a bit difficult with games like RIFT though. I just get sent around in a loop and never end up on the source of the action that triggered the call to Send(), since 12sky2 was the first time i've ever done this kind of thing its a bit more difficult tying to apply it to other games.
|
i think you can also have a try with cheat engine autoassembly before you put it onto dll, by this way ive found a ton of "COOL" functions that i cant speak more here