DreamPoeBot developer reference

Find the API.
Build the capability.

Explore DPB1 and DPB2 by type, member or use case. Every reference includes its signatures, arguments, available results and links to related APIs.

2,215 types 14,236 members 91,072 named values
DPB1 · 0.3.29.47DPB2 · 0.4.5.88Reviewed 2026-10-02
API catalog

Find the capability you need

2215 types found
Search includes all members, overloads and named values.
DPB1Class · Interface and panels

LokiPoe.InGameState.HideoutEditorUi

This class let you interact with the Hideout Editor panel (the panel used to import and export Ho, and edit all the Ho features.) The main usage of this class, is to Import a specific Ho layout.

2 declared membersOpen reference →
DPB2Class · Interface and panels

LokiPoe.InGameState.HideoutEditorUi

This class let you interact with the Hideout Editor panel (the panel used to import and export Ho, and edit all the Ho features.) The main usage of this class, is to Import a specific Ho layout.

1 declared membersOpen reference →
DPB1Class · Interface and panels

LokiPoe.InGameState.HideoutUnlockedUi

This class has only 1 property `IsOpened` and return true when the small label that let you know that a new Hideout is been unlocked is visible. This can be used to make sure you completed one of the areas that let you unlock new Ho. Just check for this class IsOpened property in Tick, while you clear the area, as soon as the property is true, you have completed the area and unlocked the Ho.

1 declared membersOpen reference →
DPB2Class · Interface and panels

LokiPoe.InGameState.HideoutUnlockedUi

This class has only 1 property `IsOpened` and return true when the small label that let you know that a new Hideout is been unlocked is visible. This can be used to make sure you completed one of the areas that let you unlock new Ho. Just check for this class IsOpened property in Tick, while you clear the area, as soon as the property is true, you have completed the area and unlocked the Ho.

1 declared membersOpen reference →

This reference covers the developer-facing declarations in the reviewed Release source snapshot, including inherited APIs through their base-type links. Product versions are documented separately so differences remain visible.