Skip to content
RF DataData reference
RU

Items and economy

Upgrade

Talics and jewels: ItemUpgrade.dat

Total 24 Known 24 Derived 0 Unused 0

Overview

Item upgrading is inserting talics into equipment sockets, and jewels that raise the chance. Everything is defined by one server table, Script\ItemUpgrade.dat; the client takes upgrade data from resource records in Item.edf.

What it consists of

  • Talics — rows 0–12 of ItemUpgrade.dat (irtal01…13), row 13 is the “restoration talic” (talic removal). The talic kind is the row number: what a talic does is hard-coded in the server by kind, new kinds cannot be added through data.
  • Jewels — rows with m_nJewelType ≠ 0: ruby, crystal, topaz, obsidian and “creation stones”; m_fJewelFieldValue is the jewel's contribution to the chance.
  • The limits m_nUpperUp … m_nClockUp — how many talics of the kind fit into each equipment part; m_fUp1…7 — the effect amount with 1–7 talics.

How it works

  • Request 7/17 (insertion): the server checks the item's sockets and the per-part limits and computes the chance from the item's grade and level, the number of talics already inserted and the set of jewels. The success, burn and reset tables are hard-coded; on Sirin Lua overrides them.
  • Request 7/19 (removal): the server returns the resource with number “kind + 20”, so irtal01…13 must occupy rows 20–32 of ResourceItem.dat.
  • Talic effects by kind are applied by a server function with constants; m_nDataEffect is the effect number for the client (kind + 1 for talics, 14 for the restoration talic).

What matters when editing

  • The order of rows 0–12 must not change; every row references an existing resource.
  • Grade 8 burns on any failure; the seventh socket (m_nUpgrade = 7) cannot be filled.

Files of the category

1 in the registry
FileSideFormatLevelCorporaRecordDigestNote
script\ItemUpgrade.datserverdatready for fullAoP ✓, GU ✓, Sirin ✓AoP 216, GU 216, Sirin 216upgrade.mdupgrade.md §1

“ready for full” — the format is understood and the fields are described; “derived” — the file is assembled from another; “opaque” — the format is not fully known; “postponed” and “out of scope” — the studio does not edit the file.

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

