Items · Summons and siege

Animus items

The animus item table; the level tables are in the “Animus” category.

Total 23 Known 18 Derived 0 Unused 5

Used parameters

Fields read by the server or the client, or assembled from other files. The description says what the field means and how it acts; below it — where that was established.

`script\AnimusItem.dat` server file

Total 23 Known 18 Derived 0 Unused 5

Schema: Scripts\strs AOP\AnimusItem.strs
Registry level: ready for full
Digest: items.md §13; all fields — items-fields.md

Offset	Field	What it is and how it acts	Goes to client as	Server readers	Role	Status	Data
`+0x000`	`m_dwIndex`	row number; also the item number in the DB key (3.1) items-fields.md, Table 24	+0x0	possibly: `140065140` `1400655A0` `14006F980` +14	key	known	8 values; most often `0` (12%)
`+0x004`	`m_strCode`	item code; the client ID is the packed code (2) items-fields.md, Table 24	+0x04 ID (packing, 2)	`1401BB1E0` `1401BC430`	key	known	8 values; most often `ijccc01` (12%)
`+0x044`	`m_strModel`	model: hex string → client u32 (models.md) items-fields.md, Table 24	+0x48 hex (models.md)	`1401DDDE0`	server + client	known	8 values; most often `840600` (12%)
`+0x084`	`m_nIconIDX`	icon (sprites.md) items-fields.md, Table 24	+0x4C	—	client	known	8 values; most often `1` (12%)
`+0x088`	`m_strCivil`	race mask, a character per race (8) items-fields.md, Table 24	+0x50 bytes	`140015690`	server + client	known	always `00110`
`+0x0C8`	`m_strName`	name; the server overwrites it from `<table>_str.dat`, the client takes it from `NDItem.edf` (6, 1) items-fields.md, Table 24	+0x08 from `NDItem.edf`	`140015DE0`	key	known	8 values; most often `Paimon` (12%)
`+0x10C`	`m_nAnimusType`	animus kind (animus.md) items-fields.md, Table 24	—	`1400946A0` `1400B8AF0`	server	known	2 values; most often `0` (50%)
`+0x118`	`m_nMoney`	price currency (8) items-fields.md, Table 24	+0x59 (byte)	`140011880` `1400122A0` `140012C50` `140013600` +1	server + client	known	always `0`
`+0x11C`	`m_nStdPrice`	price; the buy-back is based on it too (8) items-fields.md, Table 24	+0x5C	`140013FB0`	server + client	known	always `250000`
`+0x120`	`m_nStdPoint`	price in the PvP purse (currencies 2, 3) items-fields.md, Table 24	+0x60	`140011880`	server + client	known	always `0`
`+0x124`	`m_nGoldPoint`	price in gold points (currency 6) items-fields.md, Table 24	+0x64	`140013600`	server + client	known	always `0`
`+0x128`	`m_nKillPoint`	price in hunting points (currency 5) items-fields.md, Table 24	+0x6C	`140012C50`	server + client	known	always `0`
`+0x12C`	`m_nProcPoint`	price in processing points (currency 4) items-fields.md, Table 24	+0x68	`1400122A0`	server + client	known	always `0`
`+0x130`	`m_nStoragePrice`	warehouse storage price items-fields.md, Table 24	+0x70	`1400149B0`	server + client	known	always `12500`
`+0x134`	`m_bSell`	can be sold to NPC (6) items-fields.md, Table 24	+0x78	`14001A430`	server + client	known	always `1`
`+0x138`	`m_bExchange`	can be traded (6) items-fields.md, Table 24	+0x74	`14001ABB0`	server + client	known	always `1`
`+0x13C`	`m_bGround`	can be dropped (6) items-fields.md, Table 24	+0x7C	`140016C20`	server + client	known	always `1`
`+0x140`	`m_bStoragePossible`	can be stored in the warehouse (6) items-fields.md, Table 24	+0x80	`140017BA0`	server + client	known	always `1`

Unused parameters

Fields that neither the server nor the client reads. For each: why it was decided so and where that was established. The editor keeps their bytes as they are.

`script\AnimusItem.dat` server file

Offset	Field	Why unused	Data
`+0x108`	`m_nAnimusClass`	animus class (animus.md) items-fields.md: role “nobody” — no server reads found (`dataflow\wflow_<t>`, `wcase_<t>`, tower/trap objects; coverage incomplete) and the field is absent from the `Item.edf` record (`cmatch.py` check on AoP)	4 values; most often `1` (25%)
`+0x110`	`m_nKindClt`	“kind, client” (2004); does not go to the client, the model matters (7.1) items-fields.md: role “nobody” — no server reads found (`dataflow\wflow_<t>`, `wcase_<t>`, tower/trap objects; coverage incomplete) and the field is absent from the `Item.edf` record (`cmatch.py` check on AoP)	always `406`
`+0x114`	`m_nFixPart`	“equip slot”; for weapons 8/100 — one-/two-handed (7.1), constant per table for the rest items-fields.md: role “nobody” — no server reads found (`dataflow\wflow_<t>`, `wcase_<t>`, tower/trap objects; coverage incomplete) and the field is absent from the `Item.edf` record (`cmatch.py` check on AoP)	always `300`
`+0x144`	`m_bUseableNormalAcc`	common flag; unused items.md §17.5: the getter `1400182C0` has no references from code (Ghidra: only `.pdata`); `itemflow.py` over 37 tables (GetRecord, record array `+0xA0`, arguments) — no direct reads; the consumers of 14 record storage places were checked; Sirin — only a type description; the field is absent from the client `Item.edf` record	always `1`
`+0x148`	`m_strTooltipIndex`	description code; for equipment the client stores the description number `+0x84` (7.3) items-fields.md: role “nobody” — no server reads found (`dataflow\wflow_<t>`, `wcase_<t>`, tower/trap objects; coverage incomplete) and the field is absent from the `Item.edf` record (`cmatch.py` check on AoP)	8 values; most often `tijccc01` (12%)

← Back to category

Animus items

Used parameters

script\AnimusItem.dat server file

Unused parameters

script\AnimusItem.dat server file

`script\AnimusItem.dat` server file

`script\AnimusItem.dat` server file