GameBridge examples
Complete aCis and Mobius bridge classes to adapt for your game server
Forgeport distributes the connector core, not a pack-specific adapter. The
game server administrator or developer must implement GameBridge against the
server's database schema and runtime API.
These pages publish the complete bridge classes from two working integrations:
| Example | Source baseline | Advertised capabilities |
|---|---|---|
| aCis | aCis 409, Interlude | 14 |
| Mobius | Mobius CT_2.6, High Five | 14 |
The examples are source references, not downloadable adapters. Each bridge
delegates pack-specific operations to focused helper classes such as
CharacterLister, GameCredentialVerifier, GrantApplier, and
PortalCommandStore. Implement those operations against your revision, or
inline equivalent logic in the bridge.
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 Custom bridge template and copy only the applicable patterns from these examples.