Total 24 Known 24 Derived 0 Unused 0
Schema
Scripts\strs AOP\ItemUpgrade.strs
Registry level
ready for full
Digest
upgrade.md §1
OffsetFieldWhat it is and how it actsGoes to client asServer readersRoleStatusData
+0x000m_dwIndex
kind: for talics 0–12 it determines what the talic does (section 4)
upgrade.md §1 (digest row)
———known38 values; most often 0 (3%)
+0x004m_strCode
resource code (irtal01, irgef01…); linked to ResourceItem.dat by code
upgrade.md §1 (digest row)
———known38 values; most often irtal01 (3%)
+0x044m_strName
Korean name
upgrade.md §1 (digest row)
———known38 values; most often ¹«ÁöÀÇ Å»¸¯ (3%)
+0x084m_nJewelType
0 for talics; for jewels 1 ruby, 2 crystal, 4 topaz, 8 obsidian, 10 “creation stone”
upgrade.md §1 (digest row)
———known5 values; most often 0 (37%)
+0x088m_fJewelFieldValue
jewel contribution to the chance (section 3.2)
upgrade.md §1 (digest row)
———known7 values; most often 0 (37%)
+0x08Cm_nUpperUp
how many talics of this kind fit in a part: upper, lower, gauntlets, shoes, helmet, shield, melee, ranged, MAU, cloak (items.md, 12.4)
upgrade.md §1 (digest row)
———known3 values; most often 1 (66%)
+0x090m_nLowerUp
how many talics of this kind fit in a part: upper, lower, gauntlets, shoes, helmet, shield, melee, ranged, MAU, cloak (items.md, 12.4)
upgrade.md §1 (digest row)
———known3 values; most often 1 (66%)
+0x094m_nGauntletUp
how many talics of this kind fit in a part: upper, lower, gauntlets, shoes, helmet, shield, melee, ranged, MAU, cloak (items.md, 12.4)
upgrade.md §1 (digest row)
———known3 values; most often 1 (66%)
+0x098m_nShoeUp
how many talics of this kind fit in a part: upper, lower, gauntlets, shoes, helmet, shield, melee, ranged, MAU, cloak (items.md, 12.4)
upgrade.md §1 (digest row)
———known3 values; most often 1 (66%)
+0x09Cm_nHelmetUp
how many talics of this kind fit in a part: upper, lower, gauntlets, shoes, helmet, shield, melee, ranged, MAU, cloak (items.md, 12.4)
upgrade.md §1 (digest row)
———known3 values; most often 1 (66%)
+0x0A0m_nShieldUp
how many talics of this kind fit in a part: upper, lower, gauntlets, shoes, helmet, shield, melee, ranged, MAU, cloak (items.md, 12.4)
upgrade.md §1 (digest row)
———known3 values; most often 1 (66%)
+0x0A4m_nMeleeUp
how many talics of this kind fit in a part: upper, lower, gauntlets, shoes, helmet, shield, melee, ranged, MAU, cloak (items.md, 12.4)
upgrade.md §1 (digest row)
———known3 values; most often 1 (76%)
+0x0A8m_nMissileUp
how many talics of this kind fit in a part: upper, lower, gauntlets, shoes, helmet, shield, melee, ranged, MAU, cloak (items.md, 12.4)
upgrade.md §1 (digest row)
———known3 values; most often 1 (66%)
+0x0ACm_nUnitUp
how many talics of this kind fit in a part: upper, lower, gauntlets, shoes, helmet, shield, melee, ranged, MAU, cloak (items.md, 12.4)
upgrade.md §1 (digest row)
———known3 values; most often 1 (66%)
+0x0B0m_nClockUp
how many talics of this kind fit in a part: upper, lower, gauntlets, shoes, helmet, shield, melee, ranged, MAU, cloak (items.md, 12.4)
upgrade.md §1 (digest row)
———known3 values; most often 1 (66%)
+0x0B4m_nDataEffect
effect number for the client: for talics — kind + 1 (1–14); 14 — “restoration talic” (removal, section 5)
upgrade.md §1 (digest row)
———known15 values; most often 0 (63%)
+0x0B8m_nEffectUnit
1 or 2; the server does not read it in the analysed functions, it does not go to the client
upgrade.md §1 (digest row)
———known3 values; most often 0 (66%)
+0x0BCm_fUp1
effect amount with 1–7 talics of this kind in the item
upgrade.md §1 (+0xBC), §4
Item.edf (resource) +0xEC…—server → clientknown6 values; most often 0 (66%)
+0x0C0m_fUp2
effect amount with 1–7 talics of this kind in the item
upgrade.md §1 (+0xBC), §4
Item.edf (resource) +0xEC…—server → clientknown7 values; most often 0 (66%)
+0x0C4m_fUp3
effect amount with 1–7 talics of this kind in the item
upgrade.md §1 (+0xBC), §4
Item.edf (resource) +0xEC…—server → clientknown7 values; most often 0 (66%)
+0x0C8m_fUp4
effect amount with 1–7 talics of this kind in the item
upgrade.md §1 (+0xBC), §4
Item.edf (resource) +0xEC…—server → clientknown7 values; most often 0 (66%)
+0x0CCm_fUp5
effect amount with 1–7 talics of this kind in the item
upgrade.md §1 (+0xBC), §4
Item.edf (resource) +0xEC…—server → clientknown6 values; most often 0 (66%)
+0x0D0m_fUp6
effect amount with 1–7 talics of this kind in the item
upgrade.md §1 (+0xBC), §4
Item.edf (resource) +0xEC…—server → clientknown7 values; most often 0 (66%)
+0x0D4m_fUp7
effect amount with 1–7 talics of this kind in the item
upgrade.md §1 (+0xBC), §4
Item.edf (resource) +0xEC…—server → clientknown6 values; most often 0 (66%)

Unused parameters

This category has no unused parameters: every field is read by the server, the client or the build.

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