Warning: file_get_contents(./documentation/concepts/round.prefix): failed to open stream: No such file or directory in /var/www/k9720-1/htdocs/hexaverse/html.php on line 65
Hexaverse - Documentation
Top Banner


Hexaverse is round based. During each round a number of phases are processed until the next round begins. All players (and AI clients) experience each phase simultaneously. As such all players may issue commands to their units at the same time.


  1. Command Phase: During this phase all players add or remove unit commands. With few exceptions, commands are not executed immediately. Once done, all connected players are expected to request a new round by clicking the end round button (or by pressing the return key). As long as at least one connected player has not yet requested a new round, it is possible to resume an ended round by clicking this button again. This phase is typically configured to have a maximum time window. During the first round, and after the disconnection of the last player, any timer is halted until a new round is explicitly requested by connected clients.
  2. Structure Phase: Implicit computation phase. Executed the moment a new round is computed. Resources are distributed across compounds and productions advance.
  3. Attack Phase: Attack commands are executed in order of their respective units' initiative. Offensive units may fill and execute their attack queue automatically if hostile targets are in range, and an attack is considered safe. This phase ends when all units have exhausted their command lists or attack action.
  4. Motion Phase: All non-attack commands are issued during this phase. This includes standard motion as well as vehicle operations such as terraforming, construction, or repairing units. Both motion and queued operations are executed in the order of the respective unit's initiative. Towers may automatically fire at trespassing hostile units during this phase. This phase ends when all units have exhausted their command lists or movement action.
  5. Animation Phase: While the server waits, changes generated during the previous phases are properly animated by all clients. Independent events are visualized in parallel, although the server does not actually execute that way. The animation phase may last at most 10 seconds, and will be accellerated if necessary.

At the end of the animation phase, the next command phase starts.