Complete L2J integration examples
Complete single-file aCis and Mobius integrations to adapt for your game server
Forgeport distributes the connector core, not a pack-specific adapter. The game server administrator or developer registers explicit, type-safe operations against the server's database schema and runtime API.
These pages publish complete ForgeportIntegration.java examples:
| Example | Source baseline | Pack-specific differences |
|---|---|---|
| aCis | aCis 409, Interlude | BCrypt, characters.obj_Id, aCis world/data APIs |
| Mobius | Mobius CT_2.6, High Five | SHA-1/Base64, characters.charId, Mobius world/data APIs |
The examples are source references, not downloadable adapters. Each is one
file plus portal.properties. The core supplies catalog search, JSON,
capability inference, grant parsing and the command journal.
Use a complete example when you need to see exact code placement and a coherent set of pack calls. For an unfamiliar or heavily modified source, begin with the smaller installation template and borrow only verified pack-specific parts.
Choose a starting point
Use the example closest to the target source:
- Start from aCis when the pack uses aCis package names, bcrypt credentials,
characters.obj_Id, and aCis world/data APIs. - Start from Mobius when the pack uses Mobius package names, SHA-1/Base64
credentials,
characters.charId, and Mobius world/data APIs.
Do not identify compatibility from the chronicle name alone. Verify the password format, database columns, connection pool, player lookup, item and skill APIs, and persistence calls in the exact source revision.
For any other source, use the installation template and copy only the applicable patterns from these examples. What the finished integration gives a server is on the L2J web panel page.