BattlEye Filters Setup for Arma 3 Servers
This guide walks you through setting up BattlEye filters on an Arma 3 dedicated server. Filters let you control which scripts and modifications clients can run, blocking cheats and unwanted mods. You’ll learn what files to create, how to configure them, and how to test that they work.
What You’ll Need
- Access to your Arma 3 server’s file system (via FTP or a control panel).
- A text editor like Notepad++ or VS Code (plain Notepad works too).
- Basic understanding of Arma 3 server folders.
- BattlEye must be enabled in your server configuration.
Step-by-Step
- Locate the BattlEye folder. In your Arma 3 server directory, find the
BattlEyefolder. If it doesn’t exist, create it. This folder is usually at the same level as the server executable. - Identify the filter files. BattlEye uses filter files named
scripts.txt,remoteexec.txt,remoteexec2.txt, andpublicvariable.txt. These are the core filters. If they don’t exist, create them as empty text files. - Understand the format. Each line in a filter file starts with a number (0-5) followed by a semicolon and then the pattern. The number is the action:
0= allow,1= log only,2= kick,3= kick and log,4= ban,5= ban and log. For example,1""would log everything. - Start with a permissive base. For a new server, begin with
1""as the first line in each filter file. This logs all activity without blocking anything. This lets you see what scripts are being used before you tighten rules. - Add specific rules. After seeing logs, add lines to allow or block specific patterns. For example, to allow a known mod script, add
0"myModScript". To block a known cheat, add2"hackName". Use the log entries to identify patterns. - Use wildcards. BattlEye supports
*(any number of characters) and?(single character) in patterns. For example,1"*"matches everything, and2"hack*"blocks anything starting with “hack”. - Test with a client. Join your server with a normal Arma 3 client. Check the server console for BattlEye log entries. If you see “Script restriction” messages, your filters are working.
- Iterate and refine. As players join, review the logs regularly. Adjust the filter numbers and patterns to allow legitimate mods while blocking suspicious activity. Remember to restart the server after changing filter files.
- Backup your filters. Keep a copy of your filter files outside the server. If you update the server or BattlEye, you may need to reapply them.
Common Mistakes
- Using 0 for everything. Allowing all scripts defeats the purpose. Use 1 (log) for unknown patterns first.
- Forgetting the semicolon. The format is
number;pattern. Missing the semicolon makes the line invalid. - Blocking too broadly. Using
2"*"will kick everyone, including yourself. Be specific with patterns. - Not restarting the server. Filter changes only take effect after a server restart.
- Editing while server is running. Some hosts lock the files. Stop the server before editing.
Tips
- Use the official BattlEye filter guide. The BattlEye website has a detailed filter syntax reference.
- Start with a community filter set. Many server hosting communities share their filter files. Use them as a starting point and customize.
- Log to a separate file. Configure BattlEye to log to a separate file for easier analysis.
- Test with a second PC or VM. Use a separate client to test filters without risking your main account.
- Keep filters updated. New cheats and mods appear regularly. Review logs weekly.
Troubleshooting
- Players kicked instantly. Check the server log for the specific filter line that triggered. It’s usually the last line before the kick. Adjust or remove that line.
- Filters not working at all. Ensure BattlEye is enabled in
server.cfgwithBattlEye = 1;. Also check that the filter files are in the correct folder and named exactly as expected. - Server won’t start. A syntax error in a filter file can prevent startup. Check for missing semicolons or invalid numbers.
- Logs are empty. Make sure you have a
1""line at the top to log everything. Also check the server’sBattlEyefolder for log files. - Legitimate mods blocked. Add an allow rule (
0) for the specific script or use a broader pattern that matches the mod’s scripts. Test after each change.
Frequently Asked Questions
What does the number before the semicolon mean?
It’s the action: 0 = allow, 1 = log, 2 = kick, 3 = kick and log, 4 = ban, 5 = ban and log. Use 1 for monitoring, 2 for blocking.
Can I use regular expressions in filters?
No, BattlEye uses its own wildcard syntax with * and ?. Regular expressions are not supported.
Do filters affect the server performance?
Negligibly. They only check script calls. The impact is minimal compared to the security benefit.
How often should I update filters?
At least monthly, or whenever you see new cheat reports. Review logs after each server update.
Can I have separate filters for different missions?
No, filters are global per server. You can’t have per-mission filters.
What if I accidentally ban myself?
Remove the ban line from the filter file, restart the server, and join again. Bans are not permanent unless you use the ban action.
Related
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.