Hexode basic Game Design

It is about time to speak a little bit about the game itself, right? What makes Hexode different from other existing titles? And what is this going to feel like? I will try my best to highlight the most important points in the game design. Things are still subject to change, of course. But I think it is important to fix some ideas. As the development is getting me closer to something playable, I feel the need to write this down.

Read More

Unreal Engine and network replication

The Unreal Engine features its own model of network communication. Hexode is a multiplayer game by essence and I will try to explain in this post how it has been implemented so far.

To understand the network replication model, one has to first grasp the object model of UE and the notion of authority. Comming from Unity3D, the object model of UE was completely alien to me as there is no such thing in Unity3D. In the latter, everything is a gameobject and you may attach any component (with some restrictions and dependencies between certain components) and any script. It also means that you may organize the code as you so desire and define how each object is being (or not) replicated.

This is not the philosophy of the Unreal Engine.

The Unreal Engine differentiates between Actors (Something that is part of the level like a character or a skysphere or the hexagonal board of a previous post), Pawns (Actors that can be “possessed” by a¬†Controller, a human or an AI), GameMode, GameState, PlayerState, etc. Read More