THE SOURCE CODE:
The project is under development, but much has already been implemented.


https://github.com/felchs/jesterinitializer
This is the entry point for creating a server. With this class you can initialize games and assign unique IDs, handle the initial login flow, and route messages to the correct handlers. This project uses the #jesterengine, #gamepersistencebdb, and the game itself (for example, #jesterticktacktoe). You can host many different games on the same server.


https://github.com/felchs/jesterengine
The network engine is built with https://netty.io. It handles the game's structure for both action-based and turn-based games: events such as game start, game finish, turn start/end, creation of new games, etc. It also handles message sending/receiving, achievements, ranking, and more.


https://github.com/felchs/gamepersistencebdb
Almost every game needs to store data in a database. This repository is an implementation using the NoSQL Berkeley DB, which is a very fast database. You can, however, use SQL databases if you prefer. For now we're using Berkeley DB, but we plan to support MongoDB and relational databases such as MySQL, PostgreSQL, and SQL Server.


https://github.com/felchs/jesterticktacktoe
This is an example game (Tic-Tac-Toe) that uses the #jesterengine to handle game events and logic.


https://github.com/felchs/jesterclientcsharp
The client for the Jester Engine is written in C#. It handles login and message sending and includes common methods for gameplay such as sending moves, ending turns, and other game-related messages.


https://github.com/felchs/DarkstarSharpLib
This helper API is used by the jesterclientcsharp. It handles low-level network I/O over sockets and includes authentication steps for the client-server handshake.