Top Banner

Server Configuration

The server can be configured in three ways.

  1. Edit user\server\config\server.ini. This file must be configured before starting the local server. Once started, the file's contents have no impact on any running server instance.
  2. Use the provided control console to manipulate a running server.
  3. Start a server in interactive configuration mode. Any server started directly from the client GUI will be started that way. Alternatively you may provide the -c parameter to the server executable at startup.

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 override those found in the installation folder if they share the same name.

Planet configuration files may be edited or created anew. Check out user\server\config\myPlanets\Template.ini for a documented example of a new planet. Once defined, use the server.ini configuration file, control console, or interactive configuration mode to load it by name.

The currently available planets may be listed using the control console command /World/showPlanetTypes. All predefined planet names are:

  • Desert
  • FloatingIslands
  • FloatingLands
  • HollowCore
  • IceDesert
  • Lava
  • LushGreen
  • Moon
  • Ocean

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.