Connect your L2J server
Add Forgeport to an aCis, Mobius, or custom Java game server
This path connects a source-based Java game server. You add two JARs, write one
pack-specific ForgeportIntegration.java, and start Forgeport after the game
world and data tables are ready.
Forgeport handles the connection, protocol, catalog search, delivery journal, retries, and response formatting. Your class supplies only the SQL and game APIs that are specific to your pack.
Prerequisites
- Java 17 or newer for the game-server build and runtime.
- The game-server source and a working build.
- JDBC access with permission to create and update Forgeport's delivery journal.
- Outbound WSS access to
wss.forgeport.net:443.
Connect the server
Add the server in Forgeport Admin
Open Admin → Game Servers → Add game server, choose L2J, and name the server. Keep this setup page open while you install the files.
Download the three required files
Download portal-connector-core-2.0.0.jar, minimal-json-0.9.5.jar, and the
generated portal.properties. The configuration contains the server token;
keep it private.
Add the JARs and integration class
Put both JARs on the build and runtime classpath. Add
ForgeportIntegration.java to the game-server source and register your
database, credential, character, catalog, and delivery code. Start with the
installation and integration guide, or adapt a complete
aCis or
Mobius example.
Install the configuration
Place the downloaded file at config/portal.properties. Keep its Token
value unchanged. Review the configuration reference
before changing delivery windows or unstuck coordinates.
Wire startup, login, and shutdown
Call ForgeportIntegration.start() after the world and game data are ready.
Publish the player-online event from the completed EnterWorld flow, and call
Forgeport.shutdown() during game-server shutdown.
Build and restart the GameServer
Compile against the same connector JAR you deploy. Start the GameServer and check its log for the Forgeport connection message.
Confirm Connected and run Connector check
Return to Admin → Game Servers. The server card should show Connected. Connector check sends small test requests through the same connection used in production. It confirms that the connector responds, but it cannot see the final result in the game client.
Verify one real result
Link a test game account, confirm its characters appear, then buy a low-value test item and verify that it appears on the selected character in game.
What you should see
- The server card shows Connected and connector core
2.0.0. - Connector check passes for the functions you registered.
- A linked account shows its characters with current names and levels.
- A real test purchase reaches the selected character once.