Based on my packet analysis with Wireshark while using the official BattlEye RCON client:
1. Protocol Modifications
• Reforger implements a modified BattlEye RCON protocol incompatible with previous titles
• Packet structures and handshake procedures have been altered
• Response formatting deviates from the standard BattlEye implementation
2. Restricted Command Set
• Only 4 basic commands are supported (kick, restart, shutdown, ban)
• Existing tools expect the full command set, causing failures when attempting other operations
• Response handling is unreliable with the modified protocol
3. Player Data Limitations
• Reforger only provides proprietary UUIDs rather than BattlEye GUIDs
• Critical identifiers (Steam IDs, IP addresses) used by arma 3 tools are unavailable
• Player information is structured differently, breaking compatibility with older tools
4. Connection Management Issues
• Authentication sequences and connection maintenance differ from previous implementations
• Packet sequencing and heartbeat expectations have changed
• Standard tools fail to maintain stable connections as a result
5. Critical Missing Functionality
• No chat transmission or monitoring capability
• Absent server performance monitoring
• No server configuration access
I'm currently developing my own monitoring solution and RCON client/Discord bot using a BattlEye protocol library. As a workaround, I've found the server console.log files valuable for reconstructing player sessions and gathering analytics (FPS, frame times, memory usage) which I'm storing in a database for analysis.
Even with custom development, the current limitations mean any tool can only provide basic functionality compared to the administration capabilities available in previous Arma titles.