Moderation

Commands 42#

/banip 203.0.113.10 griefing
/banlist ips
/tempbanip 203.0.113.20 2h proxy
/unbanip 203.0.113.10

/tempban Steve 30m cheating
/banlist
/modhistory Steve
/unban Steve

/setjail spawn
/jail Steve spawn 2h griefing
/jailfor Alex spawn 30m
/jaillist
/jailinfo spawn

/vanish
/vanishlist
/unvanish

/mute Steve 1h spam in chat
/mutelist
/modhistory Steve
/unmute Steve

Permissions 41#

Detailed guide#

Version: 1.0.5+build.54 · Config: config.json → moderation / storage sections

Overview#

Comprehensive player moderation — ban, temp-ban, IP ban, kick, mute (with IP mutes), jail (timed), freeze, vanish, warnings, staff notes, and player reports — all with persistent storage, full history/audit trails, permission integration, and event enforcement.

Bans, mutes, kicks, warnings, notes, and reports are backed by a single canonical store per feature (see Storage Backend below) — there is exactly one code path that enforces each punishment, and the Web Dashboard's moderation API reads and writes through the same managers, so in-game commands and dashboard actions always agree.

Bans#

Commands#

Duration format: 30s · 5m · 2h · 1d · 1w

History & Audit Trail#

Every ban (player and IP) is stored with a unique ID, an active flag, optional evidence, and — once lifted — who unbanned it and when (unbannedBy / unbannedAt). Expired temp-bans are archived the same way (auto-marked inactive, no "unbanned by" staff member). Unbanning and re-banning a player never destroys their prior ban records; they remain queryable as history via the dashboard's /api/moderation/bans/{uuid} and /api/moderation/ipbans routes (see Web Dashboard).

Moderation History#

Kicks#

Every kick (including dashboard-initiated kicks) is recorded with a timestamp, reason, and issuing staff member, and is queryable as history via the dashboard's /api/moderation/kicks / /api/moderation/kicks/{name} routes — there is no in-game command to view kick history.

Mutes#

Muted players cannot chat, send private messages, or send mail. The mute system is implemented in the chat module (com.zerog.neoessentials.chat), not the moderation module — all three commands share the single neoessentials.chat.mute permission (there's no separate exempt/list/unmute node), plus neoessentials.chat.mute.exempt to make a player un-mutable.

⚠️ Unlike every other moderation command, /mute//unmute//mutelist have no root permission gate at registration — neoessentials.chat.mute is only checked deep inside the command body, not at the point Brigadier registers the command. This means all three are visible to every player in /help and can be attempted by anyone, though the body-level check should still reject an unauthorized caller — worth verifying directly if you rely on this restriction, rather than assuming registration-time enforcement like most other commands.

Like bans, every mute tracks reason, issuing staff member, an active flag, and — once lifted — unmutedBy / unmutedAt, with full history preserved. IP mutes are also supported (mute an IP directly rather than a player name) — currently exposed via the dashboard's /api/moderation/ipmute / /api/moderation/ipmutes routes rather than an in-game command.

Jail#

Jail teleports the player to a set jail location and blocks movement, interaction, combat, and teleport until released.

Commands#

Jail Region Shapes#

A jail location can be either a sphere (radius around a point) or a cuboid (two-corner box):

• /setjail <name> — auto-detects: uses a wand or WorldEdit cuboid selection if one is active, otherwise falls back to a sphere at your current position using moderation.jailSettings.defaultSphereRadius.
• /setjail <name> sphere <radius> — explicit sphere at your current position.
• /setjail <name> cuboid — cuboid from the current wand/WorldEdit selection.
• /jailwand gives an item (configurable via moderation.jailSettings.wandItem) — right-click sets corner 1, left-click sets corner 2, then run /setjail <name> cuboid.

Jail Enforcement#

While jailed, the following are blocked: - Movement outside jail radius - Teleport commands (redirected back to jail on respawn too) - Breaking/placing blocks (unless neoessentials.jail.allow-break / allow-place) - Interactions (unless neoessentials.jail.allow-interact) - Attacking entities (unless neoessentials.jail.allow-attack)

Timed jails auto-release when the duration expires (checked every second and on login). Durations use s, m, h, d, or w, for example /jail Steve spawn-jail 2h griefing.

Freeze#

Vanish#

Broadcasting vanish toggles to staff/everyone and console logging are all config-driven (moderation.vanishSettings.broadcastToStaffVanish, etc. — see below).

Warnings#

Warnings persist for offline players and are shown with a truncated ID, timestamp, reason, and issuing staff member.

Staff Notes#

Freeform notes staff can leave on a player's record — for context that isn't a punishment (e.g. "watch this player, borderline behavior last week").

Notes persist for offline players and record author, timestamp, and text. Also available via the dashboard's /api/moderation/notes/{name} and /api/moderation/note routes.

Player Reports#

Lets players flag misbehavior even while no staff are online — reports persist and show up in the review queue whenever staff next check.

Submitting a report also immediately notifies any online staff with neoessentials.moderation.reports, in addition to persisting for later review. Reports track reporter, target, reason, timestamp, and status (PENDING / REVIEWED / DISMISSED) plus who reviewed it and when. Also available via the dashboard's /api/moderation/reports, /api/moderation/reports/all, /api/moderation/reports/{id}, and /api/moderation/reports/{id}/review routes.

Data Files & Storage Backend#

Bans, mutes (including IP mutes), kicks, warnings, notes, and reports are persisted through a pluggable DataStore abstraction rather than bespoke JSON files — configured under config.json → storage:

"storage": {
  "type": "json",
  "autoMigrate": true,
  "sqlite": { "file": "data.db" },
  "mysql": { "host": "localhost", "port": 3306, "database": "neoessentials", "username": "neoessentials", "password": "", "useSSL": false, "poolSize": 10 }
}

Each punishment type is one collection (a schema-less table of JSON documents keyed by ID):

With the default json backend, collections live at neoessentials/store/<collection>.json. With yaml, neoessentials/store/<collection>.yml. With sqlite, all collections live as tables in neoessentials/store/data.db. With mysql, all collections live as tables in the configured database. If MySQL is unreachable at boot, the mod automatically falls back to the JSON backend rather than failing to start.

As of this release, storage.type covers the entire mod, not just moderation — economy, homes/warps/spawn, kits, chat (AFK/ignore/chat-format), holograms, shops, permissions (including group inheritance), the dashboard's own accounts, and the Auction House are all backed by the same DataStore system now. See Storage Backend for the complete collection list and per-system breakdown.

Config (config.json → moderation)#

Settings are nested under per-feature sub-objects, not flat keys directly under moderation.

moderation.banSettings#

moderation.kickSettings#

moderation.freezeSettings#

moderation.vanishSettings#

moderation.jailSettings#

Notes & Reports Permissions#

Back to Wiki Home