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\ItemTimer.edfclient file
Total 6Known 0Derived 6Unused 0
Schema
digest: items.md §15.2
Registry level
derived
Derived from
TimerItem.dat
Offset
Field
What it is and how it acts
Assembled from
Server readers
Role
Status
Data
+0x000
number
row number
items.md §15.2
TimerItem.m_dwIndex
—
client
derived
436 values; most often 0 (0%)
+0x004
ID
packed m_strCode; neither the server nor the client uses it
items.md §15.2
TimerItem.m_strCode
—
client
derived
180 values; most often 2164393940 (2%)
+0x008
group
group of the item given
items.md §15.2
TimerItem.m_strLendItemCode
—
client
derived
9 values; most often 17 (50%)
+0x00C
item ID
ID of the item given
items.md §15.2
TimerItem.m_strLendItemCode
—
client
derived
424 values; most often 3490840577 (1%)
+0x010
term kind
as is
items.md §15.2
TimerItem.m_nCheckType
—
client
derived
2 values; most often 2 (64%)
+0x014
term
term in seconds
items.md §15.2
TimerItem.m_nUseTime
—
client
derived
24 values; most often 14400 (32%)
script\TimerItem.datserver file
Total 5Known 5Derived 0Unused 0
Schema
Scripts\strs AOP\TimeItem.strs
Registry level
ready for full
Digest
items.md §15.1
Offset
Field
What it is and how it acts
Goes to client as
Server readers
Role
Status
Data
+0x000
m_dwIndex
row number
items.md §15.1 (digest row)
—
—
—
known
407 values; most often 0 (0%)
+0x004
m_strCode
row code; the server does not read it — the field goes to the client file
items.md §15.1 (digest row); client — from the manual data of the “Client” column
—
—
—
known
407 values; most often tires01 (0%)
+0x044
m_strLendItemCode
item given for a limited time
items.md §15.1 (digest row)
—
—
—
known
407 values; most often ircsa05 (0%)
+0x084
m_nCheckType
0 — no term; 1 and 2 — see 15.3
items.md §15.1 (digest row)
—
—
—
known
2 values; most often 2 (61%)
+0x088
m_nUseTime
term in seconds
items.md §15.1 (digest row)
—
—
—
known
21 values; most often 14400 (34%)
Unused parameters
This category has no unused parameters: every field is read by the server, the client or the build.