Use a compatible Interlude installation that already starts normally. The recommended route is the lightweight launcher, but advanced users may also connect manually without running it.
Select your existing compatible Interlude installation and press Play. The launcher starts that client; it does not include a client, download a replacement System or patch L2.exe, l2.ini, Engine.dll or Core.dll.
On supported clients, the launcher reads the existing login address from l2.ini in read-only mode and creates only the temporary Windows network redirection needed for the login connection to reach Interlude Reforged. It can also pass the server address at startup when the client supports it. Administrator permission may be required because these temporary changes are made in Windows networking, not in the game files.
If you prefer not to run the launcher, you may configure a compatible Interlude client by your own means to connect to the Interlude Reforged LoginServer and then follow the normal GameServer connection. No Interlude Reforged executable is required for this route; manual client setup and compatibility are the user’s responsibility.
The connection method is designed to avoid replacing your System folder. This explains what the launcher reads, what it changes temporarily in Windows and what it leaves untouched.
No. The launcher does not write to L2.exe, l2.ini, Engine.dll or Core.dll and does not replace files in your System folder. On supported formats it may read l2.ini in read-only mode to discover the existing login address.
Because the redirection is configured at the Windows networking layer, not inside the client. Creating or removing a local address, hosts entry or TCP rule can require elevated permission.
Only when needed, the launcher temporarily creates the route required for the client TCP login connection to reach Interlude Reforged. Depending on the client this can use a local loopback address, a hosts entry or a TCP port proxy.
No. It is created at launch and the launcher attempts to remove it when Lineage II closes normally. If Windows or the launcher terminates unexpectedly, a rule can remain until it is removed or the system is restarted, depending on the rule type.
A compatible Interlude installation that can already start normally on its own. The launcher does not disable or modify client protection components.
Absolute compatibility is not promised. Clients can use different revisions, file formats and protocols. The launcher can redirect supported login configurations, but it cannot make an incompatible game protocol compatible with the server.
The current version includes read-only support for Lineage2Ver413. For other formats it also tries to pass the server address at startup when the client supports that method, but some clients may need additional support.
No. The purpose of the launcher is specifically to connect without distributing or requiring an Interlude Reforged System folder.
Yes. Advanced users may configure a compatible Interlude client by their own means to reach the LoginServer and then follow the normal connection to the GameServer. This manual route does not require running our launcher; client configuration and compatibility remain the user’s responsibility.
No. Credentials are entered inside Lineage II. The launcher does not ask for or store them.
The current launcher has no built-in telemetry and does not upload your game files. It stores the selected client path and windowed-mode preference locally, and it may check whether the server ports are reachable.
