Warning: file_get_contents(./documentation/config/server.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

Server Configuration

The server can be configured in multiple ways.

  1. Edit game folder\server\config\server.ini. This file must be configured before starting any local server. Once started, the file's contents have no impact on any running server instance. This file does not exist until the server (or other Hexaverse applications) have run for the first time.
  2. Use the provided control console to manipulate a running server.
  3. Start a server via the client interactive visual configurator.
  4. Use the server manager.

Planet Types

The server configuration loads planets as predefined templates. While their actual layout is mostly defined by fractal noise, the underlying rules are defined in separate configuration files located in [install]\server\config\myPlanets\[planet name].ini and user\server\config\myPlanets\[planet name].ini. Configuration files located in the user folder directory are prefixed with a * character.

New planet types can be created by writing new .ini files, copying and modifying existing files from the install directory, or interactively via the interactive visual configurator. Once defined, use the server.ini configuration file, control console, interactive configuration mode, or server manager to load it by name.

The currently available planets may be listed using the control console command /World/showPlanetTypes.

Research Script

Laboratory research is controlled by a Lua script located in the installation folder [install]\lua\attributesAndResearch.lua.

However, if a Lua file exists in user\server\config\lua\attributesAndResearch.lua, then this will override the factory default script.

The script is loaded at server start, but can be updated during runtime via the control console command /IO/reloadResearchProgram. Clients will receive notifications of the generated attributes, topics, and states as needed. The script is no longer transferred to the client.

The file defines which research is possible, and how this affects unit availability and attributes. It also allows basic modification of all unit attributes.