BattlEye Kicks on Linux: Fix Every "Client Not Responding" Error

If you have joined a BattlEye-protected server on Linux through Steam Proton and been kicked with a message like "BattlEye: Client not responding" or "You were kicked off the game," you are not alone and you are not banned. What you are seeing is a configuration gap -- one that is entirely fixable once you understand the architecture.

BattlEye officially announced support for Linux via Proton in September 2021, with Valve publishing the integration details in December of that year. BattlEye's announcement on September 24, 2021 confirmed the opt-in model:

"This will be done on an opt-in basis with game developers choosing whether they want to allow it or not."

-- BattlEye (@TheBattlEye), September 24, 2021

Valve followed up in December 2021 with specifics on how straightforward the integration had become:

"All a developer needs to do is reach out [to] BattlEye to enable it for their title."

-- Valve Steamworks Development, December 3, 2021

The catch is that the support does not work automatically for every game. There is a separate runtime component that must be installed, kernel parameters that some games require, and launch option environment variables that some games need explicitly set. None of this is documented in one place in Steam's UI, which is why players keep running into kicks months or years after the support was announced.

How BattlEye Works Under Proton

To understand why kicks happen, you need to understand the architecture. On Windows, BattlEye runs as a kernel-level service that monitors the game process and reports back to the server at regular intervals. If the server does not receive a response within a timeout window, it issues a "client not responding" kick.

Under Proton, BattlEye cannot use kernel drivers the way it does on Windows. Instead, it relies on a compatibility layer called the Proton BattlEye Runtime -- a set of Linux-native libraries and service components that replicate the heartbeat behavior expected by BattlEye-protected servers. This runtime runs outside the Wine/Proton environment and communicates with the server using the same protocol BattlEye uses on Windows.

The critical detail is this: the game binary running inside Proton, and the BattlEye service talking to the server, are two separate processes. The game can launch successfully and appear to run fine while BattlEye is completely non-functional. You will not see an error until you join a server and the timeout expires -- which is why so many players assume the game is working, join a server, and then get kicked 30 to 120 seconds later with no explanation.

There are also games where the developer has not opted into BattlEye's Proton support. BattlEye's model requires each game developer to contact BattlEye and request that Proton support be enabled for their title. Valve handles the technical integration, but the opt-in is per-game. As GamingOnLinux reported when covering the integration rollout:

"Devs only need to reach out to BattlEye to have Proton support turned on."

-- GamingOnLinux, November 2021

Games that have not been opted in will always kick Proton users, and there is no client-side fix for this -- it is a server-side configuration decision by the developer. Notable examples of games that use BattlEye but have not enabled Proton support include Destiny 2 (Bungie has not responded to multiple community requests and explicitly states Proton is unsupported), GTA Online (Rockstar added BattlEye in September 2024 without enabling the Linux compatibility toggle, cutting off a previously functional player base), and Escape from Tarkov (launched on Steam in late 2025 without BattlEye Proton support enabled, despite community petitions to BSG). For these titles, no amount of client configuration will resolve the kicks.

Step 1: Install the Proton BattlEye Runtime

The single most common cause of BattlEye kicks on Linux is a missing Proton BattlEye Runtime installation. This is a separate Steam tool (App ID 1161040) and it does not install automatically when you install a BattlEye-protected game. The reason it is separate is architectural: the runtime operates outside the Wine/Proton sandbox as a native Linux process, so it cannot be bundled inside the game's Windows file structure. Steam treats it as a shared tool that any BattlEye game can reference, similar to how Proton itself is a shared compatibility tool rather than a per-game component. The Bohemia Interactive Community wiki for Arma 3 confirms this requirement explicitly: to enable BattlEye compatibility on Proton, you must download and install the Proton BattlEye Runtime from the Tools section in your Steam library. Without it, the game will connect to servers but BattlEye will fail to initialize.

