Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
This topic has been locked 
Discussions Rules and Guidelines
Report this post
i used https://forums.dayz.com/topic/239635-dayz-server-files-documentation/?tab=comments#comment-2396561
https://write.corbpie.com/installing-and-setting-up-a-dayz-standalone-server-on-windows-server-2016-guide/
https://www.youtube.com/watch?v=MU00YZTNLxQ
https://www.youtube.com/watch?v=dlxLYy_vsDg
https://www.youtube.com/watch?v=ZLj1xxThHUg
Ports only really need to be open if you want it to be visible and accessible to other players.
COMMUNITY SERVER OWNERS-- READ
Hopefully this will be helpful.
Config Parameters
The server configuration is handled via serverDZ.cfg, a configuration file which you can use to configure various game server settings such as the player count, 3rd person view, and welcome messages. etc. The file usually is located in the root directory of the server but can be placed elsewhere with the startup parameter -config. To ensure, that Steam does not overwrite this file with an update, be sure to have a copy of this original file and rename it.
Required Parameters:
hostname ="EXAMPLE NAME"; // Server name
password = ""; // Password to connect to the server
passwordAdmin = ""; // Password to become a server admin
maxPlayers = 60; // Maximum amount of players
verifySignatures = 2; // Verifies .pbos against .bisign files. (only 2 is supported)
forceSameBuild = 1; // When enabled, the server will allow the connection only to clients with same the .exe revision as the server (value 0-1)
disableVoN = 0; // Enable/disable voice over network (value 0-1)
vonCodecQuality = 7; // Voice over network codec quality, the higher the better (values 0-30)
disable3rdPerson=0; // Toggles the 3rd person view for players (value 0-1)
disableCrosshair=0; // Toggles the cross-hair (value 0-1)
serverTime="SystemTime"; // Initial in-game time of the server. "SystemTime" means the local time of the machine. Another possibility is to set the time to some value in "YYYY/MM/DD/HH/MM" format, f.e. "2015/4/8/17/23" .
serverTimeAcceleration=12; // Accelerated Time (value 0-24)// This is a time multiplier for in-game time. In this case, the time would move 24 times faster than normal, so an entire day would pass in one hour.
serverTimePersistent=0; // Persistent Time (value 0-1)// The actual server time is saved to storage, so when active, the next server start will use the saved time value.
guaranteedUpdates=1; // Communication protocol used with game server (use only number 1)
loginQueueConcurrentPlayers=5; // The number of players concurrently processed during the login process. Should prevent massive performance drop during connection when a lot of people are connecting at the same time.
loginQueueMaxPlayers=500; // The maximum number of players that can wait in login queue
instanceId = 1; // DayZ server instance id, to identify the number of instances per box and their storage folders with persistence files
lootHistory = 1; // How many persistence history files should be kept by instance, number is looped over during save
storeHouseStateDisabled = false;// Disable houses/doors persistence (value true/false), usable in case of problems with persistence
storageAutoFix = 1; // Checks if the persistence files are corrupted and replaces corrupted ones with empty ones (value 0-1)
class Missions
{
class DayZ
{
template="dayzOffline.chernarusplus"; // Mission to load on server startup. <MissionName>.<TerrainName>
};
};
Additional parameters:
respawnTime = 5; // Sets the respawn delay (in seconds) before the player is able to get a new character on the server, when the previous one is dead
motd[] = {"line1","line2"}; // Message of the day displayed in the in-game chat
motdInterval = 1; // Time interval (in seconds) between each message
maxPing= 200; // Max ping value until server kick the user (value in milliseconds)
timeStampFormat = "Short"; // Format for timestamps in the .rpt file (value Full/Short)
logAverageFps = 1; // Logs the average server FPS (value in seconds), needs to have -dologs launch parameter active
logMemory = 1; // Logs the server memory usage (value in seconds), needs to have the -dologs launch parameter active
logPlayers = 1; // Logs the count of currently connected players (value in seconds), needs to have the -dologs launch parameter active
logFile = "server_console.log";// Saves the server console log to a file in the folder with the other server logs
enableDebugMonitor = 1; //shows info about the character using a debug window in a corner of the screen (value 0-1)
steamQueryPort = 2305; // defines Steam query port, should fix the issue with server not being visible in client server browser
Launch Parameters
Run the DayZServer_x64.exe via the batch file, shortcut with parameters or other options.
Parameters:
-config=serverDZ.cfg - Selects the Server Config File
-port=2302 - Port to have dedicated server listen on
-profiles=C:\Users\%USER%\Documents\DayZ Server – Path to the folder containing server profile. By default, server logs are written to server profile folder. Logs/dumps/etc will be created there, along with BattlEye/BEC/Rcon related files. Windows Environment variables are supported (E.g. %userprofile%).
-dologs - Enables all log messages in the server RPT
-adminlog - Enables the admin log
-netlog - Enables the network traffic logging
-freezecheck - Stops the server when frozen for more than 5 min and create a dump file
-noFilePatching - Ensures that only PBOs are loaded and NO unpacked data.
-BEpath= - Sets a custom path to the Battleye files
-cpuCount= - Sets the number of logical CPU cores to use for parallel tasks processing. It should be less or equal than the numbers of available cores.
BattlEye Config
The config file BEServer_x64.cfg needs to be in the same folder as BEServer_x64.dll.The location of this folder can be customized via the startup parameters -bePath and -profiles.
Parameters:
RConPassword MyPassword - Sets the password for the connection of the RCon tool (remote connection admin tool like BEC/Dart)
RestrictRCon 1 - Enables/Disables RCon functions (kick/ban/connection restrictions)
How to Ban
How to Ban
There are currently two ways to ban players from a server:
Create a file ban.txt in the server root folder and add the player UID in a new line (44 characters long id that you can find in .adm or .rpt logs)
Create a file bans.txt in the serverRootDirectory\battleye folder and add the player BE GUID in a new line (32 characters long GUID which you can get from RCon tools like Dart or BEC).
The location of the BattlEye folder can be customized via the startup parameters -bePath and -profiles.
Some RCon tools like Dart offer the option to ban users directly via their UI which is then, written to bans.txt.
Server Messages & How to Restart Automatically:
This section describes the functionality and administration of server messages, which can be used for automatic server termination.
To setup an automatic restart you will need some other app that will automatically start terminated server as Windows Scheduler, FireDaemon or similar application.
Messages for offline database
The server message is a message that is sent to clients from the server at a given point in time.
The server message can be sent in the following manners:
every given number of minutes to all players,
to one player after his connection with possible delay,
and so called 'countdown' message that is sent to all players in predefined times before deadline is met on server ("--- Termination successfully completed ---" line will be written to the .rpt file when the termination is finished).
Flags
On Connect:
*Indicates that the server message will be sent once after a player connects to the server.
Repeat:
*Indicates that the server message will be sending to all players repeatedly.
Countdown:
*Indicates that the server message will be sent to all players in a countdown manner.
The message will be sent 90 minutes before the deadline is met, then 60 minutes, 45, 30, 20, 15, 10, 5, 2 and finally 1 minute before the deadline is met.
Shutdown:
*Indicates that the server will shutdown after countdown reaches zero.
If the Countdown flag is not set, this flag is ignored.
Properties
The maximum length of the message is 160 characters.
User can place 3 different placeholders into the message's text:
#name is replaced with the server's name
#port is replaced with server's port
#tmin is replaced with the number of minutes remaining in the countdown.
It is functional only when the Countdown flag is set.
Every property related to time in the server message is in minutes.
Delay
Applied when the server message has On connect flag set.
This value indicates how many minutes it will take before the message is sent to player.
Value of zero means that the message will be sent immediately after the player connects to
server.
Repeat
Applied when the server message has the Repeat flag set.
This value controls the frequency of the message repetition.
Deadline
Applied when the server message has the Countdown flag set.
Indicates how long it takes the countdown before it reaches zero.
Offline database
Server messages can be added, updated or deleted in the messages.xml file under the db folder placed inside mission's folder (server_root\mpmissions\dayzOffline.chernarusplus\db\messages.xml). It is not currently part of Steam server data package so you will have to create it yourself.
For automatic server termination set "deadline" and "shutdown" to enabled.
Example messages.xml
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<messages>
<!-- This is example message for automatic server termination -->
<message>
<!-- no delay -->
<delay>0</delay>
<!-- if the value is larger than 0, then flag Repeat is enabled -->
<repeat>0</repeat>
<!-- if the value is larger than 0, then flag Countdown is enabled,
countdown reaches zero in 10 hours -->
<deadline>600</deadline>
<!-- disable On connect flag -->
<onconnect>0</onconnect>
<!-- enable Shutdown flag -->
<shutdown>1</shutdown>
<!-- message itself with placeholders -->
<text>Hello, this server (#name) will shutdown in #tmin minutes.</text>
</message>
</messages>
Taskkill
If you don't want to use messages.xml for the automatic server termination, you can go with taskkill instead (link to Microsoft documentation).
All you need to do is use Windows Scheduler, FireDaemon or similar application to send the taskkill command without /f parameter and you will invoke graceful shutdown of DayZ server application ("--- Termination successfully completed ---" line will be written to the .rpt file when the termination is finished).
taskkill /im DayZServer_x64.exe
To setup an automatic restart you will need some other application that will automatically start the terminated server as Windows Scheduler, FireDaemon or a similar application.
https://steamcommunity.com/app/221100/discussions/0/3315110799613736561/