Development status checked: 20 September 2026. Frontline WARDOGS CRCON is our independent administration and community system for WARDOGS servers. This article shows the current interface, explains the verified read-only integrations and clearly separates them from functions that are still being tested.
Why WARDOGS needs its own CRCON
RCON traditionally describes remote administration of a game server. A useful community platform has to do more than send isolated commands. It must show which server is selected, when the data was observed, what an operator is allowed to do and whether an action was actually confirmed by the target system.
WARDOGS CRCON is therefore not a renamed Hell Let Loose tool. WARDOGS has its own server interface, data model and operational behaviour. We reuse experience from Frontline RCON and ARCON, but every capability is implemented and verified for the WARDOGS environment.
The current dashboard
The documented product state brings together live operation, map rotation, player context, moderation, campaigns, history and multi-server management. The interface is intended to support the complete operational flow rather than scatter individual actions across unrelated screens.
- Live operation: connection state, map, mode, factions, occupancy and available match values.
- Maps and rotation: current map, variants, planned sequence and saved profiles.
- Players and moderation: session context, local observations, watchlists and confirmed outcomes.
- Community operations: reusable announcements, campaigns, history and role-based access.
Maps, variants and rotation
Rotation management is more than choosing a map name. The interface keeps the active match, available variants, light conditions and the stored order together. A saved plan is not presented as active until the server confirms the change.
Moderation with context and confirmation
A conspicuous number is not enough to justify a moderation decision. CRCON distinguishes live server information, historical observations, local notes and confirmed incidents. An action also remains marked as requested until the target system has returned a reliable result.
This fail-closed approach is particularly important when more than one server is connected. The target server is selected explicitly, permissions are checked for that target and central RCON credentials are never exposed to a normal browser or Discord user.
Campaigns and reusable communication
Stable community operations include rules, scheduled events and recurring information. The campaign area is designed to prepare reusable content, schedule it and record its processing state. It is not intended to become an uncontrolled broadcast route.
Discord integration: what is already verified
Not every community member needs access to the administration panel. Selected information can be published through narrowly scoped server-side read paths. A persistent server-status board and live leaderboard views have been verified in the Frontline Discord environment.
These are intentionally separate from write functions. Automated VIP assignment, expiry handling and community-points integration are not advertised as generally available. They require a complete identity, permission, target-server, confirmation and rollback path before production approval.
Current capability status
| Area | Current evidence | Status |
|---|---|---|
| Web interface | Live, maps, rotation, players, moderation, campaigns, history and management are represented in the documented product state. | Documented |
| Server data | Separate server connection and protected website read path have been tested in production context. | Verified read path |
| Discord status | Persistent status board and live leaderboard reads use approved server-side access. | Verified read path |
| VIP and points | Assignment, expiry and community-points flows are prepared or under development. | Not generally released |
| Public hosting offer | No general self-service product is promised yet; clearly scoped tests are reviewed individually. | By arrangement |
How a test with Frontline works
We first document the community’s server setup, roles and daily workflows. Then we define a small test with clear boundaries and expected evidence. Read-only access comes before write access. A function is released only when permissions, target selection, confirmation, logging and rollback have been checked together.
This keeps the project useful without pretending that every visible button is already a finished service. Communities interested in that process can contact Frontline. Players can follow updates and meet the community on the Frontline Discord. The full product overview is available on the WARDOGS CRCON page.
Frequently asked questions about WARDOGS CRCON
What does CRCON mean in this project?
It describes the controlled remote administration and community layer around a WARDOGS server, including data presentation, workflows and integrations.
Is WARDOGS CRCON an official BULKHEAD or Team17 product?
No. It is developed by Frontline Network and uses the interfaces available for the game.
Is it the same application as Frontline RCON?
No. It is an independent system for WARDOGS. Operational experience is shared, but the connection, data and capabilities are implemented separately.
Which dashboard areas exist today?
The documented interface covers live operation, maps and rotation, players, moderation, campaigns, history and multi-server administration.
Can CRCON manage several WARDOGS servers?
The interface includes multi-server context and explicit target selection. Availability and permissions still have to be verified for each connected server.
Which Discord functions are verified?
A persistent status board and live leaderboard read paths have been tested in the Frontline environment.
Can Discord automatically grant VIP access?
Not as a generally released function. VIP assignment and expiry are separate write workflows that remain behind their own approval gate.
Are community points already connected?
The integration is being prepared or developed but is not presented as a generally available production feature.
Are RCON credentials sent to website visitors or Discord users?
No. Sensitive server access remains on controlled server-side systems.
How are moderation actions confirmed?
A request and a successful result are separate states. An action is complete only after a reliable response from the target system.
Can I buy WARDOGS CRCON now?
It is not yet a generally released shop product. Frontline can discuss a clearly scoped test with suitable communities.
Does the product include WARDOGS game hosting?
The administration layer and the game server are separate services. A combined setup may be evaluated, but no universal package is promised on this page.
What happens when the WARDOGS API changes?
Capabilities are rechecked and are disabled when their contract or confirmation path is no longer reliable.
Where is the current development status documented?
This article and the product page use a dated status and distinguish visible, verified and unreleased capabilities.
Can another community help test CRCON?
Yes, when the test has a clear scope, named responsibilities and a safe rollback path.
Where can players join the Frontline WARDOGS community?
Join the Frontline Discord and select the WARDOGS role to follow server and event information.
No comments yet
Comments add to the contribution. For support, reports or exile, please use the appropriate professional route.
Log in to comment
Comments run through your central customer account. Sign in or create an account by email or Discord; then you will come back to this post directly.