DayZ

From TRUgaming Wiki
Jump to navigation Jump to search

Main Page | All_Supported_Games

Client Side Notes[edit]

If you don't want to show up as Survivor.... :-)
You can change your name by adding the -name= parameter to your Steam Launch options.
SteamDZLaunch.png
Example: -name=TRUGaming
SteamDZName.png
The result:
DZName.png

Server Administration[edit]

Mods[edit]

*** PLEASE READ!!!!!! ***

  • Read the instructions from the 'mod' documentation very carefully.
  • Remember mods are new to DayZ SA and they may not work well together so make sure you test them individually, add them one at a time and test
  • Its important to have Mods loaded in the right Order to work properly!
  • Not all so called MODS are mods, some are missions or map updates/addons/enhancements and are treated differently than typical mods
  • Not all 'MODS' require loading anything but the key file to the server, everything else is on the local PC
  • Some mods are client side and create configuration files that you then add to existing server side files.


Server Profile Folder[edit]

  • By default the server profile on all TRUgaming DayZ servers is set to:
    -profiles=<user server directory>\default
  • Please note that the profiles folder on the server does NOT have to be named "profiles"


The exact path can be see when you open the Commandline Manager.
Dzcommandlinea.png

Adding 'Mods' To Your Server[edit]

Step 1: Upload Mods

  1. Stop your server
  2. Using your favorite FTP client copy the mod folder from your PC to the server root folder
    Depending on the mod some mod folders will start with the @ character others will not
    More info on how to FTP files/folders to your server can be found here:411_on_Game_Server_Management#FTP_To_My_Game_Server
    When you have finished loading your mods for directory should look something like this;
    Dzfiles.png


Step 2: Changing Commandline

  1. Click on the Commandline Manager
    Cmdlinemgr.png
  2. This will open to your Predefinded Commandline tab.
    Dzcommandlinea.png
  3. Depending on the mod you are using, some mods require the -scrAllowFileWrite flag, click on the Select link on the right hand side
  4. This will open a dialog box
    Dzmodinput.png
    In the Mods input field enter the mods you want loaded. If you are adding multiple mods make sure you separate them with a semi-colon (;)
    @mod1;@mod2;@mod3
  5. Click Apply
    Your Commandline will now look like:
    Dzmods.png
    Note: The Select on the right hand side has now changed to Selected. This will be the commandline that the server will use when you start it


Step 3: Change any config files

  1. Depending on the mod you have installed, some mods require additional configuration of either mod files or other core server files like the init.c file
    PLEASE READ YOUR MOD DOCUMENTATION FOR ADDITIONAL CONFIGURATION REQUIREMENTS
    IF YOU DO NOT MAKE THESE ADDITIONAL REQUIRED CHANGES YOUR MOD MAY NOT WORK AS EXPECTED
  2. Start your server back up


Changing 'Mods' On Your Server[edit]

  1. Stop your server
  2. Using the same basic process as above, click on the Active/Selected commandline and add or remove the mods you want loaded.
    You do not have to delete the mod folder/files from your server.
    BUT, IF YOU MADE ANY CHANGES TO ANY CORE SERVER CONFIG FILES BECAUSE OF A MOD YOU ADDED, IT MAY BREAK YOUR SERVER
    SO REMEMBER WHAT YOU DID AND HOW YOU DID IT
  3. Start your server

24/7 Daytime Issues[edit]

We have been doing some research regarding the 24/7 daytime issue.. this has from everything we have found, certainly been identified as a bug.

We have found a possible solution, it deletes the Persistence Files under the mpmissions folder.

