📑Gate

Registry of all server gates—defines where a gate leads, who can use it, and the destination area. It serves as the foundation for nearly every teleportation system (town return, /reset, /mreset, Castle Siege, events, Move.txt's /move command, etc.).

Column	Accepted Values	Description
Ind	Number, one per gate	Identifies the gate. This is the number referenced by other files (DefaultClassInfo.txt, MuCastleData.dat, ReiDoMU.dat, TvTEvent.dat, Move.txt, etc.).
Flag	Number	Present in the file, but not used anywhere in the server—a dead column.
Map	Map number	Destination map of the gate.
X / Y	Coordinates	One corner of the destination area.
TX / TY	Coordinates	Opposite corner of the destination area—the character arrives at a random point within the rectangle defined by these two corners. This same area is also used to determine whether a character is physically standing on the gate's location (within a margin of 5 tiles) when required by game logic.
TargetGate	Number corresponding to another Ind in this file, or 0	If set, this gate becomes merely an "alias": the actual destination is taken from the referenced gate (Map/X/Y/TX/TY/Dir of this gate are completely ignored). 0 = use this gate's own data.
Dir	Number from 0 to 7	Character's facing direction upon arrival.
MinLevel	Number, or -1	Minimum level required to use the gate. -1 = no minimum.
MaxLevel	Number, or -1	Maximum level allowed to use the gate. -1 = no maximum.
MinReset	Number, or -1	Minimum reset requirement. -1 = no minimum.
MaxReset	Number, or -1	Maximum reset limit. -1 = no maximum.
AccountLevel	Number	Minimum account level (Free/VIP1/VIP2/VIP3) required to use the gate.

Notes

• Magic Gladiator, Dark Lord, and Rage Fighter only require two-thirds of the gate's MinLevel (rounded down), except when entering Swamp of Calmness or when this behavior is disabled in the server's general configuration.

• When TargetGate is set, editing the Map/X/Y/TX/TY/Dir values of this gate has no effect—the actual destination is always taken from the referenced gate.

• The MinLevel/MaxLevel/MinReset/MaxReset/AccountLevel restrictions are only enforced by the system using the gate (for example, Move.txt)—Gate.txt by itself does not universally block travel in every use case.