Summary
AtlasPanel.VoidstoneSlots consistently returns a non-null but empty list,
even when the Atlas panel is open and the character has voidstones socketed.
Observed behavior
var atlas = GameController.IngameState.IngameUi.Atlas;
// atlas != null, panel confirmed open in-game
var slotList = atlas.VoidstoneSlots;
// slotList != null
// slotList.Count == 0 <-- always, regardless of actual voidstone state
Tested with a character that has at least one voidstone socketed. Confirmed
atlas itself resolves correctly (not null), so this isn't a case of the
panel simply not being open — the issue is specifically with
VoidstoneSlots returning nothing.
This points to the offsets/lookup logic backing VoidstoneSlots being
stale, likely following a recent Atlas panel layout change in-game that
the property hasn't been updated to match.
Steps to reproduce
- Load into a character with at least one voidstone socketed.
- Open the Atlas panel.
- Call
GameController.IngameState.IngameUi.Atlas.VoidstoneSlots.
- Observe
Count == 0.
Environment
- ExileApi-Compiled build: 329.15
- Game version: PoE 3.29.1
Summary
AtlasPanel.VoidstoneSlotsconsistently returns a non-null but empty list,even when the Atlas panel is open and the character has voidstones socketed.
Observed behavior
Tested with a character that has at least one voidstone socketed. Confirmed
atlasitself resolves correctly (not null), so this isn't a case of thepanel simply not being open — the issue is specifically with
VoidstoneSlotsreturning nothing.This points to the offsets/lookup logic backing
VoidstoneSlotsbeingstale, likely following a recent Atlas panel layout change in-game that
the property hasn't been updated to match.
Steps to reproduce
GameController.IngameState.IngameUi.Atlas.VoidstoneSlots.Count == 0.Environment