The source says (https://feedback.bistudio.com/T134056)
Start server with fresh storage files
Wait until restart
Observe time persistence enabled permanently

We have created a 24/7 Fix script, located on the Service Information tab. This will stop the server, delete the storage files and start the server back up. New storage files are created on startup.

The server will start in day time assuming you have set the serverDZ.cfg file to do so.
For example:

  • serverTime="2018/11/27/08/00";


  • NOTE: This will wipe any character progress

Admin Commands[edit]

You must log on as admin before typing admin commands.
Both logon and admin commands have to be sent in the chat prefixed with a #
(Note that some commands may be disabled depending on what type of server you have)


Command Example Description

Command Example Notes/Description
#login password #login adminPW Log in as the admin
#exec ban (name, ID or Player#)  #exec ban nickName Allows you to ban a player. Their ID will be added to the ban.txt
<May not be available in DayZSA> #exec ban 47114712
#exec ban 3
#kick (name, ID or Player#) #kick nickName Allows you to kick a player
#kick 47114712
#kick 3

How To Ban Players[edit]

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.

Wipe Server[edit]

A standard DayZ multiplayer mission using the offline database. Using this type of mission means that everyone's characters are locked to your server
- there is no option for shared characters over multiple servers when using the offline database.

The character information is stored within the players.db file, located within the mpmissions\dayz.chernarusplus\storage_X folder.
Removal of this causes character wipe.

RCON Password Change[edit]

The default Battleye Configuration file (BEServer_x64.cfg) is located in the \battleye folder on your server


Default Contents:
RConPassword <MyPasswordHere>
RestrictRCon 1


Once the server starts it renames this file for BEServer_x64_active_<some random numbers>.cfg, example BEServer_x64_active_6262.cfg
You can change the password but make sure you STOP the server first.

File Options: RConPassword MyPasswordHere - 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)

TOP

File Backup/Restore[edit]

  • We do not backup your server files, it is your responsibility to make backups and if necessary keep an offline copy
  • The backup process only keeps the last three backups that have been made
  • Backup files are located in the \UserBackups folder on your server


Configuration Files
This option backups/restores the server \default folder

  • By default the server profile on all TRUgaming DayZ servers is set in the command line to:
    -profiles=<user server directory>\default
  • Please note that the profiles folder on the server does NOT have to be named "profiles"
  • Compressed backup files start with the letter C, followed by the date time stamp of the backup
    Example C_02-05-2019 1257.zip

Mission Files
This option backups/restores the ENTIRE \mpmissions folder on your server

  • By default on all TRUgaming DayZ servers this is set to:
    \mpmissions\dayzOffline.chernarusplus
    and if you add any mods that may use their own structure and add files to the \mpmissions folder those will be included in the backup/restore process.
  • Compressed backup files start with the letter's MPM, followed by the date time stamp of the backup
    Example MPM_02-05-2019 1257.zip

Backup Files[edit]

Files can be backed up in one of two ways:

  • Manually, using the Configuration Backup option from the Actions menu
  • Scheduled, by creating a scheduled task under the Scheduled Tasks tab


Manually

  1. Go to the Actions tab
  2. Click on the Backup Configs or Backup mpmissions option
  3. Click OK to execute the script
    ExecuteScript.png
    This will open a command window (if you have a popup blocker turned on you will not see this and may have to allow popups for this site)

    Configbackup1.png
    If your server is running it will stop your server
    Execute the backup script. You will see information regarding the name of the file and number of files being backed up
    If you have more than 3 backup files I will inform you that it is deleting the oldest one
    Once complete, if you server was running it will restart your server.
    You be prompted to close the window... You may close this window :-)


Scheduled For more information on Scheduling a backup task see our Wiki page on the subject: Scheduling Tasks

Restore Files[edit]

Files can be only be restored Manually
** NOTE ** THIS WILL OVERWRITE ALL FILES IN THE DESTINATION FOLDER

  1. Go to the Actions tab
  2. Click on the Restore Configs or Restore mpmissions option
  3. You will be prompted with a dropdown list of available files
    RestoreList.png
  4. Select the file you want from the list and then click on the Execute button
    This will open a command window (if you have a popup blocker turned on you will not see this and may have to allow popups for this site)
    If your server is running it will stop your server

    Restorefiles.png
    Once complete, if you server was running it will restart your server.
    You be prompted to close the window... You may close this window :-)


Other Backup/Restore Notes:

  • If you want to restore individual file(s) from a backup, you will need to download the .zip file to your local PC
    Extract the .zip, locate the file you want and then upload it back to your server using the File Manager or an FTP client
  • If you have added custom files to any one of the above folders that are not part of the default file suite they will not be backed up and as a result not restored.
    Files with the following extensions are included in the backups: .c, .bin, .db, .map, .xml, .lst, .cfg

TOP