R3vo/Sandbox2 – User

From Bohemia Interactive Community
Jump to navigation Jump to search
mNo edit summary
m (cleared)
Tag: Blanking
 
(38 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{TOC|side}}


Arma 3: Server Config File
The server configuration file can be used to configure various game server settings such as the difficulty level, how many votes are needed and welcome messages.
The name of the file is determined by the <tt>[[-config]]</tt> command line option when launching the dedicated server. There is no default name - when you do not specify the filename, no server configuration file is loaded.
== Server Options ==
{| class="wikitable sortable" style="width: 100%"
! Parameter !! Default!! Description !! Since
|-
| <tt>passwordAdmin = "xyzxyz";</tt> || <tt>""</tt> || Password to protect admin access. || -
|-
| <tt>password = "xyz";</tt> || <tt>""</tt> || Password required to connect to server. || -
|-
| <tt>serverCommandPassword = "xyzxyz";</tt> || <tt>""</tt> || Password required by alternate syntax of [[serverCommand]] server-side scripting. || -
|-
| <tt>hostname="My Server";</tt> || <tt>UNKNOWN</tt> || Servername visible in the game browser. || -
|-
| <tt>maxPlayers = 10;</tt> || <tt>64</tt>(DS) || The maximum number of players that can connect to server. The final number will be lesser between number given here and number of mission slots. || -
|-
| <tt>motd[]= {"Welcome to my server.", "Hosted in the net."};</tt> || <tt>{}</tt> || Two lines welcome message. Comma is the 'new line' separator. || -
|-
| <tt>admins[] = {"<UID>"};</tt> || <tt>{}</tt> || Whitelisted clients can use #login w/o password. See [[server.cfg#Logged_In_Admin|Logged In Admin]] || {{GVI|arma3|1.70}}
|-
| <tt>headlessClients[] = {"<IP>"};</tt> || <tt>{}</tt> || Headless clients IPs. Multiple connections and addresses are allowed in the case of more than one Headless Client. See [[Arma 3: Headless Client]] || ?
|-
| <tt>localClient[] = {"<IP>"};</tt> || <tt>{}</tt> || Indicates clients with ''unlimited'' bandwidth and ''nearly no latency''. See [[Arma 3: Headless Client]] || {{GVI|arma2oa}}
|-
! colspan="3" | Server Behaviour
|-
| <tt>voteThreshold = 0.33;</tt> || <tt>UNKNOWN</tt> || Percentage of votes needed to confirm a vote. <tt>33%</tt> in this example. || ?
|-
| <tt>voteMissionPlayers = 3;</tt> || <tt>UNKNOWN</tt> || Start mission-voting when ''X'' numberOfPlayers connect. || ?
|-
| <tt>allowedVoteCmds[] = { {"kick", false, false, 0.75} };</tt> || <tt>{}</tt> || See [[Arma 3: Mission voting]] || ?
|-
| <tt>allowedVotedAdminCmds[] = { { "mission", true, true } }; || <tt>{}</tt> || </tt> See [[Arma 3: Mission voting]] || ?
|-
| <tt>kickduplicate = 1;</tt> || <tt>UNKNOWN</tt> || Do not allow duplicate ''game IDs''. Second player with an existing ID will be kicked automatically. <tt>1</tt> means active, <tt>0</tt> disabled. || ?
|-
| <tt>loopback = true;</tt> || <tt>false</tt> || Adding this option will force server into LAN mode. This will allow multiple local instances of the game to connect to the server for testing purposes. At the same time it will prevent all non-local instances from connecting. || ?
|-
| <tt>upnp = true;</tt> || <tt>false</tt> || Automatically creates port mapping on UPNP/IGD enabled router. This option allows you to create a server behind NAT (your router must have public IP and support UPNP/IGD protocol). Read more [https://en.wikipedia.org/wiki/Internet_Gateway_Device_Protocol Internet Gateway Device (IGD) Standardized Device Control Protocol]. || ?
{{Feature|warning|When enabled then this setting may delay server start-up by 600s (standard UDP timeout of 10 minutes) if blocked on firewall or bad routing etc. Thus in such case is recommended to disable it.}}
|-
| <tt>allowedFilePatching = 0;</tt> || <tt>0</tt> || Prevent or allow file patching for the clients (including the HC)
* 0 is no clients
* 1 is Headless Clients only
* 2 is all clients
| {{GVI|arma3|1.50}}
|-
| <tt>allowedLoadFileExtensions[] = {"sqf","txt"};</tt> || <tt>UNKNOWN</tt> || Only allow files with listed extensions to be loaded via [[loadFile]] command || {{GVI|arma3|1.20}}
|-
| <tt>allowedPreprocessFileExtensions[] = {"sqf","sqs"};</tt> || <tt>UNKNOWN</tt> || Only allow files with listed extensions to be loaded via [[preprocessFile]] / [[preprocessFileLineNumbers]] commands || {{GVI|arma3|1.20}}
|-
| <tt>allowedHTMLLoadExtensions[] = {"htm","html"};</tt> || <tt>UNKNOWN</tt> || Only allow files and URLs with listed extensions to be loaded via [[htmlLoad]] command || {{GVI|arma3|1.28}}
|-
| <tt>allowedHTMLLoadURIs[] = {"http://arma3.com"};</tt> || <tt>UNKNOWN</tt> || Only allow files from listed URIs and URLs to be loaded via [[htmlLoad]] command. Comment out if not used. Can use += to add to the existing list.
|-
| <tt>filePatchingExceptions[] = {"123456789","987654321"};</tt> || <tt>{}</tt> || Whitelisted Steam IDs allowed filePatching
|-
| <tt>disconnectTimeout = 5;</tt> || <tt>90</tt> || Server wait time before disconnecting client after loss of active traffic connection, range 5 to 90 seconds. || {{GVI|arma3|1.56}}
|-
| <tt>maxdesync = 150;</tt> || <tt>UNKNOWN</tt> || Max desync value until server kick the user || {{GVI|arma3|1.56}}
|-
| <tt>maxping= 200;</tt> || <tt>UNKNOWN</tt> || Max ping value until server kick the user || {{GVI|arma3|1.56}}
|-
| <tt>maxpacketloss= 50;</tt> || <tt>UNKNOWN</tt> || Max packetloss value until server kick the user || {{GVI|arma3|1.56}}
|-
| <tt>kickClientsOnSlowNetwork[] = { 0, 0, 0, 0 };</tt> || <tt>UNKNOWN</tt> || Defines if <tt>{<MaxPing>, <MaxPacketLoss>, <MaxDesync>, <DisconnectTimeout>}</tt> will be logged (0) or kicked (1) || {{GVI|arma3|1.56}}
|-
| <tt>enablePlayerDiag = 1</tt> || <tt>0</tt> || Logs players' bandwidth and desync info every 60 seconds, as well as "network message is pending" owner identity.
|-
| <tt>callExtReportLimit = 1000;</tt> || <tt>1000</tt> || If server initiated [[callExtension]] takes longer than specified limit in milliseconds, the warning will be logged into server <tt>.rpt</tt> file as well as reflected in the extension return result. Default: 1000
|-
| <tt>kickTimeout[] = { {0, -1},{1, 180},{2, 180},{3, 180} };</tt> ||
<tt>kickTimeout[] = { {kickID, timeout}, ... };</tt><br>
kickID (type to determine from where the kick originated e.g. admin or votekick etc.)
* 0 - manual kick (vote kick, admin kick, bruteforce detection etc.)
* 1 - connectivity kick (ping, timeout, packetloss, desync)
* 2 - BattlEye kick
* 3 - harmless kick (wrong addons, steam timeout or checks, signatures, content etc.)<br>
timeout = in seconds how long until kicked player can return
* >0 seconds
* -1 until missionEnd
* -2 until serverRestart<br>
(since Arma 3 1.90+ PerformanceBranch)
|-
| <tt>votingTimeOut = 60;</tt> or<br><tt>votingTimeOut[] = {60, 90};</tt> || default value is 60 seconds for voting<br>60 seconds for ready, 90 for notReady<br>(since Arma 3 v1.90 PerformanceBranch)
|-
| <tt>roleTimeOut = 90;</tt> or<br><tt>roleTimeOut[] = {90, 120};</tt> || default value is 90 s for lobby<br>90 seconds for ready, 120 for notReady<br>(since Arma 3 v1.90 PerformanceBranch)
|-
| <tt>briefingTimeOut = 60;</tt> or<br><tt>briefingTimeOut[] = {60, 90};</tt> || default value is 60 s for briefing<br>60 seconds for ready, 90 for notReady<br>(since Arma 3 v1.90 PerformanceBranch)
|-
| <tt>debriefingTimeOut = 45;</tt> or<br><tt>debriefingTimeOut[] = {45, 60};</tt> || default value is 45 s for debriefing<br>60 seconds for ready, 60 for notReady<br>(since Arma 3 v1.90 PerformanceBranch)
|-
| <tt>lobbyIdleTimeout = 300;</tt> || default value is 300 seconds (+5 seconds vs any of above) > defined value<br>
Independent of set lobbyIdleTimeout in the config file, it will be at least<br>
MAX(votingTimeout, lobbyTimeout, briefingTimeout, debriefingTimeout) + 5 seconds<br>
by default, this makes it 300 seconds of time for people in lobby and 95 in roleTimeout or briefing screen<br>
(since Arma 3 1.90+ PerformanceBranch)
|-
| <tt>missionsToServerRestart = 8;</tt> || Number of times missionEnd happens before server initiate process restart (uses actual session startup command-line parameters, not possible to combine with `missionsToShutdown` )<br>
|-
| <tt>missionsToShutdown = 8;</tt> || Number of times missionEnd happens before server initiate process shutdown (has same behavior as setting named `missionsToHardRestart`)<br>
|-
| <tt>autoSelectMission = true;</tt> || When enabled, the server auto-starts next mission in mission cycle and waits for players in the role selection.<br>
This allows full mission information in server browser and then results in proper filtering of the servers.<br>
This is lesser-variant (trimmed) of server startup command-line parameter `-autoInit`<br>
Might collide with campaign linked missions / need mission cycle etc.
|-
| <tt>randomMissionOrder = true;</tt> || When enabled, the server random start / next selection with one of missions from mission rotation list. ( setting goes outside(before) Mission class {}; )
|-
| <tt>disableChannels[] = { {0,false,true} };</tt> ||
<tt>disableChannels[] = { {channelID, text, voice}, ... }>;</tt><br>
* ''ChannelID'' : [[Number]] - use single digit of (0 to 6) to define channelID. Default: No restriction to any channels, with text/von chat set to false.<br>
* ''text'' : [[Boolean]] - use [[true]] to disable usage of text-chat for defined channelID. Default: '''[[false]]'''<br>
* ''voice'' : [[Boolean]] - use [[true]] to disable usage of voice-chat (VON) for defined channelID. Default: '''[[false]]'''<br>
List of channels ID:<br>
* 0 = Global
* 1 = Side
* 2 = Command
* 3 = Group
* 4 = Vehicle
* 5 = Direct
* 6 = System<br>
{{Feature|Informative|Missions which use [[Description.ext#disableChannels|Description.ext#disableChannels]] will override any setting of ''disableChannels[]'' in the '''server.cfg'''.}}
|-
! colspan="3" | Other Options
|-
| <tt>verifySignatures = 2;</tt> || Enables or disables the [[ArmA: Addon Signatures|signature verification]] for addons.
* Default = <tt>2</tt>.
* Verification disabled = <tt>0</tt>.
** <tt>1</tt> Will default back to <tt>2</tt>
|-
| <tt>drawingInMap = false;</tt> || Enables or disables the ability to place markers and draw lines in map. Default: <tt>true</tt> (since Arma 3 v1.64).
|-
| <tt>disableVoN = 1;</tt> || Enables or disables the '''''V'''oice '''o'''ver '''N'''et''. Default = <tt>0</tt>.
|-
| <tt>vonCodecQuality = 10;</tt> || Defines ''VoN'' codec quality. Value range is from <tt>1</tt> to <tt>20</tt>.
* Default = <tt>3</tt>.
* Since 1.62.95417 supports range <tt>1-20</tt>
* Since 1.63.x will support range <tt>1-30</tt>
* 8kHz is <tt>0-10</tt>, 16kHz is <tt>11-20</tt>, for <tt>21-30</tt> it is 32kHz for SPEEX codec and 48kHz for OPUS codec.
|-
| <tt>vonCodec = 1;</tt> || Defines ''VoN'' codec type. Value range is from <tt>0</tt> to <tt>1</tt>.
* Default = <tt>0</tt>.
* Since Arma 3 update 1.58 supports value <tt>1</tt>
* Value <tt>0</tt> uses older [https://en.wikipedia.org/wiki/Speex SPEEX codec], while <tt>1</tt> switches to new IETF standard [https://en.wikipedia.org/wiki/Opus_(audio_format) OPUS codec].
|-
| <tt>skipLobby = false;</tt> || If true, joining player will skip role selection. This is only used if no Mission, Campaign or Config setting <tt>skipLobby</tt> is defined (See [[Description.ext#skipLobby]]). Default: false;
|-
| <tt>logFile = "server_console.log";</tt> || Enables output of dedicated server console into ''textfile''. Default location of log is same as ''crash dumps'' and other logs.<br>
(Local settings) Note that this does not change the location of the "''net.log''" file, which you enable with the <tt>-netlog</tt> command line option.
|-
| <tt>steamPort = <number>;</tt> || Default <tt>2303</tt>, defines port for communication with STEAM services, needs to be unique for each dedicated server within one OS instance / network interface<br/>{{Feature | Informative | Since {{arma3}} v1.24, Steam ports are '''hardcoded as now linked to game-port of the server instance (+1 query +2 report to master)'''.}}
|-
| <tt>steamQueryPort = <number>;</tt> || default <tt>2304</tt>, defines port for server's STEAM query, needs to be unique for each dedicated server within one OS instance / network interface<br/>{{Feature | Informative | Since {{arma3}} v1.24, Steam ports are '''hardcoded as now linked to game-port of the server instance (+1 query +2 report to master)'''.}}
|-
| <tt>doubleIdDetected = "command";</tt> || rowspan="7" colspan="2" align="center" | see [[ArmA: Server Side Scripting|Server Side Scripting]]
|-
| <tt>onUserConnected = "command";</tt>
|-
| <tt>onUserDisconnected = "command";</tt>
|-
| <tt>onHackedData = "command";</tt>
|-
| <tt>onDifferentData = "command";</tt>
|-
| <tt>onUnsignedData = "command";</tt>
|-
| <tt>onUserKicked = "command";</tt>
|-
| <tt>regularCheck = "command";</tt>
|-
| <tt>BattlEye = 1;</tt> || Enables or disables the [[BattlEye]] anti-cheat engine. Default <tt>0</tt>. - since 1.09 beta, in Arma 3 default is 1. Requires installed battleye on server and clients joining the server
|-
| <tt>timeStampFormat = "short";</tt> || Set the timestamp format used on each report line in server-side [[Crash Files|RPT file]]. Possible values are "none" (default), "short", "full".
|-
| <tt>forceRotorLibSimulation = 0;</tt> || Enforces the Advanced Flight Model on the server. Default = <tt>0</tt> (up to the player). <tt>1</tt> - forced AFM, <tt>2</tt> - forced SFM.
|-
| <tt>persistent = 1;</tt> || Mission keeps running when all clients disconnect.. Default = <tt>0</tt>. Enabling the persistence option will make missions that have either ''base'' or ''instant'' respawn keep on running after all players have disconnected.
The other respawn types will not make a mission persistent. The kind of respawn a certain mission uses is set in its [[Description.ext]].
|-
| <tt>requiredBuild = xxxxx;</tt> || Minimum required client version. Clients with version lower than <tt>requiredBuild</tt> will not be able to connect. If <tt>requiredBuild</tt> is set to a large number, like <tt>requiredBuild = 999999999;</tt> for example, it will automatically be lowered to the current server version.
|-
| <tt>statisticsEnabled = <number>;</tt> || default <tt>1</tt>, allows to opt-out of [[Arma 3: Analytics|Arma 3 analytics]] for the server by using 0 || {{GVI|arma3|1.56}}
|-
| <tt>forcedDifficulty = "regular";</tt> || Enforces the selected difficulty on the server.
<br><br>
<tt>'''forcedDifficulty''' = "<difficultyClass>";</tt>
<br><br>
* If Recruit, Regular or Veteran is passed as the parameter, the particular difficulty options will be taken from data config, from the class CfgDifficultyPresets.
* If Custom will be passed as the parameter, the particular flags will be taken from CustomDifficulty class from server's profile (only Custom is saved to the profile).
* If mission cycle is defined in the [[server.cfg]], the difficulty set in the mission cycle overrides the difficulty set by '''forcedDifficulty''' parameter. || {{GVI|arma3|1.56}}
|-
| <tt>missionWhitelist[] = {"intro.altis"};</tt> || Limit the available missions for the admin for the mission change. See [[Arma 3: MP Mission Name]] for a full list. || {{GVI|arma3|1.56}}
|-
| <tt>steamProtocolMaxDataSize = 1024;</tt> || Limit for maximum Steam Query packet length. (since Arma 3 v2.00)<br>
Increasing this value is dangerous as it can cause Arma server to send UDP packets of a size larger than the MTU. This will cause UDP packets to be fragmented which is not supported by some older routers.<br>
But increasing this will fix the modlist length limit in Arma 3 Launcher.
|-
|
<syntaxhighlight lang="cpp">
class AdvancedOptions
{
    LogObjectNotFound = true; // (default true, logging enabled)
    SkipDescriptionParsing = false; // (default false, parse description.ext)
    ignoreMissionLoadErrors = false;
};</syntaxhighlight>
|
{{GVI|arma3|2.02}}
* LogObjectNotFound - [[false|False]] to skip logging "Server: Object not found" messages
* SkipDescriptionParsing - [[true|True]] to skip parsing of description.ext/mission.sqm. Will show pbo filename instead of configured missionName. OverviewText and such won't work, but loading the mission list is a lot faster when you have many missions
{{GVI|arma3|2.04}}
* ignoreMissionLoadErrors -  When server log gets filled with  too many logs entries the mission loading will be aborted and jump bad to mission selection, this forces the server to continue loading mission {{Clarify}}
|}
== Server Administration ==
If you are not using BattlEye RCon, there could only be 1 server admin at any given time. There are two ways of becoming admin, through a vote or through login with authenticated credentials.
=== Voted In Admin ===
It is possible to become a server administrator through player voting process. Such admin has less abilities than logged in admin.<br>
For example, voted in admin would be able to kick a player, but only logged in admin would be able to ban a player.<br>
For more information on voting and voting configuration see page [[Arma_3:_Mission_voting|'''Server Voting''']].
=== Logged In Admin ===
To log in as admin, one is required to type in<tt>#login</tt> command followed by server password, which matches password defined in '''passwordAdmin''' param.<br>
Since Arma2OA it is possible to add one or several user ids [[getPlayerUID|UIDs]] into '''admins[]''' server config parameter, which would allow listed users to log in as admin by simply typing <tt>#login</tt> without a password.<br>
This presents several advantages for managing the servers. The server owner can have multiple admins selected from the community and doesn't have to provide each one with server admin password.<br>
The adding and removing of UIDs is done on the server side which makes it easy to add and to remove admins if necessary. On the server, admins are handled on first come first served basis.<br>
Here are the rules:<br>
* If there is already a logged in admin on the server, the new admin will not be able to log in until previously logged in admin logs out
* If there is a voted in admin on the server, the logged in admin will override voted in admin and take admin role
* There is no difference between logged in admin that used admin password or logged in admin that was whitelisted with '''admins[]''' param
<br>
The logged in and voted in admins have different set of '''[[Multiplayer Server Commands]]''' available to them. See '''[[serverCommandAvailable]]''' for more information.
=== Server Security ===
Please check following link for security settings: '''[[Arma_3:_Server_Security]]'''
== Example Configuration File ==
<spoiler><syntaxhighlight lang="cpp">
// server.cfg
// GLOBAL SETTINGS
hostname = "Fun and Test Server"; // The name of the server that shall be displayed in the public server list
password = ""; // Password for joining, eg connecting to the server
passwordAdmin = "xyz"; // Password to become server admin. When you're in Arma MP and connected to the server, type '#login xyz'
serverCommandPassword = "xyzxyz"; // Password required by alternate syntax of [[serverCommand]] server-side scripting.
logFile = "server_console.log"; // Where the logfile should go and what it should be called
// WELCOME MESSAGE ("message of the day")
// It can be several lines, separated by comma
// Empty messages "" will not be displayed at all but are only for increasing the interval
motd[] = {
"", "",
"Two empty lines above for increasing interval",
"Welcome to our server",
"", "",
"We are looking for fun - Join us Now !",
"http://www.example.com",
"One more empty line below for increasing interval",
""
};
motdInterval = 5; // Time interval (in seconds) between each message
// JOINING RULES
maxPlayers = 64; // Maximum amount of players. Civilians and watchers, beholder, bystanders and so on also count as player.
kickDuplicate = 1; // Each ArmA version has its own ID. If kickDuplicate is set to 1, a player will be kicked when he joins a server where another player with the same ID is playing.
verifySignatures = 2; // Verifies .pbos against .bisign files. Valid values 0 (disabled), 1 (prefer v2 sigs but accept v1 too) and 2 (only v2 sigs are allowed).
equalModRequired = 0; // Outdated. If set to 1, player has to use exactly the same -mod= startup parameter as the server.
allowedFilePatching = 0; // Allow or prevent client using -filePatching to join the server. 0, is disallow, 1 is allow HC, 2 is allow all clients (since Arma 3 v1.50)
filePatchingExceptions[] = {"123456789","987654321"}; // Whitelisted Steam IDs allowed to join with -filePatching enabled
//requiredBuild = 12345; // Require clients joining to have at least build 12345 of game, preventing obsolete clients to connect
// VOTING
voteMissionPlayers = 1; // Tells the server how many people must connect so that it displays the mission selection screen.
voteThreshold = 0.33; // 33% or more players need to vote for something, for example an admin or a new map, to become effective
// INGAME SETTINGS
disableVoN = 0; // If set to 1, Voice over Net will not be available
vonCodec = 1; // If set to 1 then it uses IETF standard OPUS codec, if to 0 then it uses SPEEX codec (since Arma 3 update 1.58+)
vonCodecQuality = 30; // since 1.62.95417 supports range 1-20 //since 1.63.x will supports range 1-30 //8kHz is 0-10, 16kHz is 11-20, 32kHz(48kHz) is 21-30
persistent = 1; // If 1, missions still run on even after the last player disconnected.
timeStampFormat = "short"; // Set the timestamp format used on each report line in server-side RPT file. Possible values are "none" (default),"short","full".
BattlEye = 1; // Server to use BattlEye system
allowedLoadFileExtensions[] = {"hpp","sqs","sqf","fsm","cpp","paa","txt","xml","inc","ext","sqm","ods","fxy","lip","csv","kb","bik","bikb","html","htm","biedi"}; //only allow files with those extensions to be loaded via loadFile command (since Arma 3 build 1.19.124216)
allowedPreprocessFileExtensions[] = {"hpp","sqs","sqf","fsm","cpp","paa","txt","xml","inc","ext","sqm","ods","fxy","lip","csv","kb","bik","bikb","html","htm","biedi"}; //only allow files with those extensions to be loaded via preprocessFile/preprocessFileLineNumber commands (since Arma 3 build 1.19.124323)
allowedHTMLLoadExtensions[] = {"htm","html","xml","txt"}; //only allow files with those extensions to be loaded via HTMLLoad command (since Arma 3 build 1.27.126715)
//allowedHTMLLoadURIs[] = {}; // Leave commented to let missions/campaigns/addons decide what URIs are supported. Uncomment to define server-level restrictions for URIs
// TIMEOUTS
disconnectTimeout = 5; // Time to wait before disconnecting a user which temporarly lost connection. Range is 5 to 90 seconds.
maxDesync = 150; // Max desync value until server kick the user
maxPing= 200; // Max ping value until server kick the user
maxPacketLoss= 50; // Max packetloss value until server kick the user
kickClientsOnSlowNetwork[] = { 0, 0, 0, 0 }; // Defines if {<MaxPing>, <MaxPacketLoss>, <MaxDesync>, <DisconnectTimeout>} will be logged (0) or kicked (1)
kickTimeout[] = { {0, -1}, {1, 180}, {2, 180}, {3, 180} };
votingTimeOut[] = {60, 90}; // Kicks users from server if they spend too much time in mission voting
roleTimeOut[] = {90, 120}; // Kicks users from server if they spend too much time in role selection
briefingTimeOut[] = {60, 90}; // Kicks users from server if they spend too much time in briefing (map) screen
debriefingTimeOut[] = {45, 60}; // Kicks users from server if they spend too much time in debriefing screen
lobbyIdleTimeout = 300; // The amount of time the server will wait before force-starting a mission without a logged-in Admin.
// SCRIPTING ISSUES
onUserConnected = "";
onUserDisconnected = "";
doubleIdDetected = "";
// SIGNATURE VERIFICATION
onUnsignedData = "kick (_this select 0)"; // unsigned data detected
onHackedData = "kick (_this select 0)"; // tampering of the signature detected
onDifferentData = ""; // data with a valid signature, but different version than the one present on server detected
// MISSIONS CYCLE (see below)
randomMissionOrder = true; // Randomly iterate through Missions list
autoSelectMission = true; // Server auto selects next mission in cycle
class Missions {}; // An empty Missions class means there will be no mission rotation
missionWhitelist[] = {}; // An empty whitelist means there is no restriction on what missions' available</syntaxhighlight></spoiler>
=== Mission rotation ===
One can set an automatic mission rotation. Without an admin, the server will automatically select a mission when at least one player is connected. Once the mission is done and if there are still players on the server, it will automatically switch to the next in the cycle.
Example:<br>
{{Feature | Informative | When difficulty is set to <tt>difficulty {{=}} "Custom";</tt> the server will look into <tt>USERNAME.Arma3Profile</tt> file for the definition of custom difficulty, which should look like this: [[server.armaprofile#Server_Difficulty_Example | click to see example]]}}
<syntaxhighlight lang="cpp">
class Missions
{
class TestMission01
{
template = MP_Marksmen_01.Altis;
difficulty = "veteran";
class Params {};
};
class TestMission02
{
template = MP_End_Game_01.Altis;
difficulty = "veteran";
class Params {};
};
class TestMission03
{
template = MP_End_Game_02.Altis;
difficulty = "veteran";
class Params {};
};
class TestMission04
{
template = MP_End_Game_03.Altis;
difficulty = "veteran";
class Params {};
};
};
</syntaxhighlight>
=== Arma 3: Apex - Mission collection ===
Mainly intended for MP campaigns. If the progress is defined in the MPMissions class, server administrator can simply add the whole campaign by adding ''campaign class'' into the ''server.cfg''. See the example below.
'''config.cpp:'''
<syntaxhighlight lang="cpp">
class MPMissions
{
class Apex
{
briefingName = $STR_A3_CoopCampaignName;
class EXP_m01
{
briefingName = $STR_A3_exp_m01_missionname;
directory = "a3\missions_f_exp\campaign\missions\exp_m01.tanoa";
};
class EXP_m02
{
briefingName = $STR_A3_exp_m02_missionname;
directory = "a3\missions_f_exp\campaign\missions\exp_m02.tanoa";
};
class EXP_m03
{
briefingName = $STR_A3_exp_m03_missionname;
directory = "a3\missions_f_exp\campaign\missions\exp_m03.tanoa";
};
};
};
</syntaxhighlight>
'''server.cfg:'''
<syntaxhighlight lang="cpp">
// MISSIONS CYCLE
class Missions
{
class Apex{};
};
</syntaxhighlight>
Also the difficulty of the each mission can be overridden
<syntaxhighlight lang="cpp">
class Missions
{
class Apex
{
class EXP_m01
{
difficulty = "veteran";
};
};
};
</syntaxhighlight>
==== Additional details ====
For hosting server behind NAT or firewall, please ensure gameport and STEAMports are forwarded and open!<br>
Set the ICMP "echo reply" as allowed so the server is able return ping delay properly.<br>
It's recommended to enable the NAT traversal (so called "Edge traversal" in Windows Firewall) for '''arma3server.exe''', '''arma3.exe''' to better support clients/servers behind NAT.
==== Overriding mission params ====
On dedicated server unless you are an admin you cannot set mission options provided by mission maker via class Params. However as a server owner you can override default setting with your own. See [[Mission Parameters]] for more info
== See Also ==
* [[basic.cfg|Server Basic Config file]]
* [[Arma 3: Startup Parameters]]
* [[Arma 3: Dedicated Server]]
* [[Arma 3: Headless Client]]
* [[Arma 3: Server Security]]
* [[Arma 3: Mission voting]]
{{GameCategory|arma3|Multiplayer}}
--------------------------------
<!---
<div style="box-shadow: 0 0 1em #000000CC; padding: 1em 2em">
{{TOC|side|1|2}}
As with any good public forum, rules and guidelines help maintain order and sanity among readers and editors. The following rules and guidelines are designed so that people will return here to contribute and find quality information. Respecting these rules will help in providing a positive experience for both editors and readers alike.
= Rules of Conduct =
The '''Rules of Conduct''' regulate the interaction between Wiki members. These are in place to ensure that the Wiki remains a civilised place where people can share information freely, without being harassed or abused.
; No Flaming / Flame-baiting
: Abusive comments, personal attacks and name calling are not allowed.
; No bigotry
: Racist, sexist, homophobic or any other type of bigoted posts are not tolerated on this Wiki. Such offences will result in an immediate and permanent block.
: No discussion about illegally obtained software
=== Follow the instructions of the Wiki Admins ===
When a [[Bohemia_Interactive_Community:Administrators|Wiki Sysop]] asks you to stop doing something, please follow their instructions.
=== No Spam ===
We define spam as an article or post that has no real worth, is irrelevant, useless and offers nothing to a discussion. Spam is not limited to text - posting an image as a means of spamming, or as a link to a spam site, will also result in deletion. With spam being hard to define, that decision is left to the moderators' discretion. If in doubt ask yourself "does my reply add any constructive insight to the discussion"? If not, then this Wiki would not be the right place to post your comment.
=== Images ===
No posting of pictures containing porn, real killings, mutilations, wounds, carnage and other disgusting/explicit images. This also includes links to pages that contain such images. The only accepted images for this Wiki must be related to a product of Bohemia Interactive. Keep the following guidelines in mind when uploading and posting pictures here:
* Do not use hotlinked images in the Wiki. Use the [[Special:Upload|Upload file]] function instead to upload images to this Wiki.
* Name the image correctly <tt>gameShort_what_does_it_do.jpg</tt>
** <tt>A3_Briefing_Image.jpg</tt>
** <tt>OFP_Helicopter_Attacking.jpg</tt>
* When appropriate use an image thumbnail on the article page (such as on the [[Operation Flashpoint: Easter Eggs|{{ofp}}: Easter Eggs]] page).
* Avoid using a text link to point to an image. Display the image as thumbnail or sized appropriately for the article.
= Discussion Pages =
Discussion pages are now only used for keeping information for historic reasons. For discussions please join the '''Arma Discord server'''.
= Mod Pages =
{{Feature|important|I'd prefer not to have any community content on this biki (only exception being mikero tools and stuff from the past) [[User:R3vo|R3vo]] ([[User talk:R3vo|talk]]) 16:21, 7 January 2021 (CET)}}
You are welcome to announce your mods on this Wiki under the respective categories ([[:Category:Operation Flashpoint: Community Mod Pages|OFP]] or [[:Category:ArmA: Addon Groups|ArmA]]), but these should be limited to an ''overview'' of your mod, rather than a full-scale documentation.<br>
Each modder (or mod group) is allowed to have a one page description, with up to 8 images embedded. If images for this page are uploaded to this Wiki, their individual size should not exceed 100KB. (Images that are hosted elsewhere, and only linked to, do not fall under this limitation.)
= Writing an Article =
* Post only proven facts
* If unsure about whether something is correct or not, ask others on the Arma Discord server or mark the content so others can see that it might not be fully correct
* Do not use abbreviations such as it's, doesn't, aren't ...
* Try to avoid posting external links whenever possible. They might become outdated or content on external pages might change.
* Use simple English, remember, not everyone is a native speaker
* Avoid ALL CAPS, see [[Bohemia_Interactive_Community:Formatting#Text_formatting_markup|text formatting]] to find out how to properly highlight parts of a text
* Use the preview button before submitting changes
* Let others proof-read your creation before posting
= Formating Guidelines =
These guidelines are here to ensure that articles are presented in a clear, understandable and consistent style.
=== Avoid empty lines ===
* No empty lines underneath sections
<noWiki>
=== Avoid empty lines ===
Here starts the text </noWiki>
=== Categorise your Article ===
Categories help to properly sort the content on this biki.
* Keep the categories to a minimum. Only add the categories which are most relevant and avoid duplication.
=== No Introduction ===
* Do not create an '''Introduction''' section. The text the page starts with is considered the introduction already.
=== Summarise your Changes ===
* When making only small edits check the "This is a minor edit" box at the bottom.
{{Feature|informative|By default all edits are markes as "major". This can be changed to "minor" in your preferences setting.}}
* Add a short summary of what you changed e.g., ''Fixed typo'', ''Removed category''
=== Use Full Names for Titles ===
{{Feature|important|Make use of name templates and GameCategory [[User:R3vo|R3vo]] ([[User talk:R3vo|talk]]) 16:21, 7 January 2021 (CET)}}
When creating new categories or articles, consider the naming convention you are going to use.
<nowiki>[[Operation Flashpoint: Elite]] is more acceptable than [[OFP:Elite]]. The new category or article should almost always be [[Game Title: something]] such as [[Operation Flashpoint: Addons]].</nowiki>
<nowiki>Your choice should always be clear and concise for the reader, and easy for the editor to link back to. Keep in mind that you can use spaces in the name of the article (e.g. [[Armed Assault: Easter Eggs]] would be better than [[Armed Assault:EasterEggs]])</nowiki>
Refer to the [[Naming Conventions]] page for choosing the appropriate name when writing articles.
= Deletion Guidelines =
* Mark pages for deletion first with <noWiki>{{Wiki|delete}}</noWiki> if in doubt
* Pages containing text with no meaning, test pages or similar can be deleted if they are not being used frequently
* Pages marked for deletion with <nowiki>{{Wiki|delete}}</nowiki>
* Information about non-BI games
* Any content that is violating the copyright holder's rights or any other EULA
</div>
[[Category:Bohemia Interactive Community:Policies]]

Latest revision as of 23:33, 3 August 2023

Retrieved from "https://community.bistudio.com/wiki?title=User:R3vo/Sandbox2&oldid=346744"