THE LARGEST LINEAGE 2 SERVER COMMUNITYYOUR LINEAGE 2 COMMUNITY

  • +10,000 PLAYERS
  • VERIFIED SERVERS
  • DAILY UPDATES
CHOOSE YOUR NEXT ADVENTURE
EXPLORE L2CALENDAR

What are you looking for?

Search the sections of the site.

TOP SERVERS

Discover the featured Lineage 2 servers.

Blog

Guides, articles and tips for your next adventure.

Vlog

Videos, sieges, PvP and community moments.

Links

Clients, downloads and resources for Lineage 2.

Streamers

Find community streams.

Recruitment

Clan and constant party (CP) recruitment hub.

Buy VIP (AUTO)

Visit the VIP placement page.

Add server (Free)

List your server on the calendar.

Extend VIP time

Renew your VIP listing.

9 sections found.

Lineage 2 Client Protocol: Match the System Folder

L2Calendar Team9 min read
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.

Lineage 2 Client Protocol: Match the System Folder
Lineage II © NCSOFT

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.

ChronicleProtocol
C1 Harbingers of War419
C2 Age of Splendor478
C3 Rise of Darkness530
C4 Scions of Destiny656 (660 with update 1)
C5 Oath of Blood693 (709 with update 2)
Interlude737, 740, 744, 746
The Kamael828
Hellbound831
Gracia Part 1851
Gracia Part 212 (17 with update 1)
Gracia Final83 (87 with update 1)
Gracia Epilogue148 (152 with update 1)
Freya216
High Five267, 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:

  1. 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.
  2. 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.
  3. 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.

Lineage 2 Client Protocol: Match the System Folder (2)
Lineage II © NCSOFT

Files that must not change

Client integrity checks on live servers target a specific list, and it is short and predictable:

  • L2.bin with l2.exe as its loader carries the protocol and the entry point.
  • Engine.dll is the engine behind both, and the other DLLs sit in the same execution path.
  • nwindow.dll, core.dll and fire.dll sit in the same execution path.
  • interface.u and Interface.xdat drive the UI, and a modified one can desync the client.
  • l2.ini and user.ini hold 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:

  1. Replace the whole system folder in every release, even when only two files changed. It is a few dozen megabytes and it removes an entire class of support tickets.
  2. 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.

Frequently asked questions

What protocol version is Interlude?
Interlude clients ship as 737, 740, 744 or 746 depending on how many official updates were merged. An early clean client is 737; most Interlude builds in circulation today are 746. The server must list whichever one your client actually uses.
Why does the client disconnect after the login screen?
The most common cause is a protocol the server does not accept, so check AllowedProtocolRevisions against the client system folder. The second is a game server that never registered with the login server, and the third is port 7777 blocked between client and game server.
Can I edit files in the system folder?
Only after decrypting or unpacking the folder with a system patcher, and only the files your server allows. Protocol binaries, the UI files and map files are integrity-checked by many servers, and a modified one leads to a disconnect, sometimes only when a specific zone loads.

Lineage 2 Top Private Servers & Openings List

L2Calendar is the premier Lineage 2 private servers top list and calendar for the legendary MMORPG Lineage II. Whether you are looking for upcoming L2 Interlude servers, new High Five launches, or Classic server announcements, our platform tracks all top private server openings in one place.

Stay updated with the best Lineage 2 top servers. Our calendar displays upcoming openings, server rates from low-rate craft to mass PvP, chronicles, and launch times. Never miss a top L2 server opening — bookmark L2Calendar and check back daily for fresh Lineage 2 server announcements.

Looking for the perfect L2 server? Browse our complete list of Lineage 2 top private servers opening soon in 2025/2026. From low-rate craft servers to high-rate PvP realms, find your next Lineage II adventure here.