thomas.collett@gmail.com

After updating BattlEye approximately a few weeks back, scripts.log is no longer being written to in the BattlEye directory. BattlEye is enabled in the server's configuration, works correctly (as I can connect to it via BERcon and it is validating/kicking users as appropriate) and the server is officially approved and connected to the Hive. arma2oaserver.rpt and other log files are being written to as expected, and are archived on each restart. If anyone could shed any light on this it would be much appreciated.

You're welcome. Ensure you edit scripts.txt as per the following threads as the scripts.txt I linked you to is written without the new supported syntax: http://forums.bistudio.com/showthread.php?131759-New-BattlEye-features-for-server-admins&p=2193771&viewfull=1#post2193771 http://www.tunngle.n...er-admins-read/ I have discovered that not following instructions in the above threads will cause players to be kicked with Script Restriction #40. Simply adding the //new keyword to the top of that file is not enough.

You can download scripts.txt from: http://armafiles.info/dayzbans/scripts.txt Try uploading it to your server - don't forget to add //new to the top of the file prior to uploading it to your server.

The answer is in the previous post in this thread thanks to DeadWalking99. Just to clarify: Stop your Arma 2 server. If you are on a hosted server with a web control panel, open the scripts.txt from the online system and skip to step 5. Go to your Arma 2: OA root directory. From there navigate to: cfgdayz-> BattlEye-> scripts.txt Add a new line to the top of the file which says "//new" (without quotes). Start your server and the log file will start to generate in the cfgdayz/BattlEye directory. If you are unable to access this file via a control panel, FTP or otherwise, submit a request to your host with reference to the above. Edit: Adding this keyword means you need to use the updated syntax. Not doing so may cause players to be inadvertently kicked for "Script Restriction #xx". See details here http://forums.bistudio.com/showthread.php?131759-New-BattlEye-features-for-server-admins&p=2193771&viewfull=1#post2193771

Do you mean that should be added on a new line to the top of scripts.txt in the BattlEye directory? Edit: Adding this to the top of scripts.txt works. You are a genius. Thank you so much!

The Arma 2: OA instance is running on my own co-located hardware so I'm going to have to figure out specifically what is causing the issue. If there is any chance you get to speak to your host and can find out what they did, I would be hugely grateful and the community would benefit as a whole. From trawling the web, I've found the odd post here and there citing similar problems but with no resolution. I'll try re-downloading the BattlEye server dll and see whether that changes things.

You are incorrect. Scripts are executed for players across all kinds of events in order to sync events taking place on the client with other players on the server. The file on my server would typically be about 10 megabytes in size at the end of a 4 hour session.

Only the server administrator would know whether they are restarting due to performance issues, a misconfiguration, testing new settings or to keep player count low to gain an unfair advantage. All we can do is speculate.