Jump to content

NPC stats and drops

From Age Of Embers Wiki
Revision as of 21:47, 23 July 2026 by imported>Age Of Embers Editorial Team (Initial verified wiki package import)
NPC stats and drops
TypeNPC reference
AccessIn-game examine, Drop Viewer and combat interfaces
StatusPlayer reference
VerifiedActive NPC/drop definitions


This page explains how to read NPC information without confusing a registry entry with a complete combat definition. A boss/NPC can be listed by a task or combat-achievement registry while its combat stats are inherited from the client, a shared definition or an external data table.

What players should check

  • Combat level and hitpoints: read the in-game examine/combat panel; these are the values used by the live encounter.
  • Attack styles and weaknesses: use the boss guide and protection-prayer notes before choosing gear.
  • Drop table: open Drop Viewer and search the exact NPC name. Guaranteed, common, unique and tertiary rolls are shown separately.
  • Slayer/task status: Task book may show a different task name from the NPC’s display name.
  • Variants: normal, corrupted, hard-mode and wave variants can have separate drops and stats.

Why some entries do not show a table here

The source contains shared processors and conditional reward tables. Publishing a blank table as if it were a zero-drop NPC would be misleading. When a direct source table is available, the linked Loot table - ... page records it; when it is conditional or runtime-driven, the page directs players to the live Drop Viewer instead.

Complete NPC workflow

1. Search the NPC’s exact display name in Drop Viewer. 2. Confirm the variant and difficulty before comparing rates. 3. Read the linked boss or minigame guide for mechanics and supply setup. 4. Check the Collection log for unique progress. 5. Compare the item’s sale, shop and Burn Point value before banking or sacrificing it.

Ready to play Age of Embers?
Use this guide in-game, then jump straight into the server. Progress is persistent across the supported desktop, mobile and web-client routes.