Posted: Tue Feb 06, 2018 5:40 pm Post subject: Any trick for catching a changing address location?
I've been working with "Citadel forged in fire" on the singleplayer mode, and I've been able to find the base address for item drops previously. They've however changed how that works recently, so I can't even AoB scan for the new one.
I've been trying to find the opcode that handles loot, but the address for item amounts seem to change location after an item have changed value twice or so.
Is there anything I can do to prevent this or somehow delay it?
I really just need to be able read what accesses or writes to the item amount address once, so I can use assembly code to catch the changes.
I would try and find the changing pointer for the address or base, with unknown and changed scans. May be this would have an address that doesn't change, but it would require a bit of guess work if the offsets are unknown. But if you used a bit of Lua for processing results into pointers to view (or set up a dissect data view form) then it could speed up the process at lest. _________________
Since the address have been changing all the time I haven't really thought about using an unknown scan. I suppose to could work though for finding a pointer address pointing towards the inventory address.
As for using lua in processing results into pointers? gotta admit I have no idea how I'd do that.
Data dissect is the love of my life though.
Thanks for the help.
Edit: Sadly Citadel is so badly optimized in its early-access stage that I don't have RAM to search unknown :c
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You can download files in this forum