Raynegard Wiki - User contributions [en]

Textdata NN.dat

2026-07-02T23:39:44Z

0:0:0:0:0:0:0:1: /* Record types */

'''<code>NN.dat</code>''' (part of [[BIN textdata]]) is the numbered family of item/NPC/monster object-definition files (<code>5.dat</code>, <code>8.dat</code>, <code>16.dat</code>, … <code>92.dat</code>). Despite the <code>.dat</code> extension every file is plain CP949 text.

== Record format ==

Each file is line-based:

<pre>
<record count>
<Korean name> ┐
<English name> ├ one record = 3 lines
<stat line: space-separated ints> ┘
… repeated <count> times
</pre>

Example (<code>8.dat</code>, record 1, a ring): <code>레인가 루지아</code> / <code>Reynega_rugia</code> / <code>8 1 1 1 22 492 100000 5000 0 0 0 0 0 0</code>.

== Loading pipeline ==

* <code>Struct_Setup_DatFiles @ 00483ff0</code> — loops all 60 slots, each calling <code>TextArchive_Load_Dat_From_Array @ 00484080</code>, which reads the count then the 3 lines per record.
* <code>TextFile_Dat_FileNum_to_value @ 00485760</code> — the authoritative <code>NN.dat</code> → slot-index switch (see [[BIN textdata]] for context).
* <code>DatFiles_FileNum_value_to_DatType @ 00485650</code> — slot value (0–59) → one of 14 record types (<code>Dat_Type</code> 0–0xD).
* <code>Vtable_DatFiles_DecodeFuncs[Dat_Type] @ 00485618</code> — a 14-entry table of per-type decoders. Each decoder <code>sscanf</code>s an exact number of stat-line fields, <code>operator_new</code>s the record, and copies the parsed columns into it. Decoders are recursive (decode one record, tail-call the next).
* <code>TextDatFiles_GetSlotEntry(g_TextDatFiles, datEnum, idx) @ 00485ac0</code> — runtime fetch of record <code>idx</code> from a loaded slot.

== Record types ==

{| class="wikitable"
! Type !! Decoder !! Category !! <code>.dat</code> files !! Stat cols !! Carries
|-
| 0 || <code>0048422b</code> || [[Weapons]] (katana/sword/axe/spear/bow/bowgun) || 16–22, 62, 63 || 44 || header + 6 stats + weapon block
|-
| 1 || <code>0048453f</code> || [[Armor]] || 23–31, 61 || 16 || header + 6 stats + sprite/variant
|-
| 2 || <code>0048468c</code> || [[Rings]] || 8, 32 || 14 || header + 6 stats
|-
| 3 || <code>004847b7</code> || [[Emblems]] || 9, 33 || 8 || header only (no stats)
|-
| 4 || <code>00484882</code> || Medicine / food || 10, 11, 34 || 10–11 || header + recovery + effect name
|-
| 5 || <code>0048496d</code> || Money || 15 || 8 || header (no price)
|-
| 6 || <code>00484a18</code> || Scrolls || 38–43 || 33 || header + skill/effect params
|-
| 7 || <code>00484bd9</code> || Books || 44–47 || 8 || header only
|-
| 8 || <code>00484c80</code> || Misc items (ore / monster-item / letter) || 35, 36, 37, 48, 49 || 8 || header only
|-
| 9 || <code>00484d33</code> || Monsters || 64–69, 73, 78, 79 || 32 (31 parsed) || monster block
|-
| 0xA || <code>00484f8b</code> || Monster (special) || 70 || 36 || monster block (extended)
|-
| 0xB || <code>00485235</code> || NPCs (field/party) || 5, 74, 75 || 8 || header + refs (no shop)
|-
| 0xC || <code>00485305</code> || NPC shopkeepers (incl. Au) || 77 || 22 (21 parsed) || header + shop-type + category flags
|-
| 0xD || <code>004854f8</code> || Monsters || 89–92 || ~3 || sparse / mostly empty
|}

