Lineage 2 Client Protocol: Match the System Folder

Every lineage 2 client protocol question ends in the same place: the system folder. The client announces a revision number during the login handshake, the server checks it against its allowed list, and if the two disagree the connection closes. No error dialog, no log line the player can read, just a login screen and a disconnect.
This is how to find the number your client speaks, which numbers belong to which chronicle, and what you may safely change in that folder.
What the protocol number actually is
It is the version of the client-server packet conversation. Packets change name, order and layout between chronicles, so the server has to know which dialect a client speaks before it can parse a single packet. That is why the revision is checked at the start of the login handshake rather than later.
On the server side this is a config entry, AllowedProtocolRevisions, listing every revision the build will accept. A High Five server commonly ships 267;268;271;273. On the client side the number is baked into the binary, which means changing it means replacing files, not editing a setting.
So the practical rule: a client works with your server when its protocol is in your allowed list. Everything else is a symptom.

The revision table, by chronicle
The numbers below are the widely documented values. Where a chronicle shipped regional variants, both appear, and that gap is the source of many "it works for me" reports.
| Chronicle | Protocol |
|---|---|
| C1 Harbingers of War | 419 |
| C2 Age of Splendor | 478 |
| C3 Rise of Darkness | 530 |
| C4 Scions of Destiny | 656 (660 with update 1) |
| C5 Oath of Blood | 693 (709 with update 2) |
| Interlude | 737, 740, 744, 746 |
| The Kamael | 828 |
| Hellbound | 831 |
| Gracia Part 1 | 851 |
| Gracia Part 2 | 12 (17 with update 1) |
| Gracia Final | 83 (87 with update 1) |
| Gracia Epilogue | 148 (152 with update 1) |
| Freya | 216 |
| High Five | 267, 268, 271, 273 |
The table is maintained in the open by client-library projects, for example the l2js-client protocol list, which is also the fastest way to check a revision you have never seen before. Note the shape of the numbers: they reset after Gracia Part 1, so 12 is newer than 851, and a client at 87 is High Five's distant ancestor, not a typo.
Regional clients complicate this. Interlude ships as 737 through 746 depending on how many official updates were merged, and Russian builds of later chronicles sometimes use a different revision from the NA/EU client for the same chronicle. Two players on "the same" Gracia Final client can genuinely be on different protocols.
How to read your own client
Before you patch anything, establish what you have:
- Ask the person who supplied the client which protocol it is. Reputable sources state it, and a source that cannot answer is a source you should not redistribute.
- Check the server's
AllowedProtocolRevisions. If the client logs in, its number is in that list, which is a valid inference even without a tool. - Compare against a known-clean system folder of the same chronicle. If the file sizes and hashes differ across the board, you are looking at a different build, not a patched one.
For editing content inside the folder, the workflow is always the same two steps: decrypt or unpack the folder with a system patcher first, then open the .ini, .inv and .dat files with an editor built for them. Editing a still-encrypted file produces unreadable output, and that mistake is behind most "I changed one line and the client broke" posts.

Files that must not change
Client integrity checks on live servers target a specific list, and it is short and predictable:
L2.binwithl2.exeas its loader carries the protocol and the entry point.Engine.dllis the engine behind both, and the other DLLs sit in the same execution path.nwindow.dll,core.dllandfire.dllsit in the same execution path.interface.uandInterface.xdatdrive the UI, and a modified one can desync the client.l2.inianduser.inihold connection and player settings.- Map files can be hashed when they load on servers that enforce client integrity, which is why an edited arena map can work for hours and then disconnect players on teleport to that one zone.
Servers that enforce checks will disconnect a client with a modified file, sometimes only when a specific zone loads. If you are an owner, publish the list you enforce. If you are a player, assume anything on that list is off limits and expect a disconnect rather than a warning.
Ports and the login address
Three ports explain almost every connection problem:
- 2106 is the client-facing login port.
- 7777 is the game port the client connects to after authentication.
- 9014 is how the game server registers with the login server, internally.
The client is built to look for l2authd.lineage2.com. A hosts entry pointing that name at your IP works only on a clean client, because a client already patched for another server ignores the hosts file. The L2J documentation also offers launching the binary with the address as an argument for local testing, which leaves the client files untouched. For distribution you ship a system folder that already points at your login server, which is why the folder and the protocol have to be treated as one unit.
Ship the folder as a unit
Handing players a partial patch of a system folder is how you get a population split across three client builds. Two rules prevent it:
- Replace the whole
systemfolder in every release, even when only two files changed. It is a few dozen megabytes and it removes an entire class of support tickets. - Deliver it through the launcher so hash checks confirm the result, as covered in launcher and patch system.
Keep one canonical client build per server, document its protocol and its source in your staff notes, and archive it. When a returning player appears two years later with a client from an old mirror, you will want that archive.
Then make sure people can find the server
A correct client only helps players who know the server exists. List it where people browse by chronicle and rate with a free listing on L2Calendar, and use VIP placement if you want the top of the category at launch. The install and connect guide is the player-facing version of everything above, which is worth linking from your download page.
