Configure Easy Anti Cheat on a Rust Server
Setting up Easy Anti Cheat (EAC) on your Rust server ensures that players connecting with EAC enabled are protected from cheaters, and it’s required for official and most community servers. This guide walks you through enabling EAC on your server, updating the necessary files, and verifying that it’s working correctly.
What You’ll Need
- A Rust dedicated server (either your own hardware or a rented server from a provider).
- Access to the server’s command line or control panel (e.g., via SSH, RCON, or a web host panel).
- Administrator privileges on the server to modify configuration files.
- Basic familiarity with editing text files and running server commands.
Step-by-Step
- Stop your Rust server to avoid conflicts while editing files. Use your control panel’s stop button or run the
quitcommand in the server console. - Locate your server’s installation folder. This is usually where the
RustDedicatedexecutable or the server files are stored. If you’re using a hosting provider, check their documentation for the file path. - Open the server configuration file. In most setups, this is
server.cfglocated in theserverfolder, or you may have a startup script (e.g.,start.shorrun.bat). Look for a line that starts with+server.eacor-eac. - Enable EAC by adding or modifying the launch parameter. If you’re using a command-line startup, add
+server.eac 1to the command. If you’re using a config file, setserver.eac 1. For example, in a typical startup command:./RustDedicated -batchmode +server.port 28015 +server.level "Procedural Map" +server.seed 12345 +server.maxplayers 50 +server.eac 1
If you’re using a hosting panel, look for a checkbox or field labeled “Easy Anti Cheat” and enable it.
- Save the file and ensure the line is not commented out (no leading
//or#). - Start your server again. Watch the console output for a message like “EAC enabled” or “Easy Anti Cheat is active.” If you don’t see it, check the next steps.
- Verify from the client side: Join your server from the Rust client. In the server browser, you should see a shield icon or a note indicating EAC is enabled. If you have EAC disabled in your client, you’ll be prompted to restart with it enabled.
Common Mistakes
- Using the wrong parameter: Some guides mention
-eac(with a dash), but the correct parameter for Rust is+server.eac 1(with a plus). Using the wrong one may not enable EAC. - Forgetting to save the config file: If you edit the file but don’t save it, the server won’t pick up the change.
- EAC not supported on some hosting panels: Some budget hosting panels may not expose EAC settings. In that case, you may need to contact support or switch providers.
- Players with EAC disabled: Even if your server has EAC enabled, players can still join if they launch Rust with EAC disabled (using the “-eac” client launch option). To enforce EAC, you must also set
server.eac 1and consider using a whitelist or a mod that kicks EAC-disabled clients.
Tips
- Keep EAC updated: EAC updates automatically when the server starts, but ensure your server has internet access to fetch the latest anti-cheat definitions.
- Use a startup script: If you’re managing the server manually, create a script that includes the EAC parameter so you don’t forget it on every restart.
- Test with a friend: Have someone join with EAC enabled and another with it disabled to confirm the server enforces it correctly.
- Check the server log: After starting, look for lines containing “EAC” in the log file (usually
Log.EAC.txtin the server folder) to confirm it’s running.
Troubleshooting
- Server won’t start after enabling EAC: Double-check that you added the parameter correctly. If the server crashes, try removing the parameter and starting again. If it still crashes, the issue might be unrelated—check the full error message.
- EAC not showing as enabled in the console: Ensure the parameter is exactly
+server.eac 1(with a plus sign and no spaces around the equals). Also, verify that you’re editing the correct config file—some servers use a separateserver.cfgfor commands, but launch parameters go in the startup command. - Players get kicked for EAC issues: This can happen if the player’s EAC client is outdated or corrupted. Ask them to verify game files through Steam or reinstall EAC. On your side, ensure the server’s EAC files are intact—you can delete the
EasyAntiCheatfolder in the server directory and let it re-download on restart. - EAC works but players with it disabled can still join: This is expected behavior. To block them, you need to use a plugin like
EAC Kickeror configure your server to require EAC (some mods offer this). Alternatively, set your server to “official” mode, which forces EAC.
Frequently Asked Questions
Do I need to enable EAC on my Rust server?
It’s highly recommended. Most public servers require EAC to prevent cheating, and many players filter for EAC-enabled servers. Official Rust servers always have EAC on.
Can I enable EAC on a server hosted on a home PC?
Yes, you can. The process is the same as for a rented server, but you need to ensure your firewall allows the EAC authentication ports (usually 28015 and 28016).
What does “+server.eac 1” do exactly?
It tells the Rust server to enable Easy Anti Cheat. When set to 1, the server will require players to have EAC running; if set to 0, EAC is disabled.
How do I know if EAC is working on my server?
Check the server console for “EAC enabled” messages, or look for the Log.EAC.txt file in the server folder. Also, try joining with EAC disabled—you should see a warning or be kicked.
Can I turn off EAC later?
Yes, simply change +server.eac 1 to +server.eac 0 in your startup command or config file, then restart the server.
Why do some players get an EAC error when joining?
This usually means the player’s EAC client is outdated or corrupted. They should verify the game files via Steam, or uninstall and reinstall EAC from the Rust installation folder.
Related
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.