ArmA 3 RCON Tool by BattleMetrics

What is RCON?

RCON is used to implement admin tools for your game. Basically it lets you see what's going on in the server without you having to spend ages starting up a game client and connecting to your server manually. You can run commands remotely and automatically. Kick, ban, restart, you name it. Whatever the game server will let you do over RCON is possible.

Can I detect VPNs or ban evaders using BattleMetrics?

Yes! We track players by IP and use an external service to help us determine if an IP is a VPN. Additionally, we will tell you how many other players match the IP in question. You can even set up triggers to automatically do something if the player has many players that share the same IP.

How do I automate running my server?

You can automate a lot of rules and common tasks using triggers and schedules. You can automatically kick, ban, message, etc in response to any number of conditions. Don't want players with fewer than 250 game hours? Done. Don't want players saying racist things in chat? Easy. Want to get notified when a player asks for an admin? Not a problem. For more information on triggers and the scheduler, see these resources:

Trigger System Overview
The Scheduler
Example Triggers

Can I automatically message players?

Yes. Using triggers and schedules you can send Global Chat messages automatically. Unfortunately private messages are only supported by triggers and not schedules.

How do I ban players?

You can ban a player by clicking the drop down menu next to their name and clicking “Add Ban”. This will add the ban to our internal database. We'll kick the player from the server and continue to kick them if they try to rejoin while the ban is active. This does not take up any additional resources on your server.

Can I ban players without using the BattleMetrics database?

Sure, you just need to issue the "Add BattlEye Ban" command for the player you want to ban. You can run any supported RCON command through our system.

How do I automatically ban cheaters for script violations?

You can do this using triggers. Create a trigger with the “BattlEye Log” type. Use the Log Type, Line Number, Log Body, and/or Resulted in Kick conditions to automate the rule. One example would be to have the condition of Log Type = scripts.txt, Line number > 0, and resulted in kick = true. Those conditions would only act on players that violate the scripts.txt restrictions after the first line (line 0) and where such a violation resulted in a kick. This can save you a great deal of time combing through your logs manually looking for cheaters.