Go to the first, previous, next, last section, table of contents.

Players

Player objects are rarely necessary when building game designs; they typically only appear in saved games, in order to ensure that the same players get the same sides upon restoration.

SideProperty: player id

This property is the unique identifier of a player that is running this side. Defaults to 0, which means that no player has been assigned to the side.

Form: player [id] properties...

This form defines a player. If the id is supplied and matches the id of an existing player, then the player object is updated using the properties, otherwise a new player object will be created, using the given id if supplied, otherwise creating a new value.

GlobalVariable: player-sides-locked t/f

This variable is true if the player/side assignment may not be changed while the game is starting up. Defaults to false.

The number of players must always be less than the number of sides (sides without players just don't do anything).

PlayerProperty: name str

This property identifies the player by name. Defaults to "".

PlayerProperty: config-name str

This property identifies a particular set of doctrine and other definitions that the player is using. Defaults to "".

PlayerProperty: display-name str

This property identifies the display being used by the player's interface. The interpretation of this value is dependent on the interface in use. Defaults to "".

PlayerProperty: ai-type-name str

This property is the type of AI that will play the side if requested or necessary. The set of choices depends on what has been compiled into Xconq. (The general-purpose AI type "mplayer" will usually be available, but is not guaranteed.) An ai-type-name of "" means that no AI will run this player. Defaults to "".

PlayerProperty: password str

This property is the encoding of a password that must be entered before this player object can be reused successfully. Defaults to "".

PlayerProperty: initial-advantage n

This property is an initial relative strength at which the player should start. Some synthesis methods can use this to give more units or some other advantage to each player according to the requested strength. Defaults to 1.

GlobalVariable: advantage-min n

GlobalVariable: advantage-max n

GlobalVariable: advantage-default n

These variables set the bounds and default values for players' initial advantages. Default to 1, 9999, and 1, respectively.

Xconq is not guaranteed to be able to be able to set up a game with any combination of player advantages; the limits depend on the capabilities and characteristics of the synthesis methods that use the requested advantages in their calculations.


Go to the first, previous, next, last section, table of contents.