Without geodata, monsters ignore walls, players shoot through terrain and pathing breaks. Setting it up is a one-time job that hugely improves how a server feels.
What geodata does
- Enables proper line of sight (no casting through walls).
- Makes mobs and pets path around obstacles instead of sliding through them.
- Required for correct siege, fear/flee and ranged behaviour.
Steps
- Get the geodata for your chronicle (Interlude, High Five, etc.) — it must match your pack's format.
- Place the geodata files into your pack's geodata folder, e.g.
gameserver/data/geodata. Newer forks use a single format; older ones split geodata and pathnodes. - Open your geodata / general config and enable it: set geodata to enabled and choose the correct path-finding mode.
- Restart the game server and watch the console — it will report the region files it loads.
Common problems
- Server won't load geodata: wrong file format for your chronicle/fork.
- High RAM use: geodata is memory-heavy; give the JVM enough heap.
- Mobs still path badly: path-finding is off, or set to the basic mode — switch to the geodata-based mode.
Once movement feels right, get players in with a listing on L2TopZone.
FAQ
Do I really need geodata?
Yes — without it mobs ignore walls, casting works through terrain and sieges misbehave.
Why won't my server load geodata?
The files are the wrong format for your chronicle or fork. Use geodata that matches your pack.
Geodata uses a lot of RAM — is that normal?
Yes, it is memory-heavy. Give the JVM enough heap in your startup script.