'''Item vs entity split:''' only weapon/armor/ring carry the 6-stat block. Emblem, money, book, and misc items are header-only (8 cols) — a name + price, nothing more. Consumables add a recovery value + an effect-name string; scrolls add skill params. Monsters/NPCs use the entity layout instead of the item layout.

== Common header (every record) ==

Built by the root constructor <code>DatRecord_InitHeader @ 00483e80</code>:

{| class="wikitable"
! Offset !! Type !! Field
|-
| <code>0x00</code> || <code>char[0x10]</code> || Korean name (CP949)
|-
| <code>0x11</code> || <code>char[0x10]</code> || English name (<code>_</code> → space)
|-
| <code>0x24</code> || int || col1 = dat file number
|-
| <code>0x28</code> || int || col2 = record index (1-based)
|}

== Column → offset mapping ==

The constructors copy parsed columns sequentially into 4-byte fields starting at <code>0x24</code>:

: '''col<sub>n</sub> → record offset <code>0x24 + 4·(n − 1)</code>''' (col1→<code>0x24</code>, col2→<code>0x28</code>, col3→<code>0x2c</code>, …)

Verified by the weapon record: 44 cols, last field at <code>0x24 + 4·43 = 0xd0</code>. A few fields are single bytes rather than ints.

=== Item families (weapon / armor / ring / emblem / consumable / scroll / book / misc) ===

Share the item base (<code>ItemRecord_InitBase @ 004862c0</code> → <code>…_InitBase2 @ 00486a30</code>), which fills <code>0x2c–0x40</code>, then a per-type extension:

* '''Ring''' (<code>RingRecord_Init @ 00486930</code>): +<code>0x44–0x58</code> → 14 fields total (<code>0x24</code>–<code>0x58</code>).
* '''Armor''' (<code>ArmorRecord_Init @ 004861b0</code>): +<code>0x44–0x60</code> → 16 fields.
* '''Weapon''' (<code>WeaponRecord_Init @ 00486b10</code>): +<code>0x44–0xd0</code> → 44 fields; a byte at <code>0x68</code> (col 18), plus a run of ~15 id-like values (col 26+) that look like sprite/effect/skill references.

=== Entities (NPC / monster) ===

Use the root header (<code>0x24</code>/<code>0x28</code>) then category fields from <code>0x2c</code>:

