When the server needs to notify the client that something significant is happening, it sends it a server event. Examples include incoming missiles, the fact that the player’s ship is destroyed, or a chat message. Like actions, events have types that identify them over the wire. They are also property holders so they can contain […]

To allow a consistent way of handling traffic between client and server, we introduced the actions concept. This based on the Command design pattern and makes it quick for us to implement features that requires functionality on both client & server sides while keeping the code elegantly isolated in single-responsibility classes. All our actions implement the IGameAction interface […]

Our game play structure relies on three core components: Entities, Actions, and Server Events. The main reason for this abstraction is to allow easy communication with the server. By wrapping our core components in well-defined structures we can easily expand them while ensuring that they can always be serialized and deserialized correctly. Entities Any object […]