ClontarfX

The "DB" save interval is defined in the REDIS Server configuration file.
 
We're finding on our server that even with forcing REDIS to flush to disk every 10 seconds, we're still getting rollbacks (and in some cases, full rollbacks).
 
Skaronator will need to check his REDIS configuration.
 
Server owners really should of had the choice to use MySQL...

What Smokey is getting at is that it seems like a very poor decision to include content in the FREE mod, that requires you to PURCHASE ARMA 3 DLC. And I agree.
 
It's unfair to those without the financial means who might want to fly the aircraft in the mod. I understand that there are non-DLC helicopters, but because we can't modify the mission file, we can't remove the non-DLC, which results in a shock for some when they come across an unusable vehicle.
 
In any case, all I really want is a warning somewhere that advises players that they will require to purchase DLC in order to use all content in the mod.
 
As Smokey said, we spend hundreds of dollars a year running a server for the community for FREE, and it's a kick in the teeth for server hosters to find out that their players need to pay to play with what we believed was a free to play mod...

It is encrypted. You are not permitted to modify the Epoch server files at this time.
 
There is nothing stopping you from writing your own SQF code however, and running that via init.sqf. You don't need to modify mission.sqm at all.

There seems to be some people struggling with the concept of setting up Arma 3 within FireDaemon.
 
This XML is for people who install thier servers in a SANE location - I wont offer any assitance to anyone who insists on installing thier server in a "program files" location. :P
This also is for people who use the default file structure that comes with the Epoch Server files.
 
 
I will make things easy for you by giving you a copy of a working Arma3.xml for FD.
 
Things you will have to do in FireDeamon after importing it:
PROGRAM TAB - Change Working Directory to the location of your Arma3 Server's folder. PROGRAM TAB - Executable - check it exists at that location. Use [...] to point it to the executable (Arma3Server.exe) if it differs from default. PROGRAM TAB - Modify the Parameters specific to your server -  IP / PORT PRE / POST SERVICE TAB -  Modify the location of the Working Directory for the included Tools\log-rotator.cmd. This along with the imported XML should get you up and running.
NB - All the timings set in this XML work for me, you may need to tweak them a little depending on your Server's setup.
 
Arma3.xml for FireDaemon (copy/paste into Arma3.xml)
http://pastebin.com/rEBveMUb
 
 
Recommended(slightly more advanced):
 
Epoch requires BEC running, so this is worth a read!
 
Set up BEC via FireDaemon. Set up a dependency in the BEC Service requiring the A3 Epoch Server Service is running prior to starting. If you shutdown / restart your server BEC will go down/up with it. Recommend setting a delay to ensure the server is UP before the BEC Service starts. Alternatively:
Create a batch file to execute BEC, set this up in the POST SERVICE tab within the Arma 3 Epoch Service This will initialise BEC after the server has started I recommend setting a delay on this to ensure the Arma 3 Server is UP before BEC starts.  
NBB -  DO NOT do both of these methods or you may have multiple BEC's running and/or looping on a restart.
 
 
There are a bunch more options in FD of which there are guides on their website.
 
Also ProTip, FireDaemon have pre-made XML's for common applications on thier website :P

On behalf of Black Market Gaming and every other non-GSP provider, Thankyou and Congratulations on releasing Epoch Mod to the public  :wub:  :wub:  :wub:
 
We look forward to hosting a server for the Australian community for many moons to come :)

Since we are making great strides on the backend development thanks to our newest team member Fank. I feel that we should be ready for a public release of our server files on approximately December 1st. I know there was a thread for those "Trusted Communities" but the demand has been so great that we feel the need to make it public for everyone. Leading up to Dec. 1st, our code developers will all be hard at work adding features and fixing as many bugs as we can. Also, our content developers will be adding more content as it becomes ready.
 
The version number will likely be 0.2.5 or 0.3 by this time and not the 0.5 as I stated before. Please keep in mind that we are still very much in Alpha and will be for some time. Running a server is not going to be easy or without problems, errors, and plenty of headaches. 
 
After the files are released GSP's may start selling servers and private server hosts can host on there own hardware. I will be getting in touch with each of our current GSP supporters before release to make sure they have had a chance to test and report any bugs so they can be prepared to host when we do release the files.
 
Everyone that runs a server must acknowledge that you are not to break BI terms of use http://www.bistudio.com/community/game-content-usage-rulesand that you accept our license:  http://creativecommons.org/licenses/by-nc-nd/4.0/ Failing to comply with the above terms will result in a Cease and Desist notice and or legal action if necessary.