L2 Server Local Test: How to Prove Your Build Works Before Anyone Logs In

An L2 server local test is the cheapest few hours you will ever spend on your project. Before you rent a public box, open a firewall or announce a date, you can prove on one machine that the login server starts, that the game server registers with it, that a client can authenticate, and that a character can walk out of the starting village. Everything you skip here comes back as a support ticket during launch week, when you have no time to read a stack trace.
This guide walks the loopback setup and then the checks worth running once you are inside. It assumes you already have a pack that boots. If it does not, start with the install guide for your emulator and come back when the console reports a loaded world.
What a Local Test Actually Proves
A local test answers four questions, and nothing more:
- Does the stack start in the right order? Login server first, then the game server, or the registration step fails silently.
- Does the database schema match the pack? A missing table usually surfaces as an empty world rather than a clean error.
- Can a client authenticate and enter the world? That covers protocol revision, host resolution and account creation at once.
- Do the basic systems behave? Rates, spawns, teleports, NPC shops, class change and the newbie quest chain.
It does not prove the server survives two hundred players in Gludio, and it does not prove your network path works from outside. Those are separate tests, covered further down.

Point a Client at 127.0.0.1
Your server does not know it is local. The client is what needs redirecting, and there are two supported ways to do it. The simplest is the hosts file: add a line mapping 127.0.0.1 to l2authd.lineage2.com in C:\Windows\System32\drivers\etc\hosts on Windows, or /etc/hosts on Linux. Your pack documents this, and the L2J project publishes the same two options on its L2J documentation site. If the connection itself is the problem rather than the server, the install and connect walkthrough covers the client side.
The second way is passing the address to the client at launch:
l2.bin IP=127.0.0.1
Both work. The hosts route is easier to forget about later, and a forgotten hosts entry is a genuinely confusing failure: your client connects to the retail login server instead of yours and you spend an hour debugging a server that was never contacted. Keep a note of every change you make to the client's system folder, and revert the hosts line when you test against a public address.
Write down the exact client system state that works. When the client and the server disagree later, you will want to know which side you changed.
The Handshake Between Login and Game Server
Three ports matter in a default L2J stack, and only two of them are for players:
| Port | Who connects | Symptom when blocked |
|---|---|---|
| 2106 | The client, to authenticate | Login window hangs or rejects credentials |
| 9014 | The game server, to the login server | Game server never appears in the server list |
| 7777 | The client, to enter the world | Stuck at server select with a 9999 ping |
On a single machine all three are loopback traffic, so a firewall rule should not be necessary. If the server list stays empty anyway, the usual cause is registration: the game server has to register with the login server and store the resulting hex id where the login server expects it. Start the login server first, register, then start the game server. Reversing that order produces an error most packs do not word clearly.
If your login and game server sit on separate machines, or the pack splits the database into login and game schemas, treat the first boot as a network test in its own right. The configuration walkthrough covers the host and address keys that have to agree with each other.

A Test Checklist Worth Following
Log in with a normal account, not a GM account, and go through this list in order. Each item exercises a different layer, so a failure tells you where to look.
- Create an account through the client. If account creation is disabled on the login server, register through the tools instead and confirm the row landed in the accounts table.
- Select the server and enter the world. Watch the game server console during the transition. Warnings here are worth fixing now.
- Create a character of each race you plan to support. Starting stats, appearances and the initial inventory come from different data files.
- Run the first newbie quest. Quest state is the most common broken thing after a pack update, because scripts and data drift apart.
- Kill something and read the numbers. Confirm XP, SP, adena and drop amounts match your rate config. A multiplier applied twice is easy to spot here and expensive to find later.
- Teleport, then reload. A teleport exercises zone loading; a relog proves the character was persisted correctly.
- Take one class change with a GM-boosted character. This is the step players hit in their first week and the one most often left untested.
- Restart both servers. If the world does not come back cleanly, nothing else on this list matters.
Keep the game server console open the whole time. Every one of those steps writes something there, and the first error in the log is almost always the real one. The second error is usually a consequence.
Testing From a Second Machine
Loopback hides every network problem you have. Before launch, test from a different device on a different network, ideally a phone on mobile data so you are not behind the same NAT as the server.
- Set the external address in your config files to the public IP or hostname players will resolve. Leaving it at 127.0.0.1 makes a server that works only for you.
- Open 2106 and 7777 in the OS firewall and in any cloud security group. Those two are all a player needs.
- Never open the database port. If MySQL or MariaDB is reachable from the internet, automated scanners will find it within hours. Bind it to localhost.
If the second machine can log in but stalls at server select, the external address is wrong or the game port is filtered. If it cannot reach the login window at all, the login port or DNS is the problem. That split tells you more than reading the client log.
Load, Rates and the Limits of Testing Alone
You can learn a lot without players, and you should not pretend it is the same thing. Spawning a few hundred offline traders or GM-controlled characters tells you how the server behaves when the character table is large, which is a real and useful check. It does not simulate two hundred clients each receiving updates about the other 199 in the same zone, because outbound traffic scales with the square of the crowd rather than with the crowd.
The practical compromise is a short closed beta on the real host, with real players and a planned wipe. The open beta playbook covers how to structure one so testers test instead of grind.
What Your Local Test Cannot Cover
Be explicit with yourself about the gap. A green local test means the software works. It does not mean:
- Your host is adequate. RAM, CPU and upload bandwidth are only visible under real traffic.
- Your DDoS posture is real. A local firewall cannot absorb a volumetric flood. That is a provider feature.
- Your backups restore. Test a restore from the dump on a clean database, not just the dump itself.
- The economy is balanced. Rate decisions need days of real progression to judge.
- Your client patch is clean. A launcher that fails for one antivirus is a launch-day emergency.
Each of those deserves its own pass before you invite strangers. The launch day checklist sequences them so nothing gets forgotten on the last night.
When the Local Test Is Green
Once login, character creation, quests, teleports and a restart all work from a clean loopback setup, you have a server worth showing people. Save that state: take a database dump, archive the working config folder, and tag the pack revision. Every future change starts from a known-good baseline instead of a guess.
The next step is not a public launch. It is a rented machine you can break without warning anyone, firewalled correctly, with the same tests repeated over the real network. When that passes, list the server on L2Calendar through the free listing form so it lands in front of players browsing the server directory. If you want the opening to stand out from day one, VIP placement puts it above the standard rows during the weeks that matter most.
