Aznmaster206

but say using your example of "52" in hex, hex value has 6 values associated with each pointer, not just a single 1. as i said, you while loop through each key(offsets), but iwthin each key when you're matching the hex values, u forlop i=1:6 such that each of the 6 hex values all match and return the offset value from the new update. If the 6 hex values dont match the old values, then it'll go to the 2nd offset that finds a "52" in the 1st digit, but also continues to check the other 5 values.

isn't that what memory diagnostic tool is for ;o.. I personally havent written anythign in C++, though i helped robotics team debug stuff and learned some stuff about pointers and memory addressing.. I would think he offsets would be something similar to that. I'm not experienced with offsets/hex value and stuff but from the general idea that the topic is based on... The hex values of the old and new should be similar, if not identical. You could probalby write a simple matching code that: uses the offset/hex pair as key/data whileloop through the whole address to find a matching hex and return the associated offset. move on to next pair of key/data used in the bot assuming that hex value from old and new poe remains identical...

it shouldn't be that difficult.. if its coded in C++, basically include some libs (probably already included), then basically "open" the file. Construct a whileloop that loops through the # of memory tokens. and store each offset in an array. Then softcode the rest of the c++ file to use the array. That way, you basically copy/paste new offsets into this ini/txt file and the bot will "open" a new offset txt file when you change it and auto-update.

Out of curiosity, wouldn't it be better to have the offsets stored in a separate txt/ini file. That way, the bot could open the txt/ini file and automatically use the offset text directly within the file. This way, the community could contribute and a "new" bot patch wouldnt be necessary after every minor update. Basically, making it semi-open sourced...

1) So skeleton summon shrine keeps summoning while bot keeps killing skeleton without "clicking on shrine". Maybe make the bot click on skeleton shrine as priority when it encounters one. 2) after clicking on skeleton shrine, bot will attack the allied summons... In this case, bot attacks nothing for hte next 45sec