Update an Existing ArmA 3 Epoch Server

From Nitradopedia EN
Jump to: navigation, search
Arma3 wiki.jpg

Rent your own Prepaid ArmA 3 server! nitrado.net

This article provides a general outline for updating the Epoch Mod for ArmA 3. Please note that ArmA 3 itself is self-updating with our automated system, but the Epoch Mod is not. This is due to the fact that Steam defines a fixed update process which makes errors almost impossible, but Epoch does not have this sort of integration for the update process.



Note: It is highly recommended that you stop the server before performing any of the following, or files may be lost.


1. Backup the Redis Database

The database system, Redis, used by Epoch contains the progress of players, positions of AI on the map, logs, and much more. To ensure none of this is lost in the update, it should be backed up as the first step.

To do this, an FTP connection to your server is required. Navigate to the "arma/DB" directory. The database is in the form of dump.rdb, and should be downloaded. Place this somewhere you will remember.


Redisdb.png


Now you have backed up your database (we can upload it later if we need to). It should be noted that the update you apply could break the database, and you would need to start your progress over, even if you have it backed up.





2. Backup the Server Data

After you have saved your database, you should now backup your installed add-ons, scripts, and other file-based changes.
The easiest way would be to just rename the main installation folder. This can be done via FTP, but can also be done through the File browser on the web interface (under Tools).

This ensures that the folder, which contains the old ArmA 3 Epoch installation, is preserved through a new installation. Be aware that this will not be included in the daily backups our system makes.





3. Updating the Server Files

Now that all of your data is backed up, a new installation can be initiated. This can be done on the web interface of your game server under "Switch Game", and choose "Reinstall". This will install ArmA 3 again, and include the most recent version of Epoch.

In most circumstances, an update is only a couple files. The latest server files can be found on the official website here. The important files that should definitely stay on the server are:


Aereinstall.png

  • arma3/@EpochHive/addons/ a3_epoch_server.pbo
  • arma3/@EpochHive/addons/ a3_epoch_server_settings.pbo
  • arma3/@EpochHive/ EpochServer.dll

It is also worth taking a look at the "Announcements" section of the Official ArmA 3 Epoch forum. Here you will find the changelog.



Now that all of the data has been updated, all previous data, addons, missions, and scripts can be reuploaded to the server.


4. Importing the Database

Now that the server is updated, we can import the old database. To do this, make sure the server is stopped, then access your server via FTP, and open the "arma/DB" directory. Delete the "dump.rdb" file that is here, and then upload the database we saved back in step one to the server.

The server should then start with all previous progress retained.


5. Refreshing the Local Game

In the event that the client also received an update, you will need to update your game locally as well. If you are using a program like A3Launcher or Arma3Sync, the update should be applied through these. Otherwise, you will need to update manually.

This is done in several steps:

  • First, the old Epoch mod must be removed. This is done by deleting the "@Epoch" folder in your ArmA 3 directory (locally).
  • Next, you must acquire the newest version of Epoch, here.
  • You will need to unpack the archive, and place the "@Epoch" folder back into your ArmA 3 directory.

Now your mod is up-to-date on the client side.


6. Update Finished

If steps 1-5 were done correctly, the server will now be up-to-date, and a connection can be made.