FFXIVAPP/sharlayan

Broken since patch

Opened this issue · 6 comments

Seems memory module has broken, either some data has been moved or offsets have changed. MapID for sure is broken!

Will look into others.

For 32bit the MapID pointer seems to be directly after the MAPINFO signature as you can see here:

MapID

So I guess you need to remove either or both zeros from the PointerPath in /api/signatures or your local version in the executable folder. I am personally working with ffxiv.exe + 0x1084D84 for 32bit and ffxiv_dx11.exe + 0x16C3E74 for 64bit which is surprisingly a static address and will work without scanning 👍

EDIT: I just noticed the content ids on XIVDB are different for the zones than the number I am getting at the address. Should they be the same or are the Content IDs intended to be different from the number in-memory? Could it be I am referring to the ZoneID and not the MapID?

Map actually has more than 1 item in it's section that I've been working with @viion on which includes things like the level of map you are on/etc. It's still being finalized. I believe the zoneinfo pointer and mapinfo signature are are used but I can double check.

I updated the new ActorEntity offsets on the offset site (32 bit only), but haven't looked into the others yet.

@ChristianIvicevic That's how the signatures work. It looks for the signature, and finds a pointer immediately following the signature (Offset by the first offset, in this case, zero, so no offset), then follows that pointer, and returns the address, offset by the second offset (in this case, also zero, so no offset after the pointer either).

Essentially - the first offset is pre-pointer. Each offset after that is applied after following the next pointer.

Also - yes, those addresses are both always "static"... at least, for this particular exe version. The benefit to using signatures, is that usually the signature will still be found following most new exe updates, but pointing to a new "static" location. This means that less updates are needed.

@cjmanca First I completely mistook the zone for the map and was confused about the offsets since I am working on something else where I had the offset for a pointer path (not the actual pointer as usual) after a signature. Thinking of that didn't make me realize what I was referring to 😫

No problem, glad to hear you understand it! Always happy to have more people help with the updates on patch days.