mog1-gameserver's Introduction

MOG1-GameServer

My first attempt at creating an multiplayer game with a authoritative server. This is the model logic part.

This repo is just a part of a larger system that is currently made up of four parts:

GameServer - The game data and logic. Communicates with other programs through a local "Unix" socket.
GameManager - A program that can be used to send commands to the data server to add game content, stop the server, admin players, etc.
WebServer - Has several roles. It serves the game client, authenticates users, and acts as an interface between clients and the GameServer
WebClient - The game client. It is an HTML5/CSS3 interface that is used to provide gameplay inputs to the game, as well as something pretty-ish to look at.

mog1-gameserver's People

Contributors

Watchers

mog1-gameserver's Issues

Precompile SQL

Need to compile query statements at server initialization, then reuse them.

Additionally, there needs to be a way to have statements that update the db manage ownership of the db write privileges .

Standardize Communication Protocol

This involves making a more robust way of communicating between the web server and the game server. At the moment, the web server must know the layout of each and every response. This is silly.

Add data identifiers to each serialized object. This way parsing doesn't have to rely on prior knowledge of the byte format.
Standardize integer usage. So far, I've been a bit willy-nilly in decisions to use unsigned/signed version. Additionally, with integers that will be serialized I need to explicitly state their bit width, and add the ability to discover the bit width to the server api (rather than passing sizeof(int) as part of the serialized object data).

Client socket close error: bad file descriptor

Very occasionally the server will report an error when trying to close the connection to a client socket, reporting that there is a bad file descriptor.

Recommend Projects