MAU keys

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\UnitKeyItem.dat` server file

Total 14 Known 12 Derived 0 Unused 2

Schema: Scripts\strs AOP\UnitKeyItem.strs
Registry level: ready for full
Digest: items.md §12; 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 19	+0x0 ~	possibly: `140065140` `1400655A0` `14006F980` +14	key	known	4 values; most often `0` (25%)
`+0x004`	`m_strCode`	item code; the client ID is the packed code (2) items-fields.md, Table 19	+0x04 ID (packing, 2)	possibly: `140011440` `140041060` `14006A9D0` +84	key	known	4 values; most often `inbbb01` (25%)
`+0x044`	`m_bExist`	row is active (section 6) items-fields.md, Table 19	+0x88	`1400173B0` `1401DDDE0`	server + client	known	always `1`
`+0x048`	`m_strModel`	model: hex string → client u32 (models.md) items-fields.md, Table 19	+0x48 hex (models.md)	—	client	known	4 values; most often `730700` (25%)
`+0x088`	`m_nIconIDX`	icon (sprites.md) items-fields.md, Table 19	+0x4C	—	client	known	4 values; most often `1` (25%)
`+0x08C`	`m_strName`	name; the server overwrites it from `<table>_str.dat`, the client takes it from `NDItem.edf` (6, 1) items-fields.md, Table 19	+0x08 from `NDItem.edf`	`140015DE0`	key	known	3 values; most often `Translation` (50%)
`+0x0CC`	`m_strCivil`	race mask, a character per race (8) items-fields.md, Table 19	+0x50 bytes	`140015690`	server + client	known	always `11000`
`+0x10C`	`m_nFRAType`	MAU frame (mau.md) items-fields.md, Table 19	+0x0 ~, +0x84, +0x98	`1400C1DA0`	server + client	known	4 values; most often `0` (25%)
`+0x110`	`m_bSell`	can be sold to NPC (6) items-fields.md, Table 19	+0x78	`14001A430`	server + client	known	always `1`
`+0x114`	`m_bExchange`	can be traded (6) items-fields.md, Table 19	+0x74	`14001ABB0`	server + client	known	always `0`
`+0x118`	`m_bGround`	can be dropped (6) items-fields.md, Table 19	+0x7C	`140016C20`	server + client	known	always `0`
`+0x11C`	`m_bStoragePossible`	can be stored in the warehouse (6) items-fields.md, Table 19	+0x80	—	client	known	always `0`

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\UnitKeyItem.dat` server file

Offset	Field	Why unused	Data
`+0x120`	`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`
`+0x124`	`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)	4 values; most often `tinbbb01` (25%)

Used parameters

script\UnitKeyItem.dat server file

Unused parameters

script\UnitKeyItem.dat server file

`script\UnitKeyItem.dat` server file

`script\UnitKeyItem.dat` server file