CONFIGURATION REFERENCE

Move.txt

Movement menu destinations and entry conditions

4.MuServer/Sub-1/Data/Move/Move.txt

Section table9 recorded fieldsutf-8-sigRecorded file structure

Recorded file structure

Verify the active copy and owning role before editing. Recorded structure does not prove feature activation.

APPLICATION / RELOAD/reload move

Apply on the owning role. Startup-only settings require a restart; spawn/event reloads can reset active state.

Open full tutorial

Recorded column order

Index   Name                    	RequireMoney	MinLevel   MaxLevel		MinReset	MaxReset   AccountLevel   Gate

Field reference

Names and observations come from the supplied files. “Not established” means the unit/range/enum is not verified. Keep a known working value until confirmed.

Section / parameter	Meaning and verified limits
main	Stable identifier in this table. Keep references unique and consistent; its namespace depends on the file.
main	Display text. Preserve format placeholders such as %s and %d; translate text without renaming technical attributes.
main	Observed parameter RequireMoney. Its exact unit, accepted range or enum meaning is not established by the schema alone; retain a known working value and validate this module before changing it.
main	Lower level bound. In ItemDrop.xml MonsterMinLevel limits the monster, and -1 removes the bound.
main	Upper level bound. In ItemDrop.xml MonsterMaxLevel=-1 removes that bound.
main	Reset/Master Reset requirement or limit. These counters are independent of normal character level.
main	Reset/Master Reset requirement or limit. These counters are independent of normal character level.
main	Account-tier or VIP restriction/value. This is not the account login name; verify normal/VIP access separately.
main	Destination/entry gate ID. Must exist in the active profile’s Gate.txt and land on an owned, available map.

9 fields · 1 / 1

Learn how to apply a change