Use the API reference without getting lost

Start with a question, not a class alphabet#

• Is a player loaded? Start with LokiPoe and its game-state properties.
• Which objects are currently available? Start with ObjectManager and a specific object type.
• What is in the carried inventory? Start with InstanceInfo and InventorySlot.
• Can I use a bound skill? Start with SkillBarHud and Skill.
• How do I find a path? Start with ExilePather, then the mover guide for your product.
• How do I integrate behavior? Start with IPlugin, IBot, IRoutine, IPlayerMover or ITask and the matching Academy track.

Read a member in five passes#

1. Product and type: make sure this is your client and the correct owning type/namespace.
2. Summary: what does the operation claim to do? Some descriptions come from source summaries; others are concise inferred descriptions.
3. Signature: is it a property to read, a method to call, an event to subscribe to or an enum value? Note whether you need an instance.
4. Arguments and return value: choose the correct overload and check how it reports no data or failure.
5. Context and related APIs: find readiness requirements, base types, caller ownership and the matching guide. A short API summary is not a full workflow.

A small glossary you can use immediately#

• Interface: the methods and properties DPB expects your component to provide.
• Instance: the actual object providing behavior; selecting a routine chooses an instance, not merely a type name.
• Property: a value exposed by an object. Reading it may depend on current game state.
• Overload: another method with the same name but different arguments. Choose by the types you actually have.
• Enum: named choices or result values. Prefer their names to guessed numbers.
• Null: no object is available. Check it before accessing properties.
• Tick: a short callback during a running bot session, not an independent background thread.
• Coroutine: an async workflow resumed cooperatively by the bot.
• Request accepted: one API boundary succeeded. It does not prove the final gameplay outcome.

Follow links with a purpose#

Use catalog search for a type, member name or operation. Set the product filter first when an API differs between clients. Use a member's permanent link when sharing a particular overload.

The Academy's API links resolve to the actual catalog entry for the selected product. Reference pages link back to the relevant lessons, so you can move from a signature to a complete project and back.

If search shows an unfamiliar low-level-looking name, you usually do not need it to start. Return to your concrete question and the public entry point used by the nearest recipe.