Skip to content
RF DataData reference
RU

Items · Consumables

Recovery

Total 28 Known 24 Derived 0 Unused 4

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

Total 28 Known 24 Derived 0 Unused 4
Schema
Scripts\strs AOP\RecoveryItem.strs
Registry level
ready for full
Digest
items.md §13; all fields — items-fields.md
Corrections to the digest
  • items.md: §13: RecoveryItem.strs has two m_nMinRecoveryPro fields; the second (+0x13C) is the maximum
OffsetFieldWhat it is and how it actsGoes to client asServer readersRoleStatusData
+0x000m_dwIndex
row number; also the item number in the DB key (3.1)
items-fields.md, Table 30
+0x0possibly: 140065140 1400655A0 14006F980 +14keyknown14 values; most often 0 (7%)
+0x004m_strCode
item code; the client ID is the packed code (2)
items-fields.md, Table 30
+0x04 ID (packing, 2)140025C20keyknown14 values; most often rebbb01 (7%)
+0x044m_bExist
row is active (section 6)
items-fields.md, Table 30
+0x881400173B0 1401DDDE0server + clientknownalways 1
+0x048m_strModel
model: hex string → client u32 (models.md)
items-fields.md, Table 30
+0x48 hex (models.md)—clientknownalways ``
+0x088m_nIconIDX
icon (sprites.md)
items-fields.md, Table 30
+0x4C—clientknown7 values; most often 83 (21%)
+0x08Cm_strName
name; the server overwrites it from <table>_str.dat, the client takes it from NDItem.edf (6, 1)
items-fields.md, Table 30
+0x08 from NDItem.edf140015DE0keyknown13 values; most often Experience Point100% RecoverCapsule[Premium] (14%)
+0x0D4m_strCivil
race mask, a character per race (8)
items-fields.md, Table 30
+0x50 bytes140015690server + clientknownalways 11111
+0x114m_nLevelLim
level requirement
items-fields.md, Table 30
—140025C20serverknownalways 1
+0x118m_nUpLevelLim
upper level limit, −1 — none
items-fields.md, Table 30
+0x94140025C20server + clientknownalways -1
+0x11Cm_nMoney
price currency (8)
items-fields.md, Table 30
+0x59 (byte)140011880 1400122A0 140012C50 140013600 +1server + clientknown2 values; most often 1 (79%)
+0x120m_nStdPrice
price; the buy-back is based on it too (8)
items-fields.md, Table 30
+0x5C140013FB0server + clientknown4 values; most often 10 (43%)
+0x124m_nStdPoint
price in the PvP purse (currencies 2, 3)
items-fields.md, Table 30
+0x60140011880server + clientknownalways 0
+0x128m_nGoldPoint
price in gold points (currency 6)
items-fields.md, Table 30
+0x64140013600server + clientknownalways 0
+0x12Cm_nKillPoint
price in hunting points (currency 5)
items-fields.md, Table 30
+0x6C140012C50server + clientknownalways 0
+0x130m_nProcPoint
price in processing points (currency 4)
items-fields.md, Table 30
+0x681400122A0server + clientknownalways 0
+0x134m_nStoragePrice
warehouse storage price
items-fields.md, Table 30
+0x701400149B0server + clientknown3 values; most often 50 (57%)
+0x138m_nMinRecoveryPro
minimum v: experience += v / 100 × CPlayerDB+0x2F (140025C20), v = rand() % (max − min + 1) + min
items.md §17.5
———known6 values; most often 10 (33%)
+0x13Cm_nMinRecoveryPro
maximum v (mistakenly a second m_nMinRecoveryPro in the schema)
items.md §17.5
———known5 values; most often 100 (42%)
+0x140m_bSell
can be sold to NPC (6)
items-fields.md, Table 30
+0x7814001A430server + clientknownalways 1
+0x144m_bExchange
can be traded (6)
items-fields.md, Table 30
+0x7414001ABB0server + clientknown2 values; most often 1 (86%)
+0x148m_bGround
can be dropped (6)
items-fields.md, Table 30
+0x7C140016C20server + clientknown2 values; most often 1 (86%)
+0x14Cm_bStoragePossible
can be stored in the warehouse (6)
items-fields.md, Table 30
+0x80140017BA0server + clientknown2 values; most often 1 (86%)
+0x194m_bIsCash
cash item (log, cash shop)
items-fields.md, Table 30
+0x8C14001A090server + clientknown2 values; most often 0 (93%)
+0x198m_bIsTime
timed item; required for TimerItem.dat rows (15.1)
items-fields.md, Table 30
+0x90—clientknownalways 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\RecoveryItem.dat server file

OffsetFieldWhy unusedData
+0x0CCm_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 207
+0x0D0m_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 200
+0x150m_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
+0x154m_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)
14 values; most often trebbb01 (7%)

← Back to category

RF Online is a trademark of its owners. The reference is compiled from research for content development. Built 01.11.2026 · field catalog dated 29.10.2026 · Adagio UI 0.5.0