How to run Battleye Extended Controls as a Windows Service with FireDaemon Pro.
Battleye Extended Controls can be run as a Windows service using FireDaemon Pro. This allows you to start and run the dedicated server automatically when Windows boots and before login. FireDaemon Pro also allows you to start multiple instances of the game server, monitoring them and automatically restarting those instances in the event they crash. FireDaemon Fusion can also be used to manage your Battleye Extended Controls service, plus other Windows services via your web browser.
Battleye Extended Controls Server Setup Under FireDaemon Pro
Please follow the steps below to set up an Battleye Extended Controls as a Windows service with FireDaemon Pro
Step 1: Download BEC
Open notepad or another text editor in administrator mode. Browse to the hosts file located at "C:\Windows\System32\drivers\etc"
Add the following to the bottom of the file and save it:
127.0.0.1 ibattle.org 127.0.0.1 www.ibattle.org
- Download BEC from here.
- Extract the contents of the ZIP file into "C:\". By default the folder name will be "BattlEye-Extended-Controls-master", rename it to something shorter like "BEC" so the path should now look like "C:\BEC".
- Edit "C:\BEC\Config\Config.cfg" and change BePath so that it matches the patch to BattleEye on your Arma 2/3 Server.
- Also make sure bans.txt exists in your BattleEye directory. If it doesnt, create it.
You can find detailed configuration help in "BecGuide.txt" located in "C:\BEC".
Step 2: Download and Install FireDaemon Pro
- Download FireDaemon Pro installer
- Double-click installer and follow the installation wizard to complete the installation.
- For more information about installing FireDaemon, see the FireDaemon Pro Users Guide.
Step 3: Set Up Battleye Extended Controls as a FireDaemon Pro Service
Double click the FireDaemon Pro icon on your desktop, then click on the New (i.e. +) button in the toolbar (or type Ctrl + N) to create a new service. Enter the information into the fields as you see below. Adjust the path names to suit your installation. Note the required parameters.
The most important field on the tab is the Parameters. The Parameters define the initial setup of your server. The full parameter list should be as follows:
-f config.cfg --dsc
- -f config.cfg Loads the configuration file C:\BEC\Config\config.cfg. If you change the filename in the config directory, you will need to change it here too.
- --dsc Disables version checking which slows down the startup of BEC. It also allows you to run the FireDaemon service without the use of an account that has Administrator privileges.
Next, click on the FireDaemon Pro Settings tab:
Enter appropriate values in the fields on the Settings tab as follows:
- (Required) Job Type: You must set the job type to "Global Job".
- (Required) Logon Account: Enter the Windows account under which the application is to be run, e.g. the current user account.
- Password / Confirm Password: Enter the logon account's password twice.
- (Optional) Interact with Desktop: Interact with Desktop: If this setting is enabled (default), the applications' output messages can be seen in the console window on Windows Session 0. To switch to Session 0, it may be necessary to install FireDaemon Zero and ZeroInput. Alternatively, this setting may be disabled, in which case the application's messages will be hidden.
- (Optional) Priority: To allocate more CPU time to the application, select a higher scheduling priority in this field.
- (Optional) CPU Bindings: To run the application on a specific CPU, specify the appropriate CPU in this field.
Next, click on the Lifecycle tab. Set Shutdown By to Forceful Termination and check "Console Program".
Lastly, click the Save and Close (ie. the tick) button on the toolbar. If the service's Startup Type is set to Automatic or Automatic (Delayed-Start), it will start immediately.
Step 4: Verify that Battleye Extended Controls is Running Correctly
The Battleye Extended Controls tool server's status can easily be checked on the main FireDaemon Pro Services List - look for a Running Status value and a numeric Process ID (PID) value.
If the service's Interact with Desktop setting is enabled, the tool status can also be verified by switching to Windows Session 0 to view the game's messages.