Freeze, warn, mute, kick and ban
Common actions are available from a consistent moderation system.
A complete moderation workspace built around fast, informed action.
Full overview
StaffCore brings routine moderation actions and player context into one workspace. Staff can move from a report to a profile, evidence, notes and punishment history without relying on disconnected commands or external spreadsheets.
The aim is faster action with better consistency: important information remains attached to the player so different moderators can understand what happened before making a decision.
How it works
Staff mode and player profiles provide the context needed during an investigation. Notes, historical actions, inventory snapshots and alt information help moderators gather evidence before issuing a punishment.
Freeze, warn, mute, kick and ban actions can use structured reasons and punishment ladders. Discord webhooks create an external record for staff review and accountability.
Administration
Permissions separate staff capabilities, while configurable ladders and webhook destinations adapt the system to the server team. The project is private and designed around GhoulCraft's moderation workflow.
Feature breakdown
Each headline feature is expanded below so visitors can understand the real server use rather than seeing a short tag list.
Common actions are available from a consistent moderation system.
Prepare moderators with the tools and visibility needed during investigations.
Keep useful context attached to the player for the whole team.
Review prior actions before deciding on escalation.
Capture evidence about a player's items at important moments.
Support repeat-offender decisions and structured punishment progression.
Getting started
This project is not currently offered as a public platform download; its page documents the system and development status.
Private deployment is configured around the staff permission structure.
Punishment ladders, reason prompts and webhook channels are reviewed with the moderation team.
Staff actions are tested using non-production accounts.
Access is limited to the minimum permission level required for each role.
Related projects