ArmA 2 RCON Tool & Admin Panel
CFTools Cloud is an ArmA 2 RCon admin tool for communities that still run ArmA 2, including servers from the legacy DayZ-mod era. It is the same kind of product people search for as an Arma 2 RCon tool. Cloud connects over BattlEye RCon and provides live monitoring, searchable logs, permanent global player profiles with GUID variant handling and Steam lookup, ban sharing, and staff roles that keep the RCON password with the owner. Available RCon commands depend on the server and its BattlEye configuration. Architect and GameLabs are not available for ArmA 2.
No credit card required. A free tier is available.
Admin tool highlights
Monitoring for older dedicated servers
ArmA 2 processes are often long-lived and lightly staffed. Cloud holds a BattlEye RCon connection so someone can see players and logs without keeping a game client open on a second machine.
Profiles for long-lived communities
Older ArmA 2 networks still recognize players by GUID. Permanent profiles, GUID variant handling, and Steam lookup give that history a place that is not a spreadsheet on one admin laptop.
Ban sharing without manual file copies
Share bans across your ArmA 2 servers and use community-wide sharing when several legacy communities want the same list. That replaces copying ban files between hosts by hand.
Delegate access on a legacy box
Volunteer staff can receive limited Cloud roles. They do not each need the ArmA 2 RCON password, which is easy to lose track of on an old server install.
Scheduled restarts and broadcasts
The scheduler can restart the server and send a warning message first. Triggers and the messenger cover the small repeated jobs that older communities still do every night.
Logs that outlive the session
RCon and audit logs stay searchable after the operation ends. Paid plans retain them for 30 to 180 days. Discord and the REST API can forward events to whatever tool the community still uses.
How ArmA 2 RCon administration works
Cloud connects to the existing dedicated server over BattlEye RCon. Edge clusters in NA, EU, OC, and AS keep that connection close to the host. All storage and processing happen in Germany. Staff use the dashboard for the live list, bans, messages, and an audit trail.
What the ArmA 2 command set covers
ArmA 2 is a legacy title. The RCon commands Cloud can run depend on the server build and the BattlEye configuration on that host. Architect does not install or update ArmA 2. GameLabs does not run on ArmA 2. Queue-priority synchronization is DayZ-only and does not apply.
Who this admin tool is for
It fits communities that still operate ArmA 2 or early DayZ-mod era servers and want modern ban sharing, staff roles, and log retention. It is the wrong product if you need someone else to rent you a game slot. You bring the server. Cloud administers it over RCon.
What an ArmA 2 server needs
The dedicated server has to be yours already, and RCon has to answer from the internet.
- An ArmA 2 dedicated server reachable on the internet
- BattlEye RCon enabled and correctly configured
- Firewall access for the RCon port
- A host that allows persistent RCon connections
- A CFTools Cloud account to register the server
CFTools Cloud features for ArmA 2
- 24/7 real-time server monitoring
- VAC protection and automated Steam player rules
- VPN detection
- Geoblocking
- Schedule automatic jobs like restarts
- Trigger automatic actions based on specific events
- In-Game commands
- Automated messages for your players
- Player management and history
- Automatically ID to SteamID conversion
- Whitelist management
- Banlist management
- Banlist sharing
- Discord integration
- API access
- Server logs & RCon logs
- Audit logs
- Statistics tracking
- Global player database with over 6,5 million records
- Statistic analysis for automated player risk ratings
- Name filters against unwanted nicknames
- Chat filters
- Localization - Customize to your local language