Every scenario comes with its own basic settings, e.g., the starting time, the weather or the XP multiplier. With the missionHeader entry in config.json, you override these values for your server. This lets you adjust gameplay rules without changing the scenario itself.
You choose which scenario runs on your server in the dashboard. You can find out how in the guide Change Scenario.
How the missionHeader Works
The missionHeader is located in config.json in the root directory of your server, inside "game" → "gameProperties". All values you enter there replace the corresponding values from the scenario's header. Values you do not enter are still taken from the scenario.
How to Add the missionHeader
-
Stop the server
Stop your server via the dashboard. -
Connect via SFTP
Connect to your server via SFTP. -
Open config.json
Open the fileconfig.jsonin the root directory and find the"gameProperties"section inside"game". -
Add the missionHeader
Add the"missionHeader"entry with the desired settings inside"gameProperties". Put a comma after the previous entry. If there already is a"missionHeader", add the settings there.Leave the other entries in
"gameProperties"unchanged. -
Start the server
Save the file and start your server.
General Settings
These entries apply to all scenarios, as long as the scenario supports them:
| Entry | Description |
|---|---|
m_sName |
Displayed name of the scenario |
m_sDetails |
Detailed description of the scenario, e.g., your server rules |
m_bOverrideScenarioTimeAndWeather |
true = the scenario uses the time of day and weather from the missionHeader, if it allows it |
m_iStartingHours |
Starting time: hour |
m_iStartingMinutes |
Starting time: minute |
m_bRandomStartingDaytime |
true = random starting time (overrides m_iStartingHours and m_iStartingMinutes) |
m_fDayTimeAcceleration |
Time acceleration during the day (1 = 100%, 2 = 200% etc.) |
m_fNightTimeAcceleration |
Time acceleration during the night (1 = 100%, 2 = 200% etc.) |
m_bRandomStartingWeather |
true = random weather on start |
m_bRandomWeatherChanges |
true = the weather can change during gameplay |
m_fXpMultiplier |
XP multiplier for players, if the game mode uses XP (1 = default) |
m_bMapMarkerEnableDeleteByAnyone |
true = map markers can be deleted by anyone in the faction, false = only by the player who placed them |
m_iMapMarkerLimitPerPlayer |
How many map markers a player can have at the same time |
m_aFactionLimits |
Maximum number of players per faction (from version 1.7, see below) |
m_sMagazineRepackingRulesOverride |
Rules for repacking magazines, e.g., "CAN_WITH_SAME_CALIBER" (from version 1.9) |
m_sHydrationRulesOverride |
Rules for hydration (drinking), e.g., "DISABLED" (from version 1.9) |
Set Faction Limits
With m_aFactionLimits, you set how many players can join a faction at most. Each faction is specified by its faction key, e.g., US, USSR or FIA:
"missionHeader": {
"m_aFactionLimits": [
{
"m_sFactionKey": "US",
"m_iFactionLimit": 20
},
{
"m_sFactionKey": "USSR",
"m_iFactionLimit": 20
},
{
"m_sFactionKey": "FIA",
"m_iFactionLimit": 0
}
]
}
Value of m_iFactionLimit |
Meaning |
|---|---|
0 |
Faction is disabled |
-1 |
No limit |
greater than 0 |
Maximum number of players in this faction |
Conflict Settings
These entries only work in Conflict scenarios. For the numeric entries, -1 means that the scenario's default value is used.
| Entry | Description |
|---|---|
m_iControlPointsCap |
How many control points are required to win |
m_fVictoryTimeout |
How long a faction needs to hold a control point, in seconds |
m_iStartingHQSupplies |
How many supplies the main HQ starts with |
m_iMinimumBaseSupplies |
Minimum starting supplies in small bases |
m_iMaximumBaseSupplies |
Maximum starting supplies in small bases |
m_bIgnoreMinimumVehicleRank |
true = no rank requirement for spawning vehicles |
m_fSupplyOffloadAssistanceReward |
Share of XP for players who unload supplies they did not load themselves |
Saving and Automatic Saves
You set how often the server saves the game state automatically with the "persistence" entry. It is also located inside "gameProperties", but outside the missionHeader. Follow the steps under How to Add the missionHeader: stop the server, edit config.json via SFTP, start the server.
"gameProperties": {
"persistence": {
"autoSaveInterval": 15,
"saveRetention": 5
}
}
Leave the other entries in "gameProperties" unchanged.
| Entry | Description |
|---|---|
autoSaveInterval |
Interval between automatic saves in minutes (0 to 60, default 10, 0 = disabled) |
saveRetention |
How many save points are kept for the current scenario (1 to 128, default 10) |
If you want to disable saving completely, set the m_eSaveTypes entry in the missionHeader to 0:
"missionHeader": {
"m_eSaveTypes": 0
}