-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pulling opcodes #3
Comments
everything is in memory view, search for I_TELEPORT, then search for the beginning of the function (something like 10 line before the I_TELEPORT "Call, Call, Call"), right click, go to address, copy the address |
good? or still pb? |
Still can't find it. |
Cheat engine -> memory view -> view -> referenced string http://puu.sh/nrfBH/84b0860690.png |
You are stuck somewhere, or you found out how to get the opcode? (added NA file btw) |
I was doing dungeons, but it looks like the address might be 019EE38? Is that what you have? |
the address is 0x019D06C0 (right click on what you found, go to address, and that it, and copy what is in the text input) |
I'm not seeing that anywhere. http://i.imgur.com/O0NV7UX.png If I go to the address, I get what was in my previous image. |
Scanning memory for referenced strings take significant time, if you stop before it ends - you will see nothing. |
It's already done as far as I can tell. I just left it there for a few hours and came back to it. |
if you see http://i.imgur.com/lNZw41Z.png - just right click on copycopycopy and select go to address to see address of this code, thats all you need to compile opcode dll. |
I know this is an old topic but how do you pull OP codes? I tried that dll posted on ragezone but it just returned an error. |
When searching for the I_TELEPORT string to pull opcodes, where do you search from? I found the address for it in the memory viewer, but I can't see it in the assembly viewer. Going to the address in assembly viewer does not show the address, but rather some module + offset.
The text was updated successfully, but these errors were encountered: