BattlEye
BattlEye runs deep system inspection through a kernel driver and tends to issue Global Bans that span every BattlEye-protected title at once. The vendor operates a direct support address and accepts evidence-led submissions, but reversals are uncommon and require the file to isolate a clear false-positive signal.
Restriction tiers
- Title-specific ban
Action limited to a single title before escalation.
- Global Ban
Vendor-issued restriction that applies across every BattlEye-protected game on the same device.
- Publisher overlay
Some publishers add a separate account-level restriction on top of the BattlEye Global Ban.
What it checks
- Kernel driver scan
- Global Ban model that propagates across every BattlEye title
- Behavioural pattern detection
- Manual review escalation path
Identifiers it can use
- SMBIOS board and chassis serials
- Disk and storage controller identifiers
- MAC addresses of physical network adapters
- Process tree and signed-driver inventory
Points an appeal can make
- Operator-direct submission via the vendor support address
- Isolate the specific binary the vendor identified
- Demonstrate the flagged process was inactive at session time
- Parallel publisher submission for the title-specific layer
How appeals are handled
- Vendor responses can take several weeks; multiple submissions slow the queue
- EU residents may pursue the publisher through DSA Art. 17 / 20 / 21 in parallel
Evidence to collect
- Global Ban notice with the GUID
- Process list and uninstall logs
- Anti-virus quarantine logs where applicable
- Hardware inventory and BIOS revision history
Games that use BattlEye
This page summarises public information. Anti-cheat vendors do not publish every detail of how their systems work, so read it as background, not as an explanation of how your own case was decided.
Get an appeal written for your case
Send us the ban notice and what happened. You see the price and the waiting time before you pay.
