Features

At a glance

Protection

effective detection and blocking of bots, including private and premium builds
flexible game window limits with an individual cap per HWID
reliable hardware binding with protection against HWID spoofing
blocks launching inside virtual machines and emulators
detection of debuggers, injectors and process memory modifications
real-time integrity control of the game executable code
detection of third-party DLLs loaded into the game process
detection of local proxies and third-party VPN interceptors
built-in TCP proxy binding HWID to every game connection
automatic fallback to a backup port under network blocks and DPI
correct operation behind CGNAT and VPN thanks to HWID-tag authorization
client file hash checks to prevent modification of the interface and resources
FileHasher utility for quickly generating the verified-files configuration
automatic update of the client part from the server with progress indication
built-in Discord Rich Presence integration to promote the server — shows the “Playing lineage.com” status in Discord
remote control of client features via server flags without rebuilding
fail-closed mode: if the connection to the server is lost, game login is blocked
active session monitoring with automatic cleanup on timeout
logging of all security events
compatibility with all Lineage 2 chronicles

Additional plugins

Server monitoring — HWID, accounts and bans in the cabinet
FileHasher — client file integrity control
Lite Launcher — auto-update of the protection file
Ctrl+V — paste from clipboard into the game chat
BrowserBypass — open links on the player side
Account List — saved account manager
Discord — Rich Presence in the player profile
In-game text overlay and FPS counter

What it blocks

Bots and cheaters

BLOCKED

Adrenaline

Detected regardless of launch settings — renaming or masking the process does not help. On detection — automatic HWID ban.

BLOCKED

L2Walker / L2Helper

Detected at the system call level before connecting to the server — hiding the process or masking activity is not possible.

BLOCKED

L2PHX / packet cheats

Any attempt to intercept packets between client and server is detected on every connection. Getting in the middle — impossible.

Hacking tools

DETECTED

Debuggers & injectors

Multi-layer protection against debugging and reverse engineering. Attempts to attach a debugger, inject DLLs, or run CE/x64dbg are detected instantly — bypassing one layer is not enough.

DETECTED

Patching & file tampering

Client file integrity is verified on every launch. Replacement or patching is detected instantly — startup is blocked.

DETECTED

Login without Lin2Guard

The server-side hook blocks any connection without an active Lin2Guard session. Bypassing the client to log in is impossible.

How it works

01

Client protection

Our l2.exe checks the environment before the game starts: bots, debuggers, patching. If suspicious — blocks launch and records the violation.

02

Verification server

Checks the player's HWID against the database: active ban, window limit, suspicious behavior. Grants permission or blocks before connecting to the game.

03

Server hook

Injected into the L2J game process and blocks connections without an active protection session. Incoming traffic is verified against HWID in real time.

HWID identification

Unique hardware fingerprint. The ban is tied to hardware — cannot be bypassed by reinstalling the game or switching accounts.

Window limit

Global multi-boxing limit per HWID. Donors or VIP players get a personal limit bump — one DB row, no server restart needed.

Auto-ban

Threat scoring system: each violation adds points. When the threshold is reached — automatic ban without admin involvement.

Audit log

All events (login, logout, violations, bans) are written to the DB linked to HWID, account, and IP.

Real-time bot detection

Process monitoring runs continuously at random moments. There is no way to predict or avoid the check.

Flood protection

Automatic block on repeated failed connection attempts — no database load. Brute-force enumeration does not work.

Chronicle support

All Lineage 2 chronicles are supported, along with major L2J forks (l2jscripts, l2jeternity, Lucera2, and others) and PTS (L2Off) servers.

Fail-closed

If the protection server is unavailable — the hook blocks login. Bypassing protection by shutting it down is impossible.

Compatibility

All chronicles L2J PTS (L2Off)

Works on all Lineage 2 chronicles and any build: l2jscripts, l2jeternity, Lucera2 and other L2J forks, as well as PTS (L2Off) servers.

System components

l2.exe — client side

Replaces the standard game launcher. Distributed to players with the client. Runs in the background throughout the session.

OS: Windows Type: EXE launcher Mode: background process

lin2guard — protection server

Go binary for Linux. Runs alongside the game server. MySQL backend — all data in your database.

OS: Linux Stack: Go binary DB: MySQL

guard.so — server hook

LD_PRELOAD library, injected into the game server JVM. Intercepts traffic and verifies every connection.

Type: LD_PRELOAD Target: L2J / PTS Traffic: realtime

Pricing

Service	Price	Note
Subscription	$200	View plans
Re-bind to another IP	$30	Change IP when migrating the server.
Updates	$10 / mo	Optional. Can be added at any time — e.g., pay for 6 months upfront at $60.

Updates are not required — protection works without them. If you want new features and patches, simply pay for the needed number of months at any time.