(new install) i was with you till part 16.... i have no cfg file or config folder in the bec directory ...those files are not included in the server files download so i guess i am missing them some how. any advice on where to get all the bec directory files?
never mind i found them
http://ibattle.org/downloads/
Latest Bec Version 1.605
Md5 : 9cad0c28ec7d4fdeef251f3014cdaf6e
Sha1 : f1f03691090793c7a746946c8ace4a562f9ff56e
Below is the procedure I have used to set up A3 Epoch servers on my desktop PC. These servers are useful as a test bed when I try out things like the many scripts being released for Epoch.
Updated for Epoch RC 0.3.0.3
This How To is based upon the Install.txt provided with the Epoch server files. If your server does not start up you may have missed a step or be lacking essential software.
For additional information, please refer to the Epoch developer's Wiki which provides considerable additional information.
http://epochmod.gamepedia.com/A3Epoch:Arma_3_Epoch#Server_Setup_.26_Information
For an excellent guide on troubleshooting, refer to the FAQ at
For another take on this How To, which provides a more comprehensive discussion of the different things you need to consider for server setup.
What you will need:
A good text editor like Notepad ++ (freeware)
Visual C++ Redistributable Packages for Visual Studio 2013: http://www.microsoft.com/en-us/download/details.aspx?id=40784
30 min
a bit of patience.
Stage I: create a server directory and add all needed files to your server directory.
1) Create a new directory on the disk you wish to use for your server. Mine is on an SSD drive E:
Lets call it: E:\Arma3Server for this tutorial.
2) Open your ..Steam\SteamApps\Common\Arma3 directory. Mine happens to be in E:\Steam\SteamApps\Common\Arma3.
3) Copy everything from that directory to your new server directory E:\Arma3Server.
4) Download Epoch Mod from here http://epochmod.com/download.php. Unpack the .rar file.
5) Copy @Epoch to your new server directory E:\Arma3Server.
6) Download the Epoch Server files https://github.com/EpochModTeam/Epoch/tree/master/Server_Install_Pack.
7) Extract the archive, and copy all files and folders in it to your E:\Arma3Server directory.
Stage II: Adjust the settings for your database:
8) Open the DB folder of your E:\Arma3Server directory.
9) Open redis.conf using Notepad ++ or another text editor. It will look like this.
10) Change Changeme9832 in the "requirepass" field to a password you wish to use for your database server such as client321.
11) In your E:\Arma3Server folder, find and open @EpochHive.
12) Open EpochServer.ini using Notepad++. In it there will be a section titled [Redis] which looks like this:
13) now change the password to the one you set above for redis.conf, which for this example was client321.
Stage III: Complete configuration of Epoch Server Settings.
14) Next, in EpochHive.ini you need to specify the path to be used when starting the battleye on the serverside. Look for the following section:
Change the BattlEyePath to the one appropriate for your server. In our example, this would be E:\Arma3Server\SC\BattlEye
Now save and close EpochHive.
Stage IV: Configuring Automatic Restarts and other related issues.
In the past automatic restarts have usually been accomplished using BEC, a freeware tool. For reasons outside the scope of this how-to, development and support of BEC was discontinued and Epoch has been moving to integrated Battleye in various ways including providing functions for automatic restarts. If you wish to use BEC, you can download it using the link below:
http://www.armaholic.com/page.php?id=15716
In order to run BEC, you will need to redirect its efforts to phone home. Instructions on how to do so are listed in the post by Dwarfer in this thread.
You will also need to set the correct path to your Arma3Server\SC\Battleye folder in the configuration file for BEC which normally would be: Arma3Server\BEC\Config\Config.cfg.
BEC does still provide valuable functionality such as the ability to play certain messages periodically, but you can also schedule server restarts or utilize other features if you wish. .
Alternatives to BEC for automated server restarts:
Please see the release notes for Epoch 0.3.0.3 for details on the built in automated server restart functions. The new method for automated server restarts is recommended if you are setting up a new server.
To use the built in server restart functions, open @epochhive\epochconfigs.hpp
In the first line, change
serverRestart = false; // true sends #shutdown command to server after the time specified in ForceRestartTime
to
serverRestart = true; // true sends #shutdown command to server after the time specified in ForceRestartTime
17) Stage V: Create your server startup file.
18) Open a blank document and past the following into it then save it in your E:\Arma3Server directory as something like A3Epoch.bat. Note that if you are using Notepad++, its default is to save files as text files. Select *.* from the drop down menu for choosing the file type before saving you A3Epoch.bat: Again, the you will need to adjust the paths in this file to suit those for your server.
20) Stage VI: Configure BattlEye
21) Open the SC\Battleye folder and rename example-BEServer.cfg to BEServer.cfg and change the RConPassword.
22) Create an empty text file and save it as bans.txt in the SC\Battleye folder. Save and close the above configuration files.
23) Stage VII: Starting and joining your server.
24) In your E:\Arma3Server folder find and open the DB folder then click start-redis.
24) If you will be using BEC, go to your E:\Arma3Server\BEC folder find BEC, and start it.
25) Start Arma 3, select Play, then multiplayer and finally in multiplayer select remote. Enter the IP and port for your server, which in our example is 127.0.0.1:2302.
26) Also in your E:\Arma3Server directory should be the A3Epoch file you created above under step 18. Find it and click it.
When you do, the Arma3server console should open after slight delay, and you should see information including the port number you used above in your A3Epoch startup file. If you are using BEC, once the Arma3server is running, BEC should go through a few steps then indicate it has successfully connected to the server.
