Guide Crystal of Atlan — Reversing Stamina Offsets in Seria.exe

[byte_corvus]

Diving into the internals of Crystal of Atlan and looking at the stamina logic. It seems the game handles resource values via standard floating-point instructions in the main module.

The Technical Breakdown
Based on the dump from Seria.exe, the engine is using

movss

to pull the stamina value into the

xmm0

register for further processing. If you're looking at the instruction

movss xmm0,[rdi+000003C8]

, you've found the read address.

Assembly Context:

Seria.exe+2270F1D:
7FF6A2E90F14 - 75 21 - jne Seria.exe+2270F37
7FF6A2E90F16 - 80 BB 10010000 00 - cmp byte ptr [rbx+00000110],00
7FF6A2E90F1D - F3 0F10 87 C8030000 - movss xmm0,[rdi+000003C8] << Read Stamina
7FF6A2E90F25 - 75 10 - jne Seria.exe+2270F37
7FF6A2E90F27 - F3 0F11 83 14010000 - movss [rbx+00000114],xmm0

Spoiler: Register State at Execution

RAX=000001969F2B26C0
RBX=00000196BEC09600
RCX=0000000000000003
RDX=000001969F33ACC0
RDI=00000196BF78CDD0
RIP=00007FF6A2E90F25

Implementation Notes:

1. The value at

   RDI+3C8

   is almost certainly a Float. In these types of ARPGs, stamina is rarely a simple integer because of regen rates.
2. To modify this, you shouldn't just look at the read. You need to find the instruction that writes to

   [rdi+000003C8]

   . Use the "Find out what writes to this address" feature in your debugger while consuming stamina in-game.
3. If you want to force it via the read instruction, you'd need an AOB injection script to move a custom value into

   xmm0

   right after the read, but be careful of side effects if RDI points to shared structures (like NPCs or other entities).

Has anyone mapped out the rest of the local player structure for this build yet?