1. Open Steam.
2. In your library, click the dropdown or search filter and select Tools.
3. Search for "Proton BattlEye Runtime" in the search field.
4. Click Install on the result. It will download a small package (under 100 MB).
5. Wait for the installation to complete before launching your game.

If you cannot find it by name, you can also search Steam directly using the App ID. In the Steam browser or search bar, look up app 1161040. Once installed, the tool will appear in your Tools section as "Proton BattlEye Runtime."

Step 2: Raise vm.max_map_count

Many BattlEye-protected games that run through Proton -- DayZ and Arma 3 being the two that have the most documented Linux issues -- require a higher kernel memory map limit than the Linux default. The default value of vm.max_map_count is 65530 on most kernels (you may see it listed as 65536 in some guides -- the slight discrepancy is because the actual default is 65530 on standard kernel builds, not a round power of two). DayZ and similar games need a value of at least 1048576 (1024 * 1024) to load their assets reliably.

When this value is too low, the game will either freeze at the main menu, crash partway through loading a server, or connect and then be disconnected as the BattlEye service fails to initialize correctly within the Wine process boundary. Some custom kernels -- such as TK-Glitch -- raise this value from the default, but even common intermediate values like 524288 are not sufficient for DayZ. The safest approach is to set it to 1048576 permanently.

Temporary fix (applies until next reboot)

$ sudo sysctl -w vm.max_map_count=1048576

Permanent fix (persists across reboots)

# Write the config file
$ echo 'vm.max_map_count=1048576' | sudo tee /etc/sysctl.d/99-vm-max-map-count.conf

# Apply immediately without rebooting
$ sudo sysctl --system

# Verify the value took effect
$ sysctl vm.max_map_count
# Expected output: vm.max_map_count = 1048576

This change is safe to make permanently. The parameter controls the maximum number of distinct memory-mapped regions a single process can have. The only reason the default is as low as it is comes from the kernel's conservative assumptions about server workloads, not from any practical risk on a gaming machine.

You may also see guides that recommend values of 262144 or 524288 instead of 1048576. These lower values work for some games but not for DayZ specifically. The DayZ Linux launcher documentation is explicit that even 524288 is not reliable for DayZ under Wine, and the Linux gaming community settled on 1048576 as the value that avoids freeze and crash issues. If you are playing a different game and a lower value works for it, that is fine -- 1048576 is the safe ceiling recommendation that covers all known cases.

Distro defaults: do you still need to set this?

As of early 2026, the landscape of default vm.max_map_count values across Linux distributions has changed significantly. Several major distributions now ship with the higher value out of the box, which means you may not need to do anything. Here is the current state:

Step 3: Set the PROTON_BATTLEYE_RUNTIME Launch Option

Some games detect and use the Proton BattlEye Runtime automatically once it is installed. Others require you to explicitly point Proton to the runtime's location via a Steam launch option. If you have completed Steps 1 and 2 and are still being kicked, this is almost certainly the missing piece.

Right-click your game in Steam, select Properties, and in the Launch Options field enter the following -- substituting your actual username and runtime path:

PROTON_BATTLEYE_RUNTIME=/home/YOUR_USERNAME/.local/share/Steam/steamapps/common/Proton\ BattlEye\ Runtime/ %command%

If your Steam library is in a non-default location, the path will be different. To find it precisely, right-click "Proton BattlEye Runtime" in your Steam library, choose Manage, then Browse local files. Copy the directory path shown in your file manager and use that in the launch option.

Confirming the path with a quick terminal check

# Find where Steam installed the runtime
$ find ~ -maxdepth 8 -type d -name "Proton BattlEye Runtime" 2>/dev/null

# List the contents to confirm it's valid
$ ls "$(find ~ -maxdepth 8 -type d -name 'Proton BattlEye Runtime' 2>/dev/null | head -1)"

A valid runtime directory will contain files including run, reaper, and a v2 or similar subdirectory. If the directory is empty or the find command returns nothing, the runtime did not install correctly -- go back to Step 1 and reinstall it.

Understanding the heartbeat timeout

A detail that is consistently missing from other guides: BattlEye's "client not responding" kick is not instantaneous. The server expects heartbeat packets from the BattlEye client at regular intervals. When the client fails to respond, the server applies a grace period before issuing the kick. This is why players report being kicked anywhere from 5 seconds to 3 minutes after joining -- the variation depends on where in the heartbeat cycle the connection failure occurs, what the server's configured timeout threshold is, and whether BattlEye partially initialized before failing. A kick within 5-15 seconds typically means BattlEye never started at all (missing runtime). A kick at 30-120 seconds usually means BattlEye started but could not complete initialization (wrong path, low vm.max_map_count). A kick at 2-3 minutes consistently suggests the heartbeat was established but is being dropped periodically, which points to Proton version issues or overlay interference rather than missing configuration.

Step 4: Choose the Right Proton Version

Not all Proton builds handle the BattlEye runtime the same way. Proton Experimental receives the most frequent updates and is generally the best starting point for BattlEye-protected games. However, some games have reported better stability with specific stable releases. As of early 2026, Proton 10.0-4 is the latest stable release and should be the first alternative you try if Proton Experimental causes issues. Proton 9.0-4 remains a reliable fallback for games that have not been tested against the Proton 10 branch. Older versions like Proton 8.0-5 are worth trying only if newer builds introduce regressions for your specific game -- do not default to them, as they lack years of compatibility improvements.

To set the Proton version for a specific game, right-click the game in Steam, open Properties, go to Compatibility, check "Force the use of a specific Steam Play compatibility tool," and select your version from the dropdown.

If you are using a custom Proton build such as GE-Proton (GloriousEggroll, formerly called Proton-GE) or Proton-CachyOS, note that these builds include additional patches and often have better compatibility with BattlEye than upstream Proton for some games. GE-Proton in particular has a long history of including fixes ahead of the official releases. You can install GE-Proton using ProtonUp-Qt:

# Flatpak -- recommended and officially supported on all distros
$ flatpak install flathub net.davidotek.pupgui2

# Launch via Flatpak
$ flatpak run net.davidotek.pupgui2

# Arch / Manjaro / CachyOS -- AUR only, requires an AUR helper
$ yay -S protonup-qt-bin

# After installing via AUR, launch with:
$ protonup-qt

Once GE-Proton is installed and Steam is restarted, it will appear in the compatibility tool dropdown alongside the official Proton versions. GE-Proton releases follow the naming convention GE-Proton10-33 (the first number tracks the upstream Proton major version, the second is the GE release number). You may still see "Proton-GE" used in older forum posts and guides -- it is the same project, renamed.

Step 5: Reinstall BattlEye's In-Game Service Files

BattlEye ships its own service files inside each game's directory -- not just the Proton runtime you installed in Step 1. These are two distinct components that serve different purposes: the Proton BattlEye Runtime (Step 1) is Valve's native Linux bridge that lets BattlEye communicate with the server, while the in-game BattlEye files are the game-specific anti-cheat binaries that the developer bundles with the game itself. These in-game files can become corrupted by partial updates, failed Steam downloads, or prefix conflicts that occur when switching Proton versions mid-session. Because the files live both in the game's installation directory and inside the Wine prefix, corruption in either location can cause persistent kick loops that survive even a full game reinstall if you do not clean both locations.

Method A: Use the uninstall/reinstall batch script

Navigate to the BattlEye subdirectory inside the game's installation folder. For Steam games, this is typically:

# Example for DayZ (App ID 221100)
$ ls ~/.local/share/Steam/steamapps/common/DayZ/BattlEye/

# You should see files including BEService.exe and Install_BattlEye.bat

If you see these files, you can run the uninstall followed by reinstall via Proton. However, the most reliable approach for Linux users is simply to delete the BattlEye folder entirely and let Steam replace it through file verification:

# Remove corrupted BattlEye files for DayZ (adjust path for your game)
$ rm -rf ~/.local/share/Steam/steamapps/common/DayZ/BattlEye/

