Help with new offsets

Posts 1–12 of 12 · Page 1 of 1
Help with new offsets
Given that the dereferenced player base after the update is 0x1C912A70

Could someone experienced with memory view find and update the following offsets ?

xCoordAddr = string.format("[%s]+120", coordAddress)
yCoordAddr = string.format("[%s]+124", coordAddress)
zCoordAddr = string.format("[%s]+128", coordAddress)
xVelAddr = string.format("[%s]+150", coordAddress)
yVelAddr = string.format("[%s]+154", coordAddress)
zVelAddr = string.format("[%s]+158", coordAddress)
xPerAddr = string.format("[%s]+1A0", camAddress)
yPerAddr = string.format("[%s]+1A4", camAddress)
zPerAddr = string.format("[%s]+1A8", camAddress)

Don't pay too much attention to what the code does, just focus on the offsets of the x, y, z coords, x, y, z velocity and x, y, z cam cause they are needed for spd scripts updates.

TIA !
you make aimbot ? its public?
only need to replace coordAddress

local coordAddress = string.format("[[[[%s]+0]+28]+E8]+4", basePtr)
Quote Originally Posted by truyvietnam View Post
only need to replace coordAddress

local coordAddress = string.format("[[[[%s]+0]+28]+E8]+4", basePtr)
thanks u very much for this but how could u get new coordadress could u explain pls??
Anyone has the new basePlrPtr offset?
Quote Originally Posted by CKuJIoBuK View Post
thanks u very much for this but how could u get new coordadress could u explain pls??
Well I just got it from another cheat but you can find player coord first in CE (recommended finding Y axis), and you need to filter it and look for the one that when active, you can't move in that axis.
Open pointer scan, scan on that address.

Check on "Pointers must end with specific offsets", change the last offset to 80 (change it incase the game change it in future)
Check on "Base address must be in specific range", put trove.exe+<Local player offset> in both "From" and "To"


Scan it and store the file in somewhere.
You should repeat this process to get a low pointer path list.
After that, you can choose any pointer and use it with your local player offset, that your pointer to our coordinate
For coordAddress just remove the last offset "80"
Quote Originally Posted by CKuJIoBuK View Post
thanks u very much for this but how could u get new coordadress could u explain pls??
Thank you ALOT <3 <3 <3 <3 <3
Quote Originally Posted by truyvietnam View Post
only need to replace coordAddress

local coordAddress = string.format("[[[[%s]+0]+28]+E8]+4", basePtr)


BIG UPS to u my friend, that actually updated the script, thanks a lot !

Oher parts of it are still broken because i guess more offset updates need to be applied for player list, map overlay tp etc. but the two most useful functions (speed and noclip) are functioning correctly !

Could u explain a bit how u got the new offsets in case of future updates ?
Quote Originally Posted by itsmistertest View Post
BIG UPS to u my friend, that actually updated the script, thanks a lot !

Oher parts of it are still broken because i guess more offset updates need to be applied for player list, map overlay tp etc. but the two most useful functions (speed and noclip) are functioning correctly !

Could u explain a bit how u got the new offsets in case of future updates ?
I explained in the same thread

Here is some images
https://imgur.com/nRbywkwⓘ
https://imgur.com/g6x2kZ8ⓘ
Quote Originally Posted by truyvietnam View Post
I explained in the same thread

Here is some images
https://imgur.com/nRbywkwⓘ
https://imgur.com/g6x2kZ8ⓘ
Thanks for the feedback ! The thing is that i tried to manually find the offsets but i run to the following problem:

I got the y address every time correctly but after choosing find out what access this address or what writes to this address and reversing the opcodes, i ended up finding that the game loads the cords to one of the registers that hold floating points in arrays. Then i tried to find which address that array is located on and got another address which looks really "Unstable" since everything keeps changing when viewing it on the memory viewer or the game keeps crashing if i tried to attach the debugger on it. Any thoughts on that ?
Quote Originally Posted by itsmistertest View Post
Thanks for the feedback ! The thing is that i tried to manually find the offsets but i run to the following problem:

I got the y address every time correctly but after choosing find out what access this address or what writes to this address and reversing the opcodes, i ended up finding that the game loads the cords to one of the registers that hold floating points in arrays. Then i tried to find which address that array is located on and got another address which looks really "Unstable" since everything keeps changing when viewing it on the memory viewer or the game keeps crashing if i tried to attach the debugger on it. Any thoughts on that ?
Look like you hit a C union or similar thing, which idk how to look for it value in cheat engine and the game use it for math using our pos. But you can just find the register that count next to it.

For example: mov esp, [esi+80]
you want to get address of esi

I recommended using pointer scan because you may not find it manually
Quote Originally Posted by itsmistertest View Post
Given that the dereferenced player base after the update is 0x1C912A70

Could someone experienced with memory view find and update the following offsets ?

xCoordAddr = string.format("[%s]+120", coordAddress)
yCoordAddr = string.format("[%s]+124", coordAddress)
zCoordAddr = string.format("[%s]+128", coordAddress)
xVelAddr = string.format("[%s]+150", coordAddress)
yVelAddr = string.format("[%s]+154", coordAddress)
zVelAddr = string.format("[%s]+158", coordAddress)
xPerAddr = string.format("[%s]+1A0", camAddress)
yPerAddr = string.format("[%s]+1A4", camAddress)
zPerAddr = string.format("[%s]+1A8", camAddress)

Don't pay too much attention to what the code does, just focus on the offsets of the x, y, z coords, x, y, z velocity and x, y, z cam cause they are needed for spd scripts updates.

TIA !
From what I understood, you're looking for the player's coordinates, acceleration on x, y, z, and the player's camera.

From what I saw in the addresses, it looks like the person who wrote this was just mapping those offsets.

I actually have all of these, and they’re pretty simple.

I’ll give them to you along with localPlayer.

Code:
LocalPlayer = 0x1098418
coord_x_Offsets = 0x8+0x28+0xE8+0x4+0x80
coord_z_Offsets = 0x8+0x28+0xE8+0x4+0x84
coord_y_Offsets = 0x8+0x28+0xE8+0x4+0x88
acceleration_x_Offsets = 0x8+0x28+0xE8+0x4+0xB0
acceleration_z_Offsets = 0x8+0x28+0xE8+0x4+0xB4
acceleration_y_Offsets = 0x8+0x28+0xE8+0x4+0xB8
View_Matrix_x_Offsets = 0x20+0x100
View_Matrix_z_Offsets = 0x20+0x108
View_Matrix_y_Offsets = 0x20+0x100
View_Angles_y_Offsets = 0x10+0x28
View_Angles_x_Offsets = 0x10+0x2C
i hope this hleps
Posts 1–12 of 12 · Page 1 of 1

Post a Reply

Similar Threads

Tags for this Thread

None

Talk with us