Skip to main content
Every building, monster, troop, hero, resource, and equipment type the client can reference by numeric ID, extracted by a 6-agent parallel pass over Global_EnumType.lua (the master Lua enum repository, hundreds of small category tables) and the relevant table_decompiled/*.lua data tables, cross-referenced against the English locale strings for display names where a lookup path exists.

​
By domain

Reading this table: Not every domain’s numbers work the same way. Buildings, resources, and most of items/equipment come straight from small, complete category enums, high confidence. Monsters mixes 2 complete category enums with a sample of the actual per-monster catalog (a 12,115-row per-level table deduped down to distinct kinds, not exhaustive by monster instance, but every distinct monster kind the sampling found is included). Heroes is a deduped, type-filtered view of a 393-row table that mixes real collectible heroes with reused stat-blocks for other game modes (PVP dummies, skirmish soldiers); only type=1 (real heroes) plus category enums are included. Units/Troops is genuinely small: the player’s own army has exactly 4 troop “lines” (each a T1–T11 tier progression), not a branching class system, see the table below for confirmation that Infantry/Lancer/Marksman-style class splits don’t exist in this game’s actual data.

​
Full entity catalog (830 entries)

The source dossier ships this catalog as an interactive, client-side search tool (a search box filtering on ID/name/category, plus a domain dropdown, rendering up to the first 300 matches at a time). That live widget isn’t reproduced here. Instead, the full 830-row dataset, the same ent-data JSON data island backing the dossier’s search tool, is broken out below as one Markdown table per domain, in full, since even the largest individual domain (Buildings, 299 rows) is far more readable as a static table than the combined set would be. Each row carries four fields: ID (the numeric value used on the wire or in data tables), Internal name (the Lua enum member or internal string), Display name (the English locale string, where a lookup path exists, - where none was found), and Category (the specific enum table or data-table column the row traces back to).

​
Buildings (299)

​
Monsters (170)

​
Resources (155)

​
Items/Equipment (108)

​
Heroes (66)

​
Units/Troops (32)

Full per-domain methodology, source file:line citations, and known gaps are in each extraction agent’s own notes, not reproduced here for space, but every entry’s category column traces back to a specific enum table or data-table column documented that way.