# Then in Steam: right-click game > Properties > Local Files > Verify integrity

Method B: Delete the user-level BattlEye data

BattlEye also writes data to a per-user location inside the Wine prefix. Stale or corrupted data there can cause persistent kicks even after the game files are clean:

# Find BattlEye data inside the game's Wine prefix
# Replace APPID with the Steam App ID of your game
$ find ~/.local/share/Steam/steamapps/compatdata/APPID/ -type d -name "BattlEye" 2>/dev/null

# Review what find reports, then delete each result individually
# The -print0 / xargs -0 pattern handles paths with spaces safely
$ find ~/.local/share/Steam/steamapps/compatdata/APPID/ -type d -name "BattlEye" -print0 2>/dev/null | xargs -0 rm -rf

# Verify game files afterward to restore any needed files

Steam Deck Specifics

The Steam Deck runs SteamOS, which is a Linux distribution, and BattlEye via Proton applies the same way. However, there are a few Deck-specific considerations.

First, the vm.max_map_count change described in Step 2 is not necessary on the Steam Deck. SteamOS ships with vm.max_map_count already set to 2147483642 (MAX_INT - 5), which is far higher than the 1048576 recommended for desktop distributions. Valve set this value specifically to ensure maximum game compatibility out of the box. If you are on a Steam Deck, you can skip Step 2 entirely.

Second, some BattlEye-protected games require an additional launch option on Steam Deck to prevent the game from applying alternative code paths that can interfere with BattlEye initialization:

SteamDeck=0 PROTON_BATTLEYE_RUNTIME=/home/deck/.local/share/Steam/steamapps/common/Proton\ BattlEye\ Runtime/ %command%

The SteamDeck=0 flag tells the game and Proton not to identify the session as a Steam Deck environment. Some games use this flag to apply alternative rendering or input code paths that can interfere with BattlEye initialization or cause performance regressions. Placing it before the PROTON_BATTLEYE_RUNTIME variable is intentional -- Steam reads launch option environment variables left to right.

Diagnosing Persistent Kicks

If you have followed all of the above steps and are still being kicked, you need to read the actual BattlEye logs to understand what is failing. BattlEye writes log output to a file inside the game directory and to the Wine prefix. Checking these is the only way to see the specific error rather than guessing.

Finding BattlEye logs

# Look for BattlEye log files in the game directory
$ find ~/.local/share/Steam/steamapps/common/ -name "BEClient*.log" 2>/dev/null
$ find ~/.local/share/Steam/steamapps/common/ -name "BattlEye*.log" 2>/dev/null

# Run Steam from a terminal to see real-time output including Proton/Wine messages
# Launch your game normally from the Steam UI after running this
$ steam 2>&1 | tee ~/steam-terminal.log

# Once the session is done, filter the captured log for BattlEye-related lines
$ grep -i battleye ~/steam-terminal.log

Enable verbose Proton logging

For a full picture of what Proton is doing when BattlEye initializes, you can enable verbose logging by adding this to your launch options (temporarily -- the log files can become very large):

PROTON_LOG=1 PROTON_BATTLEYE_RUNTIME=/home/YOUR_USERNAME/.local/share/Steam/steamapps/common/Proton\ BattlEye\ Runtime/ %command%

With PROTON_LOG=1 set, Proton writes a detailed log to your home directory as ~/steam-APPID.log (where APPID is the numeric Steam App ID of the game). Search this file for "battleye," "client," or "runtime" to find the relevant section.

If you prefer to keep logs out of your home directory, you can redirect them by adding PROTON_LOG_DIR alongside PROTON_LOG:

# Create the directory first
$ mkdir -p ~/proton-logs

# Then in Steam launch options:
PROTON_LOG=1 PROTON_LOG_DIR=/home/YOUR_USERNAME/proton-logs PROTON_BATTLEYE_RUNTIME=/home/YOUR_USERNAME/.local/share/Steam/steamapps/common/Proton\ BattlEye\ Runtime/ %command%

