New Patch - New BaseAddress...
v0.2.0.e:
0x03DA7698
New Patch - New BaseAddress...
v0.2.0.e:
0x03DA7698
Got an error. seems like offsets wrong or what, standelone versionCode:self.pointer = 0x03BC1DF8 self.offsets_CurHP = [0x38, 0x378, 0x38, 0x18, 0x38, 0x0, 0x378] self.offsets_MaxHP = [0x38, 0x378, 0x38, 0x18, 0x38, 0x0, 0x388] self.offsets_CurES = [0x38, 0x378, 0x38, 0x18, 0x38, 0x0, 0x38C] self.offsets_MaxES = [0x38, 0x378, 0x38, 0x18, 0x38, 0x0, 0x390] self.offsets_CurMP = [0x38, 0x378, 0x38, 0x20, 0x38, 0x0, 0x380] self.offsets_MaxMP = [0x38, 0x378, 0x38, 0x20, 0x38, 0x0, 0x388]
Could not read memory at: 1968, length: 4 - GetLastError: 299
can u please share all offsets?
Is there a way to display the monsters in the radar?
Patch v0.2.0f:
0x03DBB7D8
Code:BasePtr := ProcessBase + 0x03DBB7D8 (PathOfExileSteam.exe / v0.2.0f) (int) aPtr_CurES := [0x30, 0x60, 0x38, 0x18, 0x38, 0x0, 0x38C] (int) aPtr_MaxES := [0x30, 0x60, 0x38, 0x18, 0x38, 0x0, 0x390] (int) aPtr_CurLife := [0x30, 0x60, 0x38, 0x18, 0x38, 0x0, 0x380] (int) aPtr_MaxLife := [0x30, 0x60, 0x38, 0x18, 0x38, 0x0, 0x388] (int) aPtr_CurMana := [0x30, 0x60, 0x38, 0x20, 0x38, 0x0, 0x380] (int) aPtr_MaxMana := [0x30, 0x60, 0x38, 0x20, 0x38, 0x0, 0x388] (int) aPtr_CurSpirit := [0x30, 0x60, 0x38, 0x20, 0x38, 0x0, 0x3A8] (int) aPtr_MaxSpirit := [0x30, 0x60, 0x38, 0x20, 0x38, 0x0, 0x3AC] (int) aPtr_CurExp := [0x30, 0x60, 0x38, 0x0, 0x30C] (int) aPtr_NeededExp := [0x30, 0x60, 0x38, 0x0, 0x310] (int) aPtr_CurLevel := [0x30, 0x60, 0x38, 0x0, 0x314] (str) aPtr_Area := [0xAF8, 0x5E0, 0x0] (int) aPtr_AreaStrLen := [0xAF8, 5F0]
Last edited by sturmi; 04-16-2025 at 01:03 PM.
did the offsets changed again with a ninja patch?
Seems like one of those 5 hotfixes broke the basePtr once again...
new one is:
However, there haven't been any changes to the offsets for quite a bit. These are still working (and should basicly work even after patches).Code:BasePtr := ProcessBase + 0x03DBB808 (PathOfExileSteam.exe / v0.2.0f HF5)
That basePtr works for mouse+keyboard. But seems there are another for joystick now
This Sounds odd to me... Nevertheless i cant test this since i dont use any controller
No, for gamepad pointer the is the same but pressing potion button that issue couse u need emulate physical press button on u gamepad, or create a virtual gamepad from script and remap physical device buttons to an virtual gamepad + emulate pressing if conditions true. So thx u again mister Sturmi
for Keyboard or Controller the Base Offset should be the Same but the the UI changes a lot
so u have to change the path to the UI Element
use ExileCore DevTree go to the UI root check the Children to find out how u get to the Life Element
0x0 is the Pointer to a VTable i think
0x8 cointains the Structure Size of the UI-Element
and i can say 0x30 is a SelfPointer and u dont need this
0x38 is the Pointer to the First Children
0x40 is the Pointer to the Last Children
0x48 is the Pointer where the Children Ends
if there only a few Children the Pointer get Stored within the UI-Elements starting area
i think this should start at 0x60 the Pointer at 0x38 should Point to this address in this Case
after that i dont know the exactly offset there should be
the boundaries of the UI-Element
and the X / Y coords where the UI element is
and a Scale Multiplier