* '''Monster''' (<code>MonsterRecord_Init @ 00485c10</code>): <code>0x2c</code> (byte) then ints <code>0x30–0x9c</code> — 29 fields (31 parsed; the 32nd column on the line isn't read). Example <code>64.dat</code> "Weldok": <code>64 1 36 1 0 0 620 62 79 354 … 160 120 100 350 50 85 150 233 61 …</code>. HP/stats not yet labelled (consumed server-side).
* '''NPC''' (<code>NpcRecord_Init @ 00485f90</code>, via <code>NpcRecord_InitBase @ 004860d0</code>): ints <code>0x2c</code>/<code>0x30</code>, a byte <code>0x34</code>, ints <code>0x38–0x40</code>, then a 14-byte block <code>0x44–0x51</code>. Example <code>77.dat</code> "Noick": <code>77 1 121 85 0 0 75 57 0 …</code>.

== Common header columns (cols 1–8, item records) ==

{| class="wikitable"
! Col !! Offset !! Meaning !! Confidence
|-
| 1 || <code>0x24</code> || dat file number || confirmed
|-
| 2 || <code>0x28</code> || record index (1-based) || confirmed
|-
| 3 || <code>0x2c</code> || sub-type / grade (small: 0–3) || tentative
|-
| 4 || <code>0x30</code> || sub-type / grade (small) || tentative
|-
| 5 || <code>0x34</code> || item level / sort key (e.g. 22, 47, 52) || tentative
|-
| 6 || <code>0x38</code> || icon bitmap index || confirmed (leader-emblem icon)
|-
| 7 || <code>0x3c</code> || buy price || confirmed (shop gold check)
|-
| 8 || <code>0x40</code> || sell price || inferred (buy/sell pair)
|}

Header-only items (emblem/money/book/misc, 8 cols) end here. Money (<code>15.dat</code>) has <code>col7=col8=0</code> — it ''is'' currency, no price. Equippables continue with the 6-stat block below.

== The 6 equip stat columns (confirmed) ==

Every equippable item record carries six stats at a fixed offset block <code>0x44–0x58</code> (cols 9–14), confirmed from the stat-display builder <code>FUN_004bacb0</code> (the item-detail panel):

{| class="wikitable"
! Col !! Offset !! Stat
|-
| col9 || <code>0x44</code> || '''OFC''' — offense / attack
|-
| col10 || <code>0x48</code> || '''DEF''' — defense
|-
| col11 || <code>0x4c</code> || '''AGL''' — agility
|-
| col12 || <code>0x50</code> || '''LUCK'''
|-
| col13 || <code>0x54</code> || '''LIFE'''
|-
| col14 || <code>0x58</code> || '''FOOD'''
|}

The on-screen order differs from the record order — the header (<code>misccaption_u.txt</code> line 1) reads <code>LIFE FOOD OFC DEF AGL LUCK</code>, and <code>FUN_004bacb0</code> re-orders fields to match. It prints two rows: the item's stat values, and a '''SPEC''' row (<code>misccaption_u.txt</code> line 2) with the <code>%+d</code> equip delta.

Cross-checks: rings (<code>8.dat</code>) only ever set cols 9–12 (OFC/DEF/AGL/LUCK), never LIFE/FOOD; armor <code>23.dat</code> col10 = DEF (main stat), col11 = AGL; weapon <code>16.dat</code> katana col9 = 110 (OFFENSE), col11 = 65 (AGL). These offsets are identical across item types — weapons carry the same 6 at <code>0x44–0x58</code>, plus their weapon-specific columns beyond.

== Weapon block (cols 15–44, <code>0x5c</code>–<code>0xd0</code>) ==

Example <code>16.dat</code> katana: <code>… 9 120 0 1 2 148 0 255 0 0 0 | 463 436 489 490 491 492 589 590 539 540 541 542 601 602 | 2 1 38 1 0</code>.

* '''cols 15–25''' — weapon params (attack range/speed/hit-rate class; <code>0x68</code>/col18 is a byte). Consumed by the attack/combat path (server-side for damage).
* '''cols 26–39''' — a run of 14 sprite/animation sequence ids (<code>463…602</code>, in the sprite-archive range) — the weapon's swing/effect frames, loaded by the animation system on equip.
* '''cols 40–44''' — display/misc; col42 (<code>0xc8</code>) = catalog icon (read by <code>Stuct_Setup_cpt_panel_catalog</code>).

== Consumables / scrolls ==

* '''Consumable''' (type 4, 10–11 cols): header + col9 = recovery amount (e.g. food <code>600</code>) + a trailing effect/skill-name string.
* '''Scroll''' (type 6, 33 cols): header + col9…col15 = skill/effect params (skill id, power, level req), rest padding.

== Monster block (<code>0x2c–0x9c</code>, ~30 fields) ==

<code>MonsterRecord_Init</code> writes cols 3+ as HP / base stats / AI / drop data. These are read by the '''server''' combat/AI — the client only uses the monster record for its sprite/name — so the columns aren't labelled here.

== Confirmed column labels (field-consumer trace) ==

{| class="wikitable"
! Record !! Col / offset !! Meaning !! Evidence
|-
| Item (all types) || col7 = <code>0x3c</code> || buy price || <code>State_NpcShopBuy_Tick @ 00467fd0</code>: buy allowed only if <code>record->0x3c <= player.money</code>, then sends <code>0x35</code>. Ring col7=100000, weapon 9000, matches.
|-
| Item || col8 = <code>0x40</code> || sell price (inferred) || Not consumer-confirmed, but the buy/sell pair — ring col8=5000 vs buy 100000; weapon col8=900 vs buy 9000.
|-
| NPC/shop (type 0xB/0xC) || col7 = <code>0x3c</code> || shop-type code || <code>State_NpcShopBuy_Tick</code> case 0 switches on <code>npcRecord->0x3c</code>, accepts <code>0x44,0x47,0x4a,0x4d,0x50,0x53</code> = letters D G J M P S (shop kinds).
|-
| NPC/shop || cols 9–22 = <code>0x44</code>–<code>0x51</code> (14 bytes) || per-category "sells this" flags || same function loops <code>npcRecord[i + 0x44]</code>, <code>i = 0..13</code>; each nonzero byte adds item-category <code>i</code> to the shop's list (14 categories: Katana…MonsterItem).
|-
| Item / emblem || col6 = <code>0x38</code> || class/icon bitmap index || <code>cpt_panel_status_widget_Draw</code>: for the party-leader emblem (dat 9), <code>record->0x38</code> is passed to <code>File_Read_Bitmap_Archive</code> as the icon image id.
|}

'''Server relevance:''' col7 (buy price) is the value the shop's gold check uses; an equipped item's col9–14 bonuses (OFC/DEF/AGL/LUCK/LIFE/FOOD) are applied to the wearer's totals. The player's ''total'' stats (base + all equipped bonuses) are computed server-side and pushed via packets <code>0xC001</code>/<code>0xC002</code> — the client never re-derives totals from records.

== See also ==

* [[BIN textdata]]
* [[textdata cptNN.txt]] — the flavor-text companion file, paired by dat number

Textdata NN.dat

2026-07-02T23:35:05Z

0:0:0:0:0:0:0:1: /* Record types */

'''<code>NN.dat</code>''' (part of [[BIN textdata]]) is the numbered family of item/NPC/monster object-definition files (<code>5.dat</code>, <code>8.dat</code>, <code>16.dat</code>, … <code>92.dat</code>). Despite the <code>.dat</code> extension every file is plain CP949 text.

== Record format ==

Each file is line-based:

<pre>
<record count>
<Korean name> ┐
<English name> ├ one record = 3 lines
<stat line: space-separated ints> ┘
… repeated <count> times
</pre>

Example (<code>8.dat</code>, record 1, a ring): <code>레인가 루지아</code> / <code>Reynega_rugia</code> / <code>8 1 1 1 22 492 100000 5000 0 0 0 0 0 0</code>.

== Loading pipeline ==

* <code>Struct_Setup_DatFiles @ 00483ff0</code> — loops all 60 slots, each calling <code>TextArchive_Load_Dat_From_Array @ 00484080</code>, which reads the count then the 3 lines per record.
* <code>TextFile_Dat_FileNum_to_value @ 00485760</code> — the authoritative <code>NN.dat</code> → slot-index switch (see [[BIN textdata]] for context).
* <code>DatFiles_FileNum_value_to_DatType @ 00485650</code> — slot value (0–59) → one of 14 record types (<code>Dat_Type</code> 0–0xD).
* <code>Vtable_DatFiles_DecodeFuncs[Dat_Type] @ 00485618</code> — a 14-entry table of per-type decoders. Each decoder <code>sscanf</code>s an exact number of stat-line fields, <code>operator_new</code>s the record, and copies the parsed columns into it. Decoders are recursive (decode one record, tail-call the next).
* <code>TextDatFiles_GetSlotEntry(g_TextDatFiles, datEnum, idx) @ 00485ac0</code> — runtime fetch of record <code>idx</code> from a loaded slot.

== Record types ==

{| class="wikitable"
! Type !! Decoder !! Category !! <code>.dat</code> files !! Stat cols !! Carries
|-
| 0 || <code>0048422b</code> || [[Weapons]] (katana/sword/axe/spear/bow/bowgun) || 16–22, 62, 63 || 44 || header + 6 stats + weapon block
|-
| 1 || <code>0048453f</code> || [[Armor]] || 23–31, 61 || 16 || header + 6 stats + sprite/variant
|-
| 2 || <code>0048468c</code> || [[Rings]] || 8, 32 || 14 || header + 6 stats
|-
| 3 || <code>004847b7</code> || Emblems || 9, 33 || 8 || header only (no stats)
|-
| 4 || <code>00484882</code> || Medicine / food || 10, 11, 34 || 10–11 || header + recovery + effect name
|-
| 5 || <code>0048496d</code> || Money || 15 || 8 || header (no price)
|-
| 6 || <code>00484a18</code> || Scrolls || 38–43 || 33 || header + skill/effect params
|-
| 7 || <code>00484bd9</code> || Books || 44–47 || 8 || header only
|-
| 8 || <code>00484c80</code> || Misc items (ore / monster-item / letter) || 35, 36, 37, 48, 49 || 8 || header only
|-
| 9 || <code>00484d33</code> || Monsters || 64–69, 73, 78, 79 || 32 (31 parsed) || monster block
|-
| 0xA || <code>00484f8b</code> || Monster (special) || 70 || 36 || monster block (extended)
|-
| 0xB || <code>00485235</code> || NPCs (field/party) || 5, 74, 75 || 8 || header + refs (no shop)
|-
| 0xC || <code>00485305</code> || NPC shopkeepers (incl. Au) || 77 || 22 (21 parsed) || header + shop-type + category flags
|-
| 0xD || <code>004854f8</code> || Monsters || 89–92 || ~3 || sparse / mostly empty
|}

'''Item vs entity split:''' only weapon/armor/ring carry the 6-stat block. Emblem, money, book, and misc items are header-only (8 cols) — a name + price, nothing more. Consumables add a recovery value + an effect-name string; scrolls add skill params. Monsters/NPCs use the entity layout instead of the item layout.

== Common header (every record) ==

Built by the root constructor <code>DatRecord_InitHeader @ 00483e80</code>:

{| class="wikitable"
! Offset !! Type !! Field
|-
| <code>0x00</code> || <code>char[0x10]</code> || Korean name (CP949)
|-
| <code>0x11</code> || <code>char[0x10]</code> || English name (<code>_</code> → space)
|-
| <code>0x24</code> || int || col1 = dat file number
|-
| <code>0x28</code> || int || col2 = record index (1-based)
|}

== Column → offset mapping ==

The constructors copy parsed columns sequentially into 4-byte fields starting at <code>0x24</code>:

: '''col<sub>n</sub> → record offset <code>0x24 + 4·(n − 1)</code>''' (col1→<code>0x24</code>, col2→<code>0x28</code>, col3→<code>0x2c</code>, …)

Verified by the weapon record: 44 cols, last field at <code>0x24 + 4·43 = 0xd0</code>. A few fields are single bytes rather than ints.

=== Item families (weapon / armor / ring / emblem / consumable / scroll / book / misc) ===

Share the item base (<code>ItemRecord_InitBase @ 004862c0</code> → <code>…_InitBase2 @ 00486a30</code>), which fills <code>0x2c–0x40</code>, then a per-type extension:

* '''Ring''' (<code>RingRecord_Init @ 00486930</code>): +<code>0x44–0x58</code> → 14 fields total (<code>0x24</code>–<code>0x58</code>).
* '''Armor''' (<code>ArmorRecord_Init @ 004861b0</code>): +<code>0x44–0x60</code> → 16 fields.
* '''Weapon''' (<code>WeaponRecord_Init @ 00486b10</code>): +<code>0x44–0xd0</code> → 44 fields; a byte at <code>0x68</code> (col 18), plus a run of ~15 id-like values (col 26+) that look like sprite/effect/skill references.

=== Entities (NPC / monster) ===

Use the root header (<code>0x24</code>/<code>0x28</code>) then category fields from <code>0x2c</code>:

* '''Monster''' (<code>MonsterRecord_Init @ 00485c10</code>): <code>0x2c</code> (byte) then ints <code>0x30–0x9c</code> — 29 fields (31 parsed; the 32nd column on the line isn't read). Example <code>64.dat</code> "Weldok": <code>64 1 36 1 0 0 620 62 79 354 … 160 120 100 350 50 85 150 233 61 …</code>. HP/stats not yet labelled (consumed server-side).
* '''NPC''' (<code>NpcRecord_Init @ 00485f90</code>, via <code>NpcRecord_InitBase @ 004860d0</code>): ints <code>0x2c</code>/<code>0x30</code>, a byte <code>0x34</code>, ints <code>0x38–0x40</code>, then a 14-byte block <code>0x44–0x51</code>. Example <code>77.dat</code> "Noick": <code>77 1 121 85 0 0 75 57 0 …</code>.

== Common header columns (cols 1–8, item records) ==

{| class="wikitable"
! Col !! Offset !! Meaning !! Confidence
|-
| 1 || <code>0x24</code> || dat file number || confirmed
|-
| 2 || <code>0x28</code> || record index (1-based) || confirmed
|-
| 3 || <code>0x2c</code> || sub-type / grade (small: 0–3) || tentative
|-
| 4 || <code>0x30</code> || sub-type / grade (small) || tentative
|-
| 5 || <code>0x34</code> || item level / sort key (e.g. 22, 47, 52) || tentative
|-
| 6 || <code>0x38</code> || icon bitmap index || confirmed (leader-emblem icon)
|-
| 7 || <code>0x3c</code> || buy price || confirmed (shop gold check)
|-
| 8 || <code>0x40</code> || sell price || inferred (buy/sell pair)
|}

Header-only items (emblem/money/book/misc, 8 cols) end here. Money (<code>15.dat</code>) has <code>col7=col8=0</code> — it ''is'' currency, no price. Equippables continue with the 6-stat block below.

== The 6 equip stat columns (confirmed) ==

Every equippable item record carries six stats at a fixed offset block <code>0x44–0x58</code> (cols 9–14), confirmed from the stat-display builder <code>FUN_004bacb0</code> (the item-detail panel):

{| class="wikitable"
! Col !! Offset !! Stat
|-
| col9 || <code>0x44</code> || '''OFC''' — offense / attack
|-
| col10 || <code>0x48</code> || '''DEF''' — defense
|-
| col11 || <code>0x4c</code> || '''AGL''' — agility
|-
| col12 || <code>0x50</code> || '''LUCK'''
|-
| col13 || <code>0x54</code> || '''LIFE'''
|-
| col14 || <code>0x58</code> || '''FOOD'''
|}

The on-screen order differs from the record order — the header (<code>misccaption_u.txt</code> line 1) reads <code>LIFE FOOD OFC DEF AGL LUCK</code>, and <code>FUN_004bacb0</code> re-orders fields to match. It prints two rows: the item's stat values, and a '''SPEC''' row (<code>misccaption_u.txt</code> line 2) with the <code>%+d</code> equip delta.

Cross-checks: rings (<code>8.dat</code>) only ever set cols 9–12 (OFC/DEF/AGL/LUCK), never LIFE/FOOD; armor <code>23.dat</code> col10 = DEF (main stat), col11 = AGL; weapon <code>16.dat</code> katana col9 = 110 (OFFENSE), col11 = 65 (AGL). These offsets are identical across item types — weapons carry the same 6 at <code>0x44–0x58</code>, plus their weapon-specific columns beyond.

== Weapon block (cols 15–44, <code>0x5c</code>–<code>0xd0</code>) ==

Example <code>16.dat</code> katana: <code>… 9 120 0 1 2 148 0 255 0 0 0 | 463 436 489 490 491 492 589 590 539 540 541 542 601 602 | 2 1 38 1 0</code>.

* '''cols 15–25''' — weapon params (attack range/speed/hit-rate class; <code>0x68</code>/col18 is a byte). Consumed by the attack/combat path (server-side for damage).
* '''cols 26–39''' — a run of 14 sprite/animation sequence ids (<code>463…602</code>, in the sprite-archive range) — the weapon's swing/effect frames, loaded by the animation system on equip.
* '''cols 40–44''' — display/misc; col42 (<code>0xc8</code>) = catalog icon (read by <code>Stuct_Setup_cpt_panel_catalog</code>).

== Consumables / scrolls ==

* '''Consumable''' (type 4, 10–11 cols): header + col9 = recovery amount (e.g. food <code>600</code>) + a trailing effect/skill-name string.
* '''Scroll''' (type 6, 33 cols): header + col9…col15 = skill/effect params (skill id, power, level req), rest padding.

== Monster block (<code>0x2c–0x9c</code>, ~30 fields) ==

<code>MonsterRecord_Init</code> writes cols 3+ as HP / base stats / AI / drop data. These are read by the '''server''' combat/AI — the client only uses the monster record for its sprite/name — so the columns aren't labelled here.

== Confirmed column labels (field-consumer trace) ==

{| class="wikitable"
! Record !! Col / offset !! Meaning !! Evidence
|-
| Item (all types) || col7 = <code>0x3c</code> || buy price || <code>State_NpcShopBuy_Tick @ 00467fd0</code>: buy allowed only if <code>record->0x3c <= player.money</code>, then sends <code>0x35</code>. Ring col7=100000, weapon 9000, matches.
|-
| Item || col8 = <code>0x40</code> || sell price (inferred) || Not consumer-confirmed, but the buy/sell pair — ring col8=5000 vs buy 100000; weapon col8=900 vs buy 9000.
|-
| NPC/shop (type 0xB/0xC) || col7 = <code>0x3c</code> || shop-type code || <code>State_NpcShopBuy_Tick</code> case 0 switches on <code>npcRecord->0x3c</code>, accepts <code>0x44,0x47,0x4a,0x4d,0x50,0x53</code> = letters D G J M P S (shop kinds).
|-
| NPC/shop || cols 9–22 = <code>0x44</code>–<code>0x51</code> (14 bytes) || per-category "sells this" flags || same function loops <code>npcRecord[i + 0x44]</code>, <code>i = 0..13</code>; each nonzero byte adds item-category <code>i</code> to the shop's list (14 categories: Katana…MonsterItem).
|-
| Item / emblem || col6 = <code>0x38</code> || class/icon bitmap index || <code>cpt_panel_status_widget_Draw</code>: for the party-leader emblem (dat 9), <code>record->0x38</code> is passed to <code>File_Read_Bitmap_Archive</code> as the icon image id.
|}

'''Server relevance:''' col7 (buy price) is the value the shop's gold check uses; an equipped item's col9–14 bonuses (OFC/DEF/AGL/LUCK/LIFE/FOOD) are applied to the wearer's totals. The player's ''total'' stats (base + all equipped bonuses) are computed server-side and pushed via packets <code>0xC001</code>/<code>0xC002</code> — the client never re-derives totals from records.

== See also ==

* [[BIN textdata]]
* [[textdata cptNN.txt]] — the flavor-text companion file, paired by dat number

BIN files

2026-07-02T11:01:12Z

0:0:0:0:0:0:0:1:

*[[BIN bitmapdata]] — Flat, single-image files: a small header (palette size, width, height) followed by an embedded color palette and 8-bit indexed pixel data. General-purpose still images (backgrounds, larger art), accessed by numeric index.
*[[BIN cockpitdata]] — Same flat indexed-image format as bitmapdata. Holds the artwork used for cockpit/HUD-style overlay panels.
*[[BIN etcimage]] — Same flat indexed-image format as bitmapdata. A catch-all bucket for miscellaneous 2D art that doesn't belong to the other image archives.
*[[BIN mapdata]] — Encrypted, name-indexed archive holding world/map data: plain-text <code>.knd</code>/<code>.knd_p</code> 3D model definitions describing map and building geometry, which reference textures and sprites from the texture/sprite archives by index.
*[[BIN npcdata]] — Encrypted, name-indexed archive of plain-text NPC definition files (one record set per NPC), keyed by a self-referential <code>npclist.dat</code> file-name list stored as entry 0.
*[[BIN palette]] — Per-entry 16-bit color palettes, one file per numeric index, matched by index to the corresponding sprite sheet in the pattern archive to color its indexed pixel data.
*[[BIN pattern]] — Multi-sprite sheets: each entry is a small directory of sub-images (offset + width/height per sprite) packed into one indexed-color pixel blob, colored using the matching-index file from the palette archive. Used for character/entity/effect animation frames.
*[[BIN point]] — Plain-text 3D point/vertex-list entries (a count followed by that many <code>x,y,z</code> coordinate lines), consumed when building mesh geometry for map objects and models.
*[[BIN sedata]] — Encrypted, numeric-indexed archive of short compressed sound-effect clips (SSF-format audio), referenced by the game's sound-effect id tables (e.g. <code>setable.txt</code>).
*[[BIN seqence]] — Plain-text, numeric-indexed animation-sequence tracks (the client's own spelling of "sequence"): per-frame timing/loop data and pattern-sheet frame indices, with built-in 8-direction mirroring, that drive playback of a pattern sheet's sprite frames.
*[[BIN sprite]] — Same flat indexed-image format as bitmapdata. Individual 2D sprite/object art placed in the game world.
*[[BIN textdata]] — Encrypted, name-indexed archive of the game's plain-text data tables: item/NPC/monster stats, UI strings, quick-chat phrases, world zone/effect/BGM tables, and more. The largest and most varied of the BIN archives.
*[[BIN texture]] — Same flat indexed-image format as bitmapdata. Texture maps applied to the 3D models defined in the mapdata archive.

Raynegard game assets

2026-07-02T10:53:25Z

0:0:0:0:0:0:0:1:

Raynegard's game data is distributed as many small files packed into a custom .bin container/archive format. The client unpacks these at startup (or on demand) to load its text, images, sprites, maps, NPC/item data, and sound.

*[[BIN files]] — the game's general-purpose archive format. Assets of a given category (text, sprites, maps, NPC data, etc.) are bundled in matched pairs of files: a small header file (e.g. <code>textdatah.bin</code>) and the packed data file (<code>textdata.bin</code>). The header is just a flat list of <code>(offset, size)</code> entries, one per packed file, with no padding or alignment between entries. Some archives ("directory-type") also store a self-referential file-name list as entry 0, so files can be looked up by name instead of index; others are accessed purely by numeric index. Contents are sometimes obfuscated with a simple repeating XOR cipher (key byte + increment, resetting per file) rather than real encryption. At startup the client loads about a dozen of these paired archives — <code>bitmapdata</code>, <code>cockpitdata</code>, <code>etcimage</code>, <code>mapdata</code>, <code>npcdata</code>, <code>palette</code>, <code>pattern</code>, <code>point</code>, <code>sedata</code>, <code>seqence</code>, <code>sprite</code>, <code>textdata</code>, <code>texture</code> — together covering nearly every non-executable asset category in the game.
*[[SSF files]] — Raynegard's custom compressed audio format. Unlike the BIN archives, an <code>.ssf</code> file is not a container — each one holds a single sound effect or music track. It has a small header (channel count, sample rate, loop flag/loop point) followed by audio data encoded with a custom ADPCM-style compression scheme. Decoding walks the file block by block, reconstructing 16-bit PCM samples from packed nibbles and a small set of fixed prediction coefficients, so it can be converted losslessly-in-practice to a standard <code>.wav</code> for playback outside the game.