CFTools OmegaManager =================================================== Introduction ------------ OmegaManager is a software to automate your DayZ server experience. Setup ------------ - Create a directory called OmegaManager - Switch to the OmegaManager directory - Create a file called manager.cfg The up-to-date default manager.cfg can be found here: https://cftools.de/_files/om/manager.cfg - Download the OmegaManager.exe using the this url: https://cftools.de/_files/om/OmegaManager.exe - Add your Steam login credentials to the respective manager.cfg configuration variables and apply any other wanted configuration changes - Start the OmegaManager - Wait for initial start to complete - Restart your server machine manager.cfg ------------ - If you are using the mobile authenticator, set mobile_authenticator to true Steam-API key ----------- The Steam API key can be retrieved here: https://steamcommunity.com/dev/apikey Enter your domain or server ip as domain Post-setup ------------ After setting up the manager and starting it for the first time it will go through its installation process. In this phase it will create its internal directories and download SteamCMD. Additionally it will attempt to install VCRedist and DirectX which are required to run the DayZ server. This can be cancelled if you dont want to install them or already have done so. Using the manager ------------ When the manager has finished its startup routine it will show a Windows notification notifying about the manager being ready. Afterwards you can access the manager internal webinterface at http://localhost:8081 or http://127.0.0.1:8081 General information ------------ - Steam account requires owned copy of DayZ to download and manage mods - Using the Steam Mobile Authenticator breaks the automatic relogin and therefore is not recommended - You cant copy and paste or import your existing server. You have to deploy and configure a new instance. - The manager has an integrated mod server, running the DZSALModServer.exe is not required OmegaManager API ------------ Documentation: https://cftools.de/_files/om/api.txt =================================================== Adding existing servers ------------ The OmegaManager requires a specific directory layout along with its own configuration file. Therefore adding existing servers is not possible. To "add" those servers, a new instance needs to be created. Afterwards all existing configuration files and the database can be copied over. Adding mods ------------ # All mods should be added over the OmegaManager webinterface / Steam account needs to own DayZ in order to download workshop items # To add mods to a specific server, navigate to the instance Overview and select the mods tab. Lookup the mod(s) you want to add and press the blue plus. (The load order can be adjust anytime by dragging and dropping the mods in the upper section.) After the page has been saved, the manager enters one of two states: 1. Mods already tracked but not applied Restart your game server and the mods will get installed 2. Mods not yet tracked Mods are usually downloaded during the "upstream check" which is scheduled to run every 10 minutes. To force the manager to download the mods immediatly, you can either force an upstream check or navigate to the dashboard and click on "Installed untracked mods now" After the upstream check or the mod downloading completed you can restart the game server to install them. Mods will not immediatly show up as installed in the mod section of the overview of the instance however. It might take up to 20 minutes to properly appear in that list Adding non workshop items ------------ OmegaManager does currently not offer a out-of-the-box solution for adding non workshop items. To do this the mod needs to be added manually to the omega.cfg. 1. Create new directory called @%yourmodname% in the server root 2. Open omega.cfg 3. Copy existing mod configuration and adjust directory and set file_id to 0 4. Save and close omega.cfg 5. Restart game server (Workaround) Hiding server mods for the DZSALauncher ------------ In versions till 1.8.0010 server side mods are being reported to the DZSALauncher. To hide them, a new launch parameter must be added to the server in the Omega instance configuration: -ignoremod=@MyMod1;@MyMod2; =================================================== Deprecation of OmegaManager-legacy-old ------------ OmegaManager-legacy-old (all versions prior to 1.8.0000) will be finally deprecated on 01.01.2020 with cloud endpoints being closed without prior notice. A switch to OmegaManager-legacy-compat (all versions after 1.8.0000) is strongly recommended