Skip to main content

​
Managing Security: Script Restrictions

BattlEye is an aggressive anti-cheat solution. By default, it blocks almost any robust script Execution. “Script Restriction #0” kicks are common when running heavily modded scenarios like Antistasi or Exile, as legitimate mission scripts trigger the generic security filters.
Reading TimeDifficultyLast Updated
6 minutesAdvancedJanuary 2026

​
Analyzing the Kick

When a player is kicked for a “Script Restriction,” BattlEye generates a log entry on the server.
  1. Locate Log: Navigate to /battleye/scripts.log.
  2. Read Entry: Look for the last line.
    • Example: #0 "player setVelocity [0,0,10];"
  3. Interpret: This means line 0 (or 7 depending on the file) blocked the specific command setVelocity.

​
Adding Exceptions

To allow this script without disabling the filter entirely:
  1. Open Filter: Edit /battleye/scripts.txt.
  2. Find Line: Locate the line ID (e.g., line 7 starts with 7 setVelocity).
  3. Append Exception: Add a != followed by the exact code snippet you want to allow.
    • Change: 7 setVelocity
    • To: 7 setVelocity !=player setVelocity [0,0,10]

​
Support Channels

If you need assistance or have any questions, please contact our support team:

​
First Month Discount

Use code KB20 at checkout to get 20% off your first month of hosting!
Last Updated: January 2026 | Arma 3: Filters refined.