WARDOGS server administration
WARDOGS RCON tools for community server admins
WarGuardian combines WARDOGS server administration, community bans, staff permissions and player evidence review in a hosted browser panel. Your first server is free.
What is WARDOGS RCON?
RCON means remote console.
WARDOGS exposes an RCON interface that lets authorized administrators read server information and send supported management commands.
An RCON panel gives your staff a web interface for those tasks.
WarGuardian connects to that interface from its service.
Your admins use their own sign-in and the permissions you assign.
You can manage several community servers from one dashboard.
What can you manage with WarGuardian?
- Players and moderation. View connected players, review their history, issue warnings, kick players and manage bans.
- Maps and match controls. Manage supported map rotations and match settings without composing raw requests.
- Staff access. Assign permissions by community and server. Keep a record of staff actions.
- Shared ban lists. Maintain community ban records and share lists with other participating communities.
- Player evidence. Connect the kill feed to review combat records and investigate flagged activity.
- Community operations. Configure supported automation, priority queues, broadcasts and Discord integration.
Available controls depend on the RCON capabilities your WARDOGS server exposes and the permissions your account has.
WARDOGS capabilities and requirements
| Workflow | WarGuardian capabilities | Requires |
|---|---|---|
| Live administration | Roster, messages, kicks, bans, faction changes, maps and supported match controls. | A reachable RCON endpoint and the relevant staff permission. |
| Community bans | Reasons, timed and offline bans, selected-server scope, private shared lists and evidence review. | Explicit sharing/subscription choices and authorized server access. |
| Player history | Recorded aliases, visits, notes, watchlist activity and command history. | Collected history; gaps remain visible. |
| Steam context | Available profile age, visibility, VAC bans and game bans. | Configured Steam integration; public/cached data may be incomplete. |
| Combat review | Kill records, weapon comparisons, review summaries and source coverage. | The appropriate connected event feed and retained records. |
| Reports | Player report links, ticket assignment, replies and private staff notes. | Enabled report entry points and authorized staff. |
| Priority access | Reserved slots, whitelist controls and configured seeding rewards. | Supported game configuration and explicit policies. |
| Integrations | Discord notifications, authorized bot/script APIs and MCP evidence review. | Configured integrations and scoped access. |
Community bans with reasons and evidence
Review a player, record the reason and choose the intended server scope. Timed bans retain their deadline; offline actions can remain queued until the player joins. Check delivery status before assuming the game server has applied a decision.
Private lists let participating communities share selected moderation records through authorized subscriptions. Review the issuer, reason, evidence and expiry before applying another community's decision. List access does not grant access to all of the source community's private player history or staff notes.
The public ban-list directory is a separate view of explicitly published lists. Private sharing and public publication are separate choices.
Investigate a player report
- Open or claim the community ticket and check the incident server.
- Review the account's recorded visits, aliases, notes and action history.
- Inspect relevant kill records, weapon comparisons and source coverage.
- Check footage, record the staff finding and confirm any moderation action.
Steam context, watchlist flags and statistical indicators help staff decide what to investigate. They do not prove cheating. An optional AI summary uses a configured provider or available trial; staff should check its findings against the underlying evidence.
A connected RCON endpoint does not establish complete combat history. Missing Steam data is not a clean ban history, and a relationship between accounts does not establish common ownership.
WARDOGS automation and server operations
| Task | Available tools |
|---|---|
| Manage factions | Team balancing, team-switch locks and configured Infected mode. |
| Enforce player policies | Sustained high-ping rules, idle cleanup, name/protected-tag policies and Steam-based connect rules. |
| Apply combat rules | Configured team-kill limits and weapon block/allow policies. Weapon restrictions kick; they do not add bans. |
| Seed a server | Seeding protection and temporary priority-access rewards. Protection's respawn cycle affects connected players, including active players. |
| Communicate | Player messages, recurring announcements, broadcasts and restart warnings. |
| Maintain server activity | Empty-server resets, supported weather changes and configured outage alerts. |
| Create a custom rule | Supported schedule, player or map triggers with conditions and broadcast, message, warning or kick actions. |
Configure rules for the selected server and check their required sources and permissions. Use dry run or preview where provided, then inspect recent results. A saved rule does not mean that an action has already run successfully.
Choosing a WARDOGS RCON tool
| Requirement | WarGuardian |
|---|---|
| Hosting | Hosted browser panel; keep your existing game host. |
| Staff access | Individual sign-ins and community/server permissions. |
| Ban management | Community ban records and shared lists with participating communities. |
| Player review | History and combat evidence when the kill feed is connected. |
| Server operations | Supported map controls, automation, broadcasts and Discord integration. |
| Starting cost | First WARDOGS server free; current plans and beta terms. |
Choose a tool that supports your game build, moderation workflow and hosting requirements. Check game-specific features before moving an existing community.
Compare WarGuardian, Warcon and BattleMetrics by hosting, staff access, player history and ban management. The current feature catalog has additional workflow details.
What do you need to connect?
You need a WARDOGS community server with RCON enabled, its RCON address and port, and its RCON password.
Your hosting provider supplies those details.
The RCON port may differ from the port players use to join the game.
WarGuardian is hosted, so you do not install the panel on your own web server.
Follow the WARDOGS RCON connection guide to test your endpoint and connect your community.
Questions from WARDOGS server owners
Is WarGuardian the official RCON tool?
No.
WarGuardian is an independent community administration service.
WARDOGS also provides its own RCON console.
Does every admin need the server password?
No.
Connect the server once, then give staff their own access and roles.
Staff permissions determine which actions each person can use.
Can WarGuardian prove that a player is cheating?
Player reviews organize evidence for your staff.
A flag or a high score is a reason to investigate, rather than proof of cheating.
How much does it cost?
Your first server is free.
See WarGuardian pricing for current community plans and beta terms.
Does shared ban access automatically ban players everywhere?
Sharing records and selecting enforcement scope are separate choices. Review the source and the destination servers before activating an enforcement workflow.
Does WarGuardian replace my hosting provider?
Your dedicated server stays with its existing provider. WarGuardian needs access to its supported RCON endpoint; feed-based review also needs the configured event source.
Run your WARDOGS community with WarGuardian
Start with one server, connect your RCON endpoint and invite your staff.
Create your community