Connector porting guide
How to connect your Lineage 2 game server to Forgeport
The Portal connector is the bridge between your Lineage 2 game server and Forgeport: a small piece of code running inside your game server's JVM that dials out to the Forgeport gateway over WebSocket, reports live status, and applies purchases and services in-game.
What we maintain, what you write
We ship and maintain one thing: the core connector library —
PortalConnector, PortalConfig, the GameBridge interface, and
GrantResult. It owns the WebSocket protocol (handshake, heartbeat, retry
with backoff, message dispatch) and has zero dependency on any specific pack.
You download it as a prebuilt jar; we version it and tell you when an update
is available.
Everything that touches your game — your database schema, your live world,
your login/session tables — is pack-specific, so you implement it: a
class that implements GameBridge against your pack's actual API. We don't
offer per-pack bridges as a supported product. Instead we publish two real,
tested reference examples (aCis 409 and L2J Mobius CT_0) so you have working
code to read and adapt, not just an interface to guess at.
Why not one bridge for everyone?
We tried. Building a second, independent GameBridge for L2J Mobius CT_0
took real engineering time even with the aCis one already working — every
pack's schema, password hashing, and API differ enough that a generic
"official" bridge would either be wrong for most packs or so hedged it
wouldn't do anything real. The core (the ~50% that's genuinely
pack-agnostic) is what we can honestly maintain for everyone.
Where to go next
- Architecture — the core/bridge split, the wire
protocol, and what
adapterVersionactually proves. - Porting guide — step by step: download the core,
implement
GameBridge, wire it into your game server's startup/shutdown. - Capabilities — what each protocol capability requires from your bridge, with real code from both reference examples.
- Reference examples — the full aCis 409 and L2J Mobius CT_0 implementations, gotchas included.
- Versioning — how
adapterVersionis tracked and what "update available" actually means.