Skip to content

RF DataData reference

Theme RU

Dungeons

Scenarios

Total 49 Known 49 Derived 0 Unused 0

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.

`Quest\<scenario>.txt` server file

Total 49 Known 49 Derived 0 Unused 0

Schema: scenario text: ### quest, ## mission, # job (dungeons.md §2–3)
Registry level: ready for full

Record: top-level markers

Offset	Field	What it is and how it acts	Goes to client as	Server readers	Role	Status	Data
`—`	`###`	new quest; the next token is the header (≤ 32 bytes); one per file dungeons.md §2.2	—	—	—	known	—
`—`	`##`	new mission; header ≤ 32 bytes dungeons.md §2.2	—	—	—	known	—
`—`	`#`	new job; header ≤ 32 bytes dungeons.md §2.2	—	—	—	known	—
`—`	`*`	key: the next token is the key name of level `###`/`##`/`#` dungeons.md §2.2	—	—	—	known	—
`—`	`[END_OF_FILE]`	end of file, required dungeons.md §2.2	—	—	—	known	—
`—`	`other tokens`	skipped (comments rely on this; lone markers inside a comment are dangerous) dungeons.md §2.2	—	—	—	known	—

Record: quest keys (after `###`) (`quest`)

Offset	Field	What it is and how it acts	Goes to client as	Server readers	Role	Status	Data
`—`	`membership_party`	≠ 0: only a player in a party can open, only the opener's party members can enter. 0: any player can enter, race is not checked (4.3). The client checks the party when openi… dungeons.md §3.1 (digest row)	—	—	—	known	—
`—`	`member_num`	How many players at once in the channel (checked on entry and re-entry, error 0x12) dungeons.md §3.1 (digest row)	—	—	—	known	—
`—`	`use_map`	The map must exist and have type 1 in `Map_Data.spt` (in AoP: Dungeon00, 01, 02, 04). Must come before all keys that reference dummies dungeons.md §3.1 (digest row)	—	—	—	known	—
`—`	`start_mission`	≤ 32 bytes, check in 2.3 dungeons.md §3.1 (digest row)	—	—	—	known	—
`—`	`limit_lv_min`	+0x11F8, +0x11FC. Effectively required, see below dungeons.md §3.1 (digest row)	—	—	—	known	—
`—`	`limit_lv_max`	+0x11F8, +0x11FC. Effectively required, see below dungeons.md §3.1 (digest row)	—	—	—	known	—
`—`	`dummy_block`	Up to 32 blocks of 32 dummies, no overflow checks. A dummy is any from the map's `.spt` dungeons.md §3.1 (digest row)	—	—	—	known	—
`—`	`monster_group`	Up to 32 groups of 32 monsters, unchecked. Only commented out in the data dungeons.md §3.1 (digest row)	—	—	—	known	—
`—`	`reward_item`	Up to 128 per list. An item of any table. Quantity counts only for stackable items, clamped to 99. Probability 0…1.0 (otherwise an error); stored as `rate… dungeons.md §3.1 (digest row)	—	—	—	known	—
`—`	`reward_exp`	`one`\\|other, number (double) dungeons.md §3.1 (digest row)	—	—	—	known	—
`—`	`reward_pvp`	`one`\\|other, int dungeons.md §3.1 (digest row)	—	—	—	known	—
`—`	`reward_dalant`	`one`\\|other, int dungeons.md §3.1 (digest row)	—	—	—	known	—
`—`	`description`	≤ 16 bytes, default `NO DATA` dungeons.md §3.1 (digest row)	—	—	—	known	—

Record: mission keys (after `##`) (`mission`)

