Connector updates and checks
Choose your connector family for update and verification instructions
Each connector family has its own artifact, runtime, version, and update steps. Choose the server you are updating:
Update L2J
Current: 2.0.0 (Java 17). Replace the connector-core JAR, recompile, restart, and verify.
Update L2Off / PTS
Current: 1.2.0 (Node 22). Replace the standalone connector beside portal.toml and verify the queue.
Update Metin2
Current: 1.0.0 (Node 22). Replace the standalone connector and verify MySQL-backed features.
What Connector check tells you
Connector check sends small requests through the same live connection Forgeport uses in production. It confirms that advertised functions respond and validates their returned shape. Some checks need a designated game account or character, and the Admin page tells you when a check changes state.
It cannot see inside the game client. A queue insert, password transform, or game mutation can agree with its configuration while still being wrong for the deployed server. After installation or update, perform one real account-linking test and one real delivery test.
State-changing checks use real test data
Item, currency, service, and unstuck checks can make a small real change when their capability is present. Use the designated test account and character shown in Admin.
Version status in Admin
The server card compares the version reported by the running connector with the release catalog for that server. It shows whether the build is current, has an update available, or is unsupported. Pack name, chronicle, and revision do not change this version comparison.