Server Setup
How to add your first Rust server
Start in the dashboard and use the server add flow. Enter the server name, IP, RCON port, and password, then run a connection test before saving. The panel is designed to stay lightweight on Lite and more persistent on Premium and Elite.
1. Open DashboardGo to My Servers and use the `+ Add Server` action.
2. Enter Rust RCON detailsUse the public IP or hostname, the correct RCON port, and your current RCON password.
3. Run a testTest the connection before saving so bad host or port input does not get stored as a broken server.
4. Open the workspaceOnce saved, the console, players, reports, plugin health, and other Rust tools will wake up for that server.
Player Enrichment
How to get your Steam Web API key
Steam lookups power better player context like profile age, game bans, and ban history. AegisRcon keeps this as an account setting so the same key can enrich multiple servers from one place.
Where to get itVisit `steamcommunity.com/dev/apikey`, sign in with Steam, set a domain, and copy the generated key.
Where to save itOpen Dashboard > Settings > Platform Integrations and paste the key into the Steam Web API field.
What it unlocksSteam profile lookups, ban history checks, and better player review context across the panel.
Plugin
What AegisBridge unlocks
AegisBridge exists for the Rust data that plain WebRCON does not expose cleanly enough on its own. It is the layer that makes team context, richer combat review, and future anti-cheat or team tracker signals much easier to work with.
Install the plugin
Drop the latest `AegisBridge.cs` into your Rust plugins folder, then load or reload it from the server as you normally would.
Confirm the panel sees it
Open the Plugins workspace and check that AegisBridge shows a healthy state and the expected version.
What gets better
Combat detail, team state, bridge-backed stats, and future anti-cheat-ready telemetry all grow from here.
Keep it lightweight
The bridge is intentionally bounded and optimized so richer Rust context does not become a memory sink on busy servers.
Moderation Flow
How reports and cases are meant to work together
Every report matters, but not every report deserves the same urgency. That is why AegisRcon keeps raw intake and promoted cases separate. Staff can still see what players are reporting in real time, while the serious review queue stays cleaner and easier to work through.
All Reports
The raw intake stream. Useful for pattern awareness, context checks, and seeing what players are sending right now.
All Cases
The promoted queue. This is where repeated or stronger signals become worth focused moderator review.
Automation
How to start with Trigger Automation
Start with a preset, then tune conditions and actions to your server. The trigger builder is designed to stay readable: fields, checks, values, match modes, inner groups, and direct actions are all visible instead of buried behind unclear toggles.
1. Start from a presetUse VPN, bans, threat, reports, or keyword presets as a faster base.
2. Adjust the conditionsChange the thresholds and checks to match your server's actual moderation style.
3. Add grouped logicUse inner match groups when one part of the rule needs its own `all` or `any` logic.
4. Choose actions carefullyWebhook, mute, notes, kick, or ban can all be tied to the rule, but stronger actions should stay owner-controlled.
Maintenance
Plugin health and permissions checks
The plugin and permission tools are there so moderation and server upkeep do not live in different worlds. Use Plugin Health to spot heavy or outdated plugins, and use Group Permissions to review what each group can actually do.
Plugin HealthCheck loaded state, hook time, RAM use, source, and version status from one Rust-specific table.
Group PermissionsReview permission matrices by plugin and group without leaving the same server workspace.
Before wipe or patch dayUse both tools together to clean up heavy plugins, missing permissions, or stale bridge setups before problems show up live.
Aegis