to my understanding Ryftomate is not usable after each Rift patch due to Memory addresses / offsets being changed with-in rift??? There are a few bots on the market (not for rift) that automatically scan the Game client for the new Memory address's / offsets to hook Can rfytomate be designed to do this? or is it not safe todo so? Would be easier on the devs in the long run and better for the customers if it all went well and was possible with rift
after a patch devs have to check many things one part are the offsets etc but also there are many others things as well
Some games don’t do anything to hide their memory addresses, the rift team have done a decent job of ensuring there’s are a pain in the ass to find some are over twelve levels deep. As an example there are 29 addresses that contain MAX HP, of these only one remains static the rest of the addresses change during game play. So when you find the static addresses: 0260E238 You then need to find what points to the addresses and use that instead. This way the software survives a reboot by using a static pointer rather than a dynamic address. Although it would be possible to write something that would auto detect the addresses because there are so many false ones and because some of them are dynamic you would end up spending a lot of time setting up the bot before each run and every time an address changed (zoning levelling etc) you would need to rescan them.
It IS possible to have ryftomate do this...to a point... Scanning against all the millions/possibly billions of different memory offsets to find information does take ALOT of computing power, you're still looking at 30-60min of just non stop scanning. The process would have to make the game log out, change chars, and even reboot the game itself to weed out the bad "static" offsets... You'd almost need it to be ran on the server side of things, for someone to code it up, put it on a dedicated server (or pc), then do its thing... Even though, you're talking MANY MANY MANY lines of coding, and i'd guess that it'd be a larger project than Ryftomate itself... It's just easier to do it all on the patching day.
Not really true, you can easily use pattern matching to find memory locations in advance, unless you want to waste development time and scan memory locations one at a time then sure, you are definitely right.
