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.
DataTable\ItemPremium.edfclient file
Total 10Known 0Derived 8Unused 2
Schema
digest: items.md §16.2
Registry level
derived
Derived from
PcRoom.dat
Offset
Field
What it is and how it acts
Assembled from
Server readers
Role
Status
Data
+0x000
number
row number
items.md §16.2
PcRoom.m_dwIndex
—
client
derived
763 values; most often 0 (0%)
+0x004
used
as is
items.md §16.2
PcRoom.m_bUse
—
client
derived
always 1
+0x008
choice: groups ×50
choice item groups, 5 × 10 (FF — empty)
items.md §16.2
PcRoom.m_itmSelect
—
client
derived
5 values; most often 17 / 17 / 17 / 17 … (42%)
+0x03C
choice: ID ×50
IDs of choice items (FFFFFFFF — empty)
items.md §16.2
PcRoom.m_itmSelect
—
client
derived
7 values; most often 3255763457 / 3255763458 / 3473016577 / 3473016579 … (42%)
+0x104
choice: count ×5
m_nSelectNumber of the five lists (FF = −1)
items.md §16.2
PcRoom.m_nSelectNumber
—
client
derived
2 values; most often 1 / 1 / 255 / 255 … (58%)
+0x109
fixed: groups ×10
groups of fixed items
items.md §16.2
PcRoom.m_itmFix
—
client
derived
2 values; most often 8 / 6 / 255 / 255 … (58%)
+0x114
fixed: ID ×10
IDs of fixed items
items.md §16.2
PcRoom.m_itmFix
—
client
derived
66 values; most often 3238986241 / 3289317889 / 4294967295 / 4294967295 … (20%)
+0x13C
fixed: count ×10
m_nFixNumber, byte
items.md §16.2
PcRoom.m_nFixNumber
—
client
derived
2 values; most often 1 / 1 / 255 / 255 … (58%)
script\PcRoom.datserver file
Total 8Known 8Derived 0Unused 0
Schema
Scripts\strs AOP\PcRoom.strs
Registry level
ready for full
Digest
items.md §16.1
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 number in packets
items.md §16.1 (digest row)
—
—
—
known
763 values; most often 0 (0%)
+0x004
m_strCode
row key: class and level (16.3), e.g. bw01, af30
items.md §16.1 (digest row)
—
—
—
known
763 values; most often aw01 (0%)
+0x044
m_bUse
1 in all rows; not read in the analysed server and client functions
items.md §16.1 (digest row)
—
—
—
known
always 1
+0x048
m_strEventName
human-readable caption in CP949: “벨라토 워리어(1-20)” etc.; never read
5 values; most often ircpc01 / ircpc02 / irpch01 / irpch03 … (42%)
+0x0D8
m_nSelectNumber ×5
—
items.md §16.2 (digest row)
—
—
—
known
2 values; most often 1 / 1 / -1 / -1 … (58%)
+0x22C
m_itmFix ×10
10 fixed items: code
items.md §16.1
—
—
—
known
66 values; most often ikbpc01 / iwepc01 / -1 / -1 … (20%)
+0x234
m_nFixNumber ×10
—
items.md §16.2 (digest row)
—
—
—
known
2 values; most often 1 / 1 / -1 / -1 … (58%)
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.
DataTable\ItemPremium.edfclient file
Offset
Field
Why unused
Data
+0x113
(byte)
padding
items.md §17.5; unused: padding bytes (after a byte field up to the field at the next multiple of 4; unnamed bytes have no reads in MSVC code except whole-record copies; 2004 source citemdatamgr.h); 0 everywhere in AoP
always 0
+0x146
(tail) ×2
padding
items.md §17.5; unused: padding bytes (after a byte field up to the field at the next multiple of 4; unnamed bytes have no reads in MSVC code except whole-record copies; 2004 source citemdatamgr.h); 0 everywhere in AoP