ArmA 2 Server Management
Quick answer
CFTools Cloud provides ArmA 2 server management over BattlEye RCon for communities that still operate ArmA 2 and legacy DayZ-mod era servers. You get real-time monitoring, searchable logs, permanent global player profiles with GUID variant handling and Steam lookup, fully granular RBAC without sharing the RCON password, ban lists with cross-server and community-wide sharing, scheduler and triggers, Discord integration, and API access. Paid Cloud plans retain logs for at least 30 days and up to 180 days. CFTools Architect and GameLabs are not available for ArmA 2; Cloud is the supported product for this title.
Support summary
| Feature area | ArmA 2 support |
|---|---|
| CFTools Cloud | Supported |
| CFTools Architect | Not Available |
| GameLabs | Not Available |
| RCon logs | Supported |
| Player history | Supported |
| Ban list & ban sharing | Supported |
| Community-wide ban sharing | Supported |
| Granular RBAC (no shared RCON password) | Supported |
| Discord integration | Supported |
| Queue-priority synchronization | Not Applicable |
What CFTools can do for ArmA 2
- Monitor ArmA 2 server availability and status 24/7 over RCon
- Track players with permanent global profiles across sessions
- Manage ban lists; share across your servers and community-wide
- Resolve GUID variants and Steam identities for moderation
- Grant staff fully granular RBAC without sharing the RCON password
- Retain paid-plan logs for 30 to 180 days depending on plan
- Schedule restarts, broadcasts, and recurring admin jobs
- Trigger automatic actions from server and player events
- Send Discord alerts for staff and community operations
- Automate custom workflows through the REST API
CFTools Cloud for ArmA 2
Monitoring and RCon for ArmA 2
CFTools Cloud keeps a persistent BattlEye RCon connection to your ArmA 2 server so you can monitor uptime, players, and logs without launching a game client.
- 24/7 real-time monitoring
- Live player list and session visibility
- Searchable RCon and audit logs
- Paid log retention from 30 to 180 days depending on plan
Players and ban intelligence
ArmA 2 communities often deal with long-lived player identities. CFTools uses permanent global profiles with GUID variant handling and Steam lookup, and supports ban sharing across your servers and community-wide.
- Permanent global player profiles
- GUID variant handling and Steam lookup
- Cross-server and community-wide ban sharing
- Whitelist controls
- VPN detection and geoblocking options
- Granular RBAC without sharing RCON
Automation for legacy ArmA 2 networks
Scheduler, triggers, messenger, Discord, and API tooling help keep older ArmA 2 networks operable with modern admin workflows.
- Scheduled restarts and announcements
- Event-based triggers for common moderation tasks
- In-game commands where supported by RCon
- Discord notifications for staff
- REST API for external tools
- Name and chat filters
ArmA 2 requirements
CFTools Cloud for ArmA 2 requires a reachable dedicated server with BattlEye RCon. Architect and GameLabs are not available for this title.
- An ArmA 2 dedicated server reachable over the internet
- BattlEye RCon enabled and correctly configured
- Network/firewall access for the RCon port
- A CFTools Cloud account to register the server
- Host or firewall rules that allow persistent RCon connections
Setup flow
- 1Create or sign in to your CFTools Cloud account.
- 2Add your ArmA 2 server and provide its connection details.
- 3Configure and verify BattlEye RCon access.
- 4Confirm CFTools can see live players and logs.
- 5Configure ban lists, RBAC roles, Discord alerts, and automation.
Common admin workflows
How admins monitor ArmA 2 players
Admins review the live player list and historical global profiles to identify returning players across aliases and act with kicks, bans, or messages.
How ban sharing protects ArmA 2 communities
Shared and community-wide ban lists help older ArmA 2 networks coordinate moderation without manually syncing ban files between servers.
How staff access is delegated
Fully granular RBAC lets network owners grant limited Cloud permissions without handing out the ArmA 2 RCON password.
How restarts are scheduled
The scheduler runs restart jobs and optional broadcast warnings so players know when the ArmA 2 server will go down.
How Discord keeps legacy staff loops alive
Discord integrations forward selected events so volunteer staff can respond even when they are not watching the Cloud dashboard.
How the API extends ArmA 2 tooling
Communities can use the REST API to connect websites, bots, or custom moderation tools to CFTools Cloud data for ArmA 2.
Known limitations
- CFTools Architect is not supported for ArmA 2; Cloud manages existing servers only.
- GameLabs is DayZ-only and is not available for ArmA 2.
- DayZ-only features such as queue-priority synchronization do not apply to ArmA 2.
- Live features depend on a correctly configured BattlEye RCon connection.
- ArmA 2 is a legacy title; available RCon commands depend on the server and BattlEye configuration.