Offset	Field	What it is and how it acts	Goes to client as	Server readers	Role	Status	Data
`—`	`area`	Searched only among dummies with the `dq` prefix. All `dummy:` and `react_contents` of the mission must lie inside the `area` box dungeons.md §3.2 (digest row)	—	—	—	known	—
`—`	`start_pos`	Where to move players when the mission starts dungeons.md §3.2 (digest row)	—	—	—	known	—
`—`	`gate_pos`	Several allowed (up to 32, unchecked). With `PORTAL` the server opens all portals of the map; the list affects only packet 35/8 (5.3) dungeons.md §3.2 (digest row)	—	—	—	known	—
`—`	`job_order`	Mission complete when all jobs are done / any one dungeons.md §3.2 (digest row)	—	—	—	known	—
`—`	`lim_time_sec`	Stored in ms. Required and > 0 dungeons.md §3.2 (digest row)	—	—	—	known	—
`—`	`result_type`	Not set — value 0xFF (not equal to “PORTAL”, see 5.3) dungeons.md §3.2 (digest row)	—	—	—	known	—
`—`	`result_contents`	Next mission for `NEXT` dungeons.md §3.2 (digest row)	—	—	—	known	—
`—`	`description`	Mission description dungeons.md §3.2 (digest row)	—	—	—	known	—
`—`	`complete_msg`	Text on completion dungeons.md §3.2 (digest row)	—	—	—	known	—
`—`	`loot_item`	Event item: at mission start `count` pieces are handed to living monsters of this code in `area` and drop on their death guaranteed (5.6) dungeons.md §3.2 (digest row)	—	—	—	known	—
`—`	`add_monster`	`monster:` code count, `<place>` (`dummy:`/`block:`) dungeons.md §3.2 (digest row)	—	—	—	known	—
`—`	`respawn_monster`	Keep up to “count” monsters alive: checked every `term` seconds, at most `lim` appearances in total (`lim` ≤ 0 — no limit) dungeons.md §3.2 (digest row)	—	—	—	known	—
`—`	`respawn_monster_option`	Makes the last `respawn_monster` disabled at start and names it; `inner`/`respond … respawn_monster: name` enable it dungeons.md §3.2 (digest row)	—	—	—	known	—
`—`	`change_monster`	At mission start every living “from” monster is replaced by the “to” one with probability NN % dungeons.md §3.2 (digest row)	—	—	—	known	—
`—`	`if`	Alternative description/completion text if the replacement from the last `change_monster` fired dungeons.md §3.2 (digest row)	—	—	—	known	—
`—`	`inner`	When a channel player enters the dummy (or any dummy of the block): create monsters/items, show the text or enable a named respawn. **Fires once per… dungeons.md §3.2 (digest row)	—	—	—	known	—
`—`	`respond`	When a monster of this code is killed: create monsters/items (with `-1` — near the kill spot) or show the text dungeons.md §3.2 (digest row)	—	—	—	known	—
`—`	`add_time`	Killing the monster / picking up the item of the target extends the mission limit by N seconds and shows the text dungeons.md §3.2 (digest row)	—	—	—	known	—

Record: job keys (after `#`) (`job`)

Offset	Field	What it is and how it acts	Goes to client as	Server readers	Role	Status	Data
`—`	`type`	Only these two values. `LOOT` and `BOSS` from comments are a loading error. Default TAKE. [game, 29.10.2026, G3, Sirin AoP] `type LOOT` in `DarkHole_01.txt`… dungeons.md §3.3 (digest row)	—	—	—	known	—
`—`	`contents`	Item (TAKE, any table) or monster (HUNT) dungeons.md §3.3 (digest row)	—	—	—	known	—
`—`	`count`	≥ 1; `-1` only for HUNT: “kill all” dungeons.md §3.3 (digest row)	—	—	—	known	—
`—`	`react_type`	Add a reaction to job completion dungeons.md §3.3 (digest row)	—	—	—	known	—
`—`	`react_contents`	Portal opened by the last reaction dungeons.md §3.3 (digest row)	—	—	—	known	—
`—`	`description`	Job description dungeons.md §3.3 (digest row)	—	—	—	known	—

Record: compound arguments

Offset	Field	What it is and how it acts	Goes to client as	Server readers	Role	Status	Data
`—`	`monster: CODE N`	monster from MonsterCharacter dungeons.md §3.4	—	—	—	known	—
`—`	`m_group: GROUP N`	random monster of the group dungeons.md §3.4	—	—	—	known	—
`—`	`item: CODE N`	item of any table dungeons.md §3.4	—	—	—	known	—
`—`	`dummy: NAME`	map dummy dungeons.md §3.4	—	—	—	known	—
`—`	`block: NAME`	random dummy of the block dungeons.md §3.4	—	—	—	known	—
`—`	`<word> -1`	near the event location (`respond` only) dungeons.md §3.4	—	—	—	known	—

Unused parameters

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

← Back to category