Skip to main content
A BattlEye “Script Restriction” kick on Arma 3 means a filter file such as scripts.txt matched code a player’s game ran. To fix it, find the logged code in the matching log file (for example scripts.log), add an exception to that filter line with !="exact code" or !"part of the code", save the file and restart. Filter files usually come with a mission framework or mod.

What are BattlEye filters?

BattlEye filters are text files that check what players’ games do. scripts.txt scans every script that runs on a client for keywords. Other files check commands on the server, for example createVehicle.txt for spawned vehicles. Frameworks such as Altis Life ship their own filters for their mission. Each line starts with an action number:

Where are the filter files?

Filter files and their logs live in the server’s BattlEye folder. On our servers, open Files and check the battleye folder in the server root. If your mission came with filter files, upload them there.

How to fix a Script Restriction kick

1

Note the kick

Note the filter name in the kick message, for example a script restriction or a remoteExec restriction, and the player’s time of kick.
2

Open the log

In the BattlEye folder, open the log that matches the filter, for example scripts.log for scripts.txt. Find the entry for that player and copy the code it shows.
3

Find the filter line

Open the filter file and find the line with the keyword that matched.
4

Add an exception

At the end of that line, add a space and then !="exact code" for an exact match or !"part of code" for a partial match. Put the text in quotes. Inside the quotes, write a quote mark as \".
5

Save and restart

Click Save Content and restart the server. Test the same action in game again.
Example: allowing one createDialog call that a filter blocks.
Keep exceptions as exact as you can. A short partial exception can let cheat scripts through too.

How to test filters without kicking players

Change the number at the start of a line from 5 or 7 to 1 or 3. The filter then only logs. Play normally, read the log, add exceptions, and switch back to kick when the log stays clean.

Frequently asked questions

Can I just delete the filter files?

You can, but then BattlEye no longer blocks anything on those checks, which makes cheating easier. Use exceptions or log-only mode instead.

Why do kicks start after a mod update?

New mod versions run new code that old exceptions don’t cover. Repeat the steps with the new log entries.

Is this the same as a signature kick?

No. Signature kicks are about mod files and keys. See signature errors.

Arma 3 server guide

Every Arma 3 page in one place.

Signature errors

Mod keys and verifySignatures.

Altis Life server

A framework with its own filters.

BattlEye RCon

Remote admin through BattlEye.

File Manager

Edit and upload files.

Checked against the AsYetUntitled BattlEye filters guide on 31 October 2026; panel steps tested on our Game Panel (Arma 3 dedicated server 2.22, BattlEye Server 1.221). Filter behaviour may change with BattlEye updates.

Need Extra Help?

If you encounter any issues, our support team is ready to assist:

Save on Your Hosting

Ready to upgrade your hosting? Use code KB20 at checkout for 20% off your first order!

Last Updated: October 2026