pws://six.unitedoperations.net/arma3/a3srv1.yml SRV1 - Primary
pws://six.unitedoperations.net/arma3/a3srv2.yml SRV2 - Alternate
pws://six.unitedoperations.net/arma3/a3srv3.yml SRV3 - Test 1
pws://six.unitedoperations.net/arma3/a3srv4.yml SRV4 - Test 2
pws://six.unitedoperations.net/arma3/a3srv5.yml SRV5 - Training 1
pws://six.unitedoperations.net/arma3/a3srv6.yml SRV6 - Training 2
At present I will be running a minimal number of the servers until there is a better established load/remand.
Expect for me to keep SRV1 + Test 3/4 On for the next few weeks. At which time we will redetermine how to proceed based on demand.
We are not currently running the development builds of A3, we will change to this should the need arise. I will most likely change SRV2/SRV4 into Dev versions if there is a desire to help test over and above the base play requirements.
Standard Mission Submission Rules are now in effect.
Things to keep in mind with SixUpdater
You will need to define your ArmA3 Paths, and you will need to FORCE your preset to ArmA3.
There are a number of other concerns with using SixUpdater.
Play withSix(220.127.116.110 Required)
Play withSix has better support for ArmA3 and ArmA2 at present, as it is the next product that we will be switching over into.
Again, please do not use the dev build in steam, it will not be in sync with the server.
Spoiler redacted, please do not use beta updates.
You will need to define your Game Paths as appropriate to your local install.
At present it will work with both ArmA2 servers and ArmA3. It should present the least amount of difficulty in using, but I am anxious to hear your feedback in comparison to earlier versions and or in comparison with SixUpdater.
Edited by Impulse 9, 2014-07-26 @ 09:30.