ArmA 3 Server Management
Quick answer
CFTools Cloud provides ArmA 3 server management over BattlEye RCon for communities and network operators. You get real-time monitoring, searchable RCon and audit 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 3; Cloud is the supported product for this title.
Support summary
| Feature area | ArmA 3 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 3
- Monitor ArmA 3 server availability and status 24/7 over RCon
- See who is online and review permanent global player profiles
- Manage ban lists; share across your servers and community-wide
- Handle GUID variants and Steam lookup for player identity
- Grant staff fully granular RBAC without sharing the RCON password
- Retain paid-plan logs for 30 to 180 days depending on plan
- Schedule automatic restarts, messages, and other recurring jobs
- Trigger automatic actions based on server and player events
- Send Discord alerts and run in-game admin commands
- Use the REST API for custom ArmA 3 admin tooling
CFTools Cloud for ArmA 3
Monitoring and RCon for ArmA 3
CFTools Cloud connects to your ArmA 3 server over BattlEye RCon for continuous monitoring. You can see live status, connected players, and searchable RCon, server, and audit logs without sitting in-game.
- 24/7 real-time server monitoring
- Live player list with session details
- Searchable RCon logs and audit logs
- Paid log retention from 30 to 180 days depending on plan
Players, bans, and staff access
ArmA 3 player management uses permanent global CFTools profiles with GUID variant handling and Steam lookup. Ban lists can be shared across your servers and community-wide. Fully granular RBAC keeps the RCON password off staff machines.
- Permanent global player profiles
- GUID variant handling and Steam lookup
- Cross-server and community-wide ban sharing
- Whitelist management
- VPN detection, geoblocking, and Steam-related protections
- Granular staff permissions without sharing RCON
Automation and integrations
Scheduler, triggers, messenger, Discord, and the REST API cover common ArmA 3 admin workflows such as restart warnings, automated kicks or bans, and staff notifications.
- Scheduled restarts and recurring jobs
- Event-based triggers
- In-game commands and automated messaging
- Discord notifications and announcements
- REST API for custom integrations
- Name and chat filters
ArmA 3 requirements
CFTools Cloud for ArmA 3 depends on a reachable dedicated server with BattlEye RCon enabled. Architect deployment and GameLabs are not available for this title.
- An ArmA 3 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
- Provider support may vary if the host restricts RCon
Setup flow
- 1Create or sign in to your CFTools Cloud account.
- 2Add your ArmA 3 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 3 players
Admins use the live player list and permanent global profiles to review sessions, resolve GUID or Steam identities, and act via kicks, bans, or in-game commands.
How ban sharing works for ArmA 3
Bans follow the player identity and can be shared across your ArmA 3 servers and community-wide lists, reducing repeat offenders hopping between community servers.
How staff permissions work
Fully granular RBAC lets you grant limited or full Cloud admin actions without distributing the ArmA 3 RCON password.
How scheduled restarts work
The scheduler runs restart jobs and optional pre-restart messages so players get clear warnings before downtime.
How Discord alerts work
Selected ArmA 3 events and admin actions can be forwarded to Discord so staff stay informed without watching the dashboard constantly.
How API automation fits ArmA 3
The REST API exposes Cloud resources so communities can build custom ArmA 3 tools, stores, or moderation bots on top of CFTools.
Known limitations
- CFTools Architect is not supported for ArmA 3; Cloud manages existing servers only.
- GameLabs is DayZ-only and is not available for ArmA 3.
- DayZ-only features such as queue-priority synchronization do not apply to ArmA 3.
- Live features depend on a correctly configured BattlEye RCon connection.
- Some hosting providers restrict RCon access, which can block Cloud connectivity.