Skip to content
RF DataData reference
RU

Maps

Monster spawn

Total 24 Known 9 Derived 0 Unused 15

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.

Map\<map>\<map>-[BLOCK].dat client file

Total 8 Known 0 Derived 0 Unused 8
Schema
Strs\[BLOCK].strs
Registry level
ready for full
Digest
copy of the server file in the client

Map\<map>\<block>.dat server file

Total 8 Known 5 Derived 0 Unused 3
Schema
Strs\[MAP].strs
Registry level
ready for full
Digest
spawn files (<block>.dat, for type 1 maps — <block>_<set>.dat); those unused by blocks are leftovers (8 nareaM files of 80 bytes), maps.md §3
OffsetFieldWhat it is and how it actsGoes to client asServer readersRoleStatusData
+0x000m_dwIndex
row number
maps.md §3
———known—
+0x004m_strCode
monster code (64): MonsterCharacter key; missing — loading error
maps.md §3
———known—
+0x044m_dwRegenTime
Respawn attempt interval, ms (3.1). For a boss — time from death to appearance (3.2)
maps.md §3 (digest row)
———known—
+0x048m_dwRegenLimNum
How many monsters of this row live at once. 0 — the row does not work
maps.md §3 (digest row)
———known—
+0x04Cm_dwRegenProp
Attempt chance in percent: rand() % 100 < value; ≥ 100 — always, 0 — never
maps.md §3 (digest row)
———known—

Map\<map>\<map>-[BLOCK].dat server file

Total 8 Known 4 Derived 0 Unused 4
Schema
Strs\[BLOCK].strs
Registry level
ready for full
Digest
spawn blocks, maps.md §3
OffsetFieldWhat it is and how it actsGoes to client asServer readersRoleStatusData
+0x000nCount
block number
maps.md §3
———known—
+0x004Lable
block name (64); also the spawn file name <block>.dat
maps.md §3
———known—
+0x044m_dwDummyNum
number of points (the list ends with "0")
maps.md §3
———known—
+0x048m_strDummyCode ×20
*dm dummy name (64), 20 points
maps.md §3
———known—

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.

Map\<map>\<map>-[BLOCK].dat client file

OffsetFieldWhy unusedData
+0x000nCount
the client does not open the file: the strings [BLOCK], [PORTAL], _str.dat are absent in the AoP client image in both ASCII and UTF-16; the server reads its own copy
maps.md §4 (before 4.1)
—
+0x004Lable
the client does not open the file: the strings [BLOCK], [PORTAL], _str.dat are absent in the AoP client image in both ASCII and UTF-16; the server reads its own copy
maps.md §4 (before 4.1)
—
+0x044m_dwDummyNum
the client does not open the file: the strings [BLOCK], [PORTAL], _str.dat are absent in the AoP client image in both ASCII and UTF-16; the server reads its own copy
maps.md §4 (before 4.1)
—
+0x048m_strDummyCode ×20
the client does not open the file: the strings [BLOCK], [PORTAL], _str.dat are absent in the AoP client image in both ASCII and UTF-16; the server reads its own copy
maps.md §4 (before 4.1)
—
+0x088m_dwSelectProp ×20
the client does not open the file: the strings [BLOCK], [PORTAL], _str.dat are absent in the AoP client image in both ASCII and UTF-16; the server reads its own copy
maps.md §4 (before 4.1)
—
+0x598m_nMin
the client does not open the file: the strings [BLOCK], [PORTAL], _str.dat are absent in the AoP client image in both ASCII and UTF-16; the server reads its own copy
maps.md §4 (before 4.1)
—
+0x59Cm_nMob
the client does not open the file: the strings [BLOCK], [PORTAL], _str.dat are absent in the AoP client image in both ASCII and UTF-16; the server reads its own copy
maps.md §4 (before 4.1)
—
+0x5A0m_nMax
the client does not open the file: the strings [BLOCK], [PORTAL], _str.dat are absent in the AoP client image in both ASCII and UTF-16; the server reads its own copy
maps.md §4 (before 4.1)
—

Map\<map>\<block>.dat server file

OffsetFieldWhy unusedData
+0x050m_dwRegenMinNum
never read
maps.md §3: “No reads found” [code]
—
+0x054m_dwStdKill
never read
maps.md §3: “No reads found” [code]
—
+0x058m_dwRegenMaxNum
never read
maps.md §3: “No reads found” [code]
—

Map\<map>\<map>-[BLOCK].dat server file

OffsetFieldWhy unusedData
+0x088m_dwSelectProp ×20
point selection weight
maps.md §3: “the only code with the 0x44 point record stride is the loader” (search in dzs.txt)
—
+0x598m_nMin
nMin of the block, 0 in AoP
maps.md §3: “search for all reads of +0x598/+0x59C/+0x5A0 in dzs.txt: none refers to the block record”; the client does not use the file for these fields
—
+0x59Cm_nMob
nMob of the block, 0 in AoP
maps.md §3: “search for all reads of +0x598/+0x59C/+0x5A0 in dzs.txt: none refers to the block record”; the client does not use the file for these fields
—
+0x5A0m_nMax
nMax of the block, 0 in AoP
maps.md §3: “search for all reads of +0x598/+0x59C/+0x5A0 in dzs.txt: none refers to the block record”; the client does not use the file for these fields
—

← 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