- Home
- Skills
- Game Development
- Moderation Console for Online Games
Moderation Console for Online Games
Staff tools for multiplayer games that are least-privilege, audited, fair on appeal and tested against abuse.
$7
Works with the AI Agents you already use
Moderation Console for Online Games
Example session with this skill installed
Build a moderation spec for a survival game. I need separate powers for teleporting and banning, a reason-code list for griefing, and an escalation ladder that starts with a 24-hour ban.
- Read your context and instructions
- Compiled the moderation console
I have generated the moderation specification and server-side logic for your survival game. The system enforces least-privilege access and mandatory audit logging for all staff actions.
Moderation System Specification
1. Staff Power Flags
| Power | Flag Name | Description |
|---|---|---|
| Teleport | can_summon | Move any player to staff location or vice versa. |
| Ban | can_game_ban | Disconnect player and prevent future authentication. |
| Observe | is_invisible | Remove staff from synced state, physics, and sounds. |
2. Griefing Reason Codes
{
"G01": "Griefing: Resource Blocking",
"G02": "Griefing: Intentional Team Killing",
"G03": "Griefing: Asset Destruction",
"G04": "Griefing: Spawn Camping"
}
3. Escalation Ladder (Data-Driven)
| Violation Count | Base Action | Duration | Multiplier (Repeat) |
|---|---|---|---|
| 1st Offense | Area Ban | 24 Hours | 1.0x |
| 2nd Offense | Game Ban | 72 Hours | 2.0x |
| 3rd Offense | Game Ban | 7 Days | 3.0x |
| Aggravated | Game Ban | Permanent | N/A |
4. Server Audit Handler
async function handleBanRequest(staffId, targetId, reasonCode, note) {
const staff = await db.accounts.get(staffId);
if (!staff.powers.has('can_game_ban')) {
logSecurityViolation(staffId, 'unauthorized_ban_attempt');
throw new Error('Access Denied');
}
const ladderLevel = await getPlayerViolationCount(targetId);
const duration = calculateBanDuration('G01', ladderLevel);
await db.auditLog.create({
actor: staffId,
action: 'GAME_BAN',
target: targetId,
reason: reasonCode,
expires: Date.now() + duration
});
return executeBan(targetId, duration);
}
Next steps
- Review
templates/policy.mdto adjust the 24-hour base duration for different reason codes. - Run the generated
tests/security/moderation_leak.test.tsto verify invisible mode. - Hook the
handleBanRequestto your staff UI panel.
Connects securely to your tools. The creator never sees your data.
About this skill
Moderating multiplayer games often devolves into giving staff "god mode" or banning players without context. This skill builds a server-authoritative moderation system focused on audit trails, evidence-backed reporting, and fair escalation.
What it does
- Staff Power Isolation: Converts moderator capabilities into granular server-side flags to prevent privilege creep.
- Evidence-Backed Reporting: Builds a report flow that automatically attaches chat logs, area entry logs, and ledger slices.
- Escalation Logic: Implements a data-driven "warn-to-ban" ladder with multipliers based on player history.
- Invisible Observation: Implements stealth modes that remove staff from synced state, preventing detection via client-side hacks.
- Audited Restitution: Provides idempotent item return tools that move assets back along the ledger without full database rollbacks.
How it works
- Infrastructure Audit: Analyzes your existing networking and storage code to fit current architectural patterns.
- Policy Definition: Establishes reason codes, ban lengths, and escalation multipliers in a
policy.mdtemplate. - Server Implementation: Generates the message handlers for staff powers, record queries, and the audit log system.
- Security Hardening: Executes attack tests to ensure normal clients cannot trigger staff messages or detect invisible moderators.
Frameworks & tools
Designed for server-authoritative game engines and backends including Unity Dedicated Servers, Unreal Engine, Colyseus, Nakama, and Roblox. Works with any stack that supports server-side validation and persistent storage.
Why this beats prompting it yourself
Generic prompts often miss the nuances of state synchronization that leak "invisible" moderators to cheaters. This skill enforces strict least-privilege architecture and ensures every punishment is tied to a mandatory reason code and audit row out of the box.
Use cases
- Designing a "warn-to-ban" escalation ladder for a new MMO.
- Building a staff console that shows player purchase history before allowing a ban.
- Implementing audited admin commands for community managers.
- Writing security tests to verify that banned accounts cannot trade or re-join areas.
Known limitations
Does not define legal privacy policies. Developers must manually set retention periods for personal data in accordance with local laws. Requires an existing server-authoritative architecture.
Requires server-authoritative architecture. Does not generate legal privacy policy text. Policy numbers for ban lengths must be finalized by the developer.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 7 days ago