Connect your L2Off server
Run the standalone Forgeport connector beside retail server binaries
The L2Off connector is a standalone Node process. It reads one generated
portal.toml, connects to SQL Server, and sends Forgeport requests to the SQL or
delivery path configured for your pack. You do not write a Java integration.
Item delivery requires an extender that reads a queue and applies the item to the live character. Forgeport does not ship that extender component.
Prerequisites
- Node 22 or newer on the connector host.
- SQL Server credentials for the world and account databases.
- Outbound WSS access to
wss.forgeport.net:443. - An extender delivery path for purchased items.
- A test account and character for end-to-end verification.
Connect the server
Add the server in Forgeport Admin
Open Admin → Game Servers → Add game server, choose PTS / L2Off, and name the server.
Download the connector and profile
Download portal-connector-pts-1.2.0.mjs and the generated portal.toml.
The profile contains a secret token; keep it out of version control.
Check your delivery path first
Identify whether you can build the extender, already have an item-delivery feature, or have no delivery path. Follow Extender integration. Do not leave a delivery section enabled until something in the game server consumes its queue.
Configure portal.toml
Fill in the database connections, password format, codepage, catalog paths,
queries, queue, and only the delivery sections your extender implements.
Every generated line marked CHECK must be verified against your pack.
Start the connector
Put both files in one directory and run from that directory:
node portal-connector-pts-1.2.0.mjsConfirm Connected and run Connector check
The server card should show Connected. Connector check sends small test requests through the production connection. It proves the connector can run its configured operations, but it cannot prove that the extender consumes a queue row inside the game.
Verify the real result
Link a test account, confirm its characters appear, buy one low-value item, and verify in the client that the extender delivers it exactly once.
Verify every enabled feature on this pack
Chronicle, extender, schema, authentication daemon, and Windows codepage can differ. A valid SQL statement can still be wrong for a running server. Treat a feature as unconfirmed until you verify its visible result in the game client.