Common error patterns and what they mean

Third-Party Tools and Overlays

BattlEye scans the game process and any libraries loaded into it. On Linux, this includes Wine-loaded DLLs, overlay software, and hardware monitoring tools running alongside the game. BattlEye's official FAQ addresses this directly:

"Generally we only ever ban for the use of actual cheats/hacks."

-- BattlEye FAQ (battleye.com/support/faq)

However, while BattlEye does not ban for non-cheat software, it can and does kick players for specific programs that trip its detection rules. Their FAQ also notes that macro tools may result in kicks (not bans), and that "[INFO] Blocked loading of file" messages do not indicate a ban risk but can still disrupt game operation.

When troubleshooting persistent kicks after completing all setup steps, temporarily close or disable the following and test again:

• Discord's in-game overlay -- Discord's overlay injects into the game process and is a known source of BattlEye tension on some titles. You will find reports online both from people who run it with no problems and from people who solved unexplained kicks by disabling it. The safe move during diagnosis is to disable it.
• MangoHud and vkBasalt -- These Vulkan layers hook into the rendering pipeline. The vast majority of Linux players run MangoHud alongside BattlEye games without any issue, and it is not listed by BattlEye as a blocked application. It is included here strictly as a diagnostic variable to isolate. If disabling MangoHud fixes your kicks, report it on ProtonDB -- it would be an unusual finding worth documenting.
• GameMode (Feral) -- Generally fine, but worth disabling as a variable during diagnosis.
• NVIDIA Ultra-Low Latency Mode -- BattlEye's official FAQ specifically mentions this as a cause of application termination issues on Windows; the same can apply in Wine environments.
• Input remapping tools -- Macro tools and input remappers can trip BattlEye's kick logic even if they do not trigger a ban. This is one of the more consistently documented causes of non-configuration kicks across multiple games.

How to Set Up BattlEye on Linux

Step 1: Install the Proton BattlEye Runtime

Open Steam and filter your library to show Tools. Search for "Proton BattlEye Runtime" and install it. This is the foundational requirement for BattlEye to operate under Proton. Without it, no BattlEye-protected server will accept your connection regardless of any other configuration you apply.

Step 2: Set vm.max_map_count to 1048576 permanently

Open a terminal and run: echo 'vm.max_map_count=1048576' | sudo tee /etc/sysctl.d/99-vm-max-map-count.conf followed by sudo sysctl --system to apply immediately. This kernel parameter must be raised for games like DayZ and Arma 3 that require many memory map regions under Wine. Without it, the game will freeze at load or crash partway through a session even if BattlEye is configured correctly.

Step 3: Verify and set the PROTON_BATTLEYE_RUNTIME launch option

Right-click your game in Steam, open Properties, and set this in the Launch Options field: PROTON_BATTLEYE_RUNTIME=/home/YOUR_USERNAME/.local/share/Steam/steamapps/common/Proton\ BattlEye\ Runtime/ %command%. Confirm the path exists first using find ~ -maxdepth 8 -type d -name "Proton BattlEye Runtime". Explicitly setting this variable resolves the majority of remaining kick issues after the runtime is installed.

Step 4: Reinstall BattlEye in-game files if needed

If kicks persist after the above three steps, delete the BattlEye folder inside the game's installation directory and then verify game files in Steam. Also delete any BattlEye data inside the game's Wine prefix (at ~/.local/share/Steam/steamapps/compatdata/APPID/). Stale or partially updated BattlEye service files inside the prefix can cause kick loops that survive reinstalling the game itself.

Frequently Asked Questions

Why does BattlEye kick me from servers on Linux even though the game launches?

The game launching and BattlEye working are two separate things under Proton. BattlEye requires its own Linux-compatible runtime layer called the Proton BattlEye Runtime, which must be installed separately from Steam's Tools section and, for some games, explicitly pointed to via the PROTON_BATTLEYE_RUNTIME environment variable in your launch options. Without this, BattlEye's service cannot establish a heartbeat with the server, causing the client not responding kick after a short delay.

What is the Proton BattlEye Runtime and where do I install it?

The Proton BattlEye Runtime (Steam App ID 1161040) is a compatibility tool published by Valve that allows BattlEye's anti-cheat service to function inside the Proton/Wine translation layer. You install it from your Steam library by filtering the library view to Tools and searching for Proton BattlEye Runtime. Once installed, many games will pick it up automatically, but some require a manual PROTON_BATTLEYE_RUNTIME launch option pointing to its installation directory.

What is vm.max_map_count and why does DayZ require it to be raised on Linux?

vm.max_map_count is a Linux kernel parameter that limits how many separate memory map areas a single process can create. DayZ and several other Proton-run games require a significantly higher value than the standard kernel default of 65530 to load their assets without freezing or crashing. SteamOS on Steam Deck ships with this value already set to 2147483642 (MAX_INT - 5) and does not need adjustment. Arch Linux (since April 2024), Fedora 39+, and Ubuntu 24.04+ also now default to 1048576. On distributions that still default to 65530 -- including Debian 12, Debian 13, and openSUSE -- you can set it temporarily with sudo sysctl -w vm.max_map_count=1048576 or permanently by writing to /etc/sysctl.d/. Note that Debian 13 no longer reads /etc/sysctl.conf; the drop-in directory method is required. Always check your current value with sysctl vm.max_map_count before making changes.

Does BattlEye on Linux actually work, or will I be banned for using Proton?

BattlEye officially supports Proton on Linux. Valve and BattlEye announced this integration in late 2021, and the Proton BattlEye Runtime is a legitimate, supported tool. You will not be banned simply for running the game through Proton. Bans only occur for actual cheats and hacks. The kicks players experience are configuration errors, not enforcement actions, and can be resolved by following the setup steps correctly.

This question deserves a more direct answer because there is a lot of conflicting information online. The concern typically comes from two sources: older forum posts from before the 2021 Proton support announcement (when using Proton with BattlEye games was genuinely unsupported), and game-specific situations like GTA Online where the developer -- not BattlEye -- chose to block Proton clients at the server level. In those cases, players were not banned for using Proton; they were simply kicked because the developer disabled Proton support server-side. BattlEye's own FAQ and ban appeal policy are clear that Proton usage is not a bannable offense. For games where the developer has enabled Proton support, using Proton with the correct setup is the fully supported path.

Sources and References

Technical details in this guide are drawn from official documentation and verified sources.

• BattlEye FAQ -- official BattlEye documentation on client not responding errors, blocked file messages, and ban policy
• Valve Steamworks: Update on BattlEye + Proton support -- official Valve announcement of BattlEye Proton integration, December 2021
• BattlEye (@TheBattlEye) Proton support announcement -- original BattlEye announcement confirming opt-in Proton/Steam Deck support, September 24, 2021
• GamingOnLinux: More BattlEye titles for Proton on Linux -- coverage of the rollout including vm.max_map_count requirements for DayZ
• Bohemia Interactive Community: Arma 3 Play on Linux -- official Arma 3 Linux setup wiki including BattlEye Runtime installation steps
• BrebisSolide: easier-dayz-CLI-Linux-launcher -- DayZ Linux launcher documentation covering vm.max_map_count and Proton setup requirements
• Linux Kernel Documentation: /proc/sys/vm/ -- official kernel documentation confirming the default vm.max_map_count value of 65530
• Arch Linux: Increasing the default vm.max_map_count value -- official Arch Linux announcement raising the default to 1048576 in the filesystem package, April 2024
• Phoronix: Fedora 39 vm.max_map_count boost -- coverage confirming SteamOS ships with vm.max_map_count set to 2147483642 (MAX_INT - 5) and Fedora's adoption of the increased value
• SteamDB: Proton BattlEye Runtime (App 1161040) -- Steam database record confirming the Proton BattlEye Runtime app ID and metadata