Lineage 2 Launcher Updater: Ship Patches Without Reinstalls

A lineage 2 launcher updater does three things: it checks the files in the player's client, downloads the ones that are missing or out of date, and then starts system\L2.exe. Everything else it shows, from news to Discord buttons, is a wrapper around those three jobs. Get the update loop right and patches become routine. Get it wrong and every content change turns into "reinstall the client" for a few hundred people.
This covers the update loop, the two manifest formats still in circulation, where the packages live on the web server, and the failures that only appear on launch night.
What the launcher is actually checking
A launcher compares the player's local files against a list published by the server. Each entry carries a path, a size and a checksum. If the hash matches, the file is current. If it does not, the launcher downloads the new copy and replaces it. That is the whole mechanism, whether the tool is a 2008 L2Updater.exe or a .NET 8 launcher written last month.
Three things make the difference between a working version and a frustrating one:
- Critical files. A handful of files must be current before the game can start at all, because a protocol-mismatched client disconnects at the login screen. Mark them as mandatory and block the Start button until they are updated.
- Compression. Patch files should be compressed and decompressed on the fly. A raw patch of a few hundred textures is several hundred megabytes.
- A visible version string. When a player reports a bug, the first question is which launcher build and which patch revision they are on. If the launcher does not show it, support becomes guesswork.

Two manifest formats: hash plus JSON, or line-based checksums
Both work. They differ in how much you have to write yourself.
| Approach | How it works | Best for |
|---|---|---|
| Modern manifest | A remote manifest lists every file with a hash. The launcher compares, downloads only the differences, and a separate builder tool generates the full and incremental packages. The open-source l2-launcher-custom project works this way: .NET 8 launcher, hash comparison, manual Full Check, and a PatchBuilder that emits .bz2 files, a files.xml manifest and a download.php endpoint. | New servers, or anyone comfortable shipping a small .NET app. |
| Classic updates.lst | A text file with one line per file: path, CRC, size, mandatory flag. The original L2Updater format used lines shaped like F1=l2text\help.htm|<crc>|<size>|n under a header, with a self-entry such as IAM=L2Updater.exe|<crc>|<size> so the launcher could update itself. A generator tool builds the package and the list. | Interlude-era packs, or teams inheriting a launcher that already works. |
The classic format has one extra trick worth knowing: a ModifyHost flag that maps l2authd.lineage2.com to your login server IP in the Windows hosts file on first run. It saves players an edit, and it also means the launcher needs permission to write that file, which is why some of them trigger antivirus warnings.
Packaging: full install and incremental patch are different products
You need two artifacts and they are not interchangeable:
- Full client package. The whole thing, usually close to 10 GB for a modern client, for players who own nothing.
- Patch package. Only the files that changed since the last release, for players who are already on the previous build.
Generate the patch by diffing two builds of the client folder, not by remembering which files you edited. The difference matters: a file you changed and then reverted still ships, and a texture you replaced through a second tool gets missed. Keep every release's manifest so you can produce a delta between any two versions, and keep the last full package online permanently.
Preserve the folder structure inside the archive. A patch that unpackssysteminto the client root instead of replacingclient\systemleaves two of everything and the client still starts, which makes the bug look random.
Always include the critical files in every patch even when they did not change. It costs a few megabytes and it repairs clients that were broken by an earlier half-applied update.

Where the packages live on the web server
The updater directory is a static file host with a manifest next to it. Your site can serve it, and so can a plain nginx directory:
/updater/
files.xml
download.php
system/
textures/
maps/
...
- Serve it over HTTPS. A launcher downloading executables over plain HTTP is a man-in-the-middle waiting to happen.
- Expect bandwidth spikes. A patch push sends the same few hundred megabytes to everyone who is online. If the updater shares an uplink with the game server, players will feel the patch as lag, so keep them on separate hosts when you can.
- Cache the full package, never the manifest. The manifest should be served with no-cache headers so clients never compare against a stale file list.
Client integrity and antivirus false positives
Two problems arrive together the moment you ship a launcher:
- Players with modified clients. Hash checks catch files that were edited or replaced. If you want more than that, some launchers ship a small client-side DLL for tamper checks and basic cheat detection. Decide before launch whether you want that responsibility, because it is also the first thing a sophisticated cheater reverses.
- Antivirus warnings. An executable that writes into a game folder reads as suspicious to heuristics. Large servers publish a plain note telling players to add the game folder to their antivirus exclusions, and some still get flagged after every rebuild. Signing the binary reduces the noise but does not remove it.
Self-updating launchers need their own hash check, or a modified launcher can be distributed as an "update" to your players. Keep the launcher's own entry in the manifest and refuse to run if it does not match.
The failure nobody debugs: protocol mismatch
A launcher can update perfectly and still leave players unable to log in, because the client it delivered speaks a different protocol than the server accepts. The server's AllowedProtocolRevisions setting lists the revisions it will talk to, for example 267;268;271;273 on a High Five build. If the client's system folder is at a different protocol, the symptom is a login screen followed by a disconnect with no useful error.
Pin the exact client build your patch is based on, ship that system folder in every full package, and treat a client from a different source as unsupported. The client system files guide covers how the revision is checked and which files must not change.
Launch-day checklist
- Run a Full Check on a clean install, then start the game from the launcher. Twice, on different machines.
- Change one file on the server side, rebuild the manifest, and confirm the launcher picks up that single file and nothing else.
- Kill the download halfway. The launcher should recover, not leave a corrupted file that passes a size check.
- Test from a machine with a fresh antivirus install, which is the closest you get to a new player's experience.
- Publish a manual patch download for the players whose launcher simply will not cooperate. There are always some.
After the patch works, get people to download it
A launcher is only useful to players who already installed the client. For everyone else the entry point is your listing. Put the server in front of players browsing by chronicle and rate with a free L2Calendar listing, and if you want the top of the category on opening day, VIP placement is the paid version. The server website guide covers the download page and registration flow the launcher hangs off.
