Служебные команды

Команды 102#

/gms
/gmc Steve
/gamemode spectator
/gamemode 1 Steve

/workbench
/craft
/anvil
/grindstone
/stonecutter

/broadcast &6Рестарт через {online} игроков
/bc Техокно
/broadcastworld Только этот мир

/antioch
/antioch holy
/kittycannon
/beezooka 3

/help rg
/rg list

Права 86#

Подробное руководство#

Version: 1.0.4+build.16

Table of Contents#

1. Player Info Commands
2. Nicknames
3. MOTD System
4. Rules System
5. Helpop
6. Suicide
7. Depth
8. Player State Commands
9. Per-Player Time & Weather
10. Server Admin Commands
11. World Interaction
12. Fun Commands
13. Mail

Overview#

Miscellaneous quality-of-life commands covering player info, server admin tools, world/environment manipulation, fun commands, and player state management.

Player Info Commands#

Permissions note: neoessentials.whois is an admin-only node (default: false). Use neoessentials.whois.detailed for detailed diagnostics (IPs, internal flags). neoessentials.ping.others is granted to all players by default.

Nicknames#

Commands#

Permission nodes#

Nickname rules#

• Length: 3–16 characters (after stripping colour codes).
• Characters: a-z A-Z 0-9 _ & # § only.
• Uniqueness: case-insensitive; two players cannot share the same plain-text nick.
• Colour codes: &0–9, &a–f, &k–r, and hex &#RRGGBB are all supported when the player has neoessentials.nick.color.

Storage#

Nicknames are persisted in config/neoessentials/nickname_data.json (UUID → raw nick string with & codes). They are loaded on server start and re-applied to all online players.

MOTD System#

The MOTD (Message of the Day) system supports multiple named profiles, auto-rotation, and web-dashboard management.

Commands#

Color codes#

Use & color codes in MOTD messages (e.g. &aGreen text &cRed text). They are converted to § automatically.

Profiles#

Profiles are persisted through the pluggable DataStore backend (JSON by default — see Storage Backend), across two collections:

• motd_profiles — one record per profile, keyed by profile name, holding motd/author/timestamp
• motd_meta — a single "settings" record holding activeProfile, rotationEnabled, rotationIntervalMinutes, and rotationCurrentIndex

Legacy file: config/neoessentials/motd_data.json (both the multi-profile layout and the older single-MOTD-at-root layout) is only read once, automatically, to migrate its contents into the DataStore collections above the first time the profile collection is empty — it is never written to again afterward.

Dashboard API#

The dashboard exposes /api/motd for full profile management:

Rules System#

The Rules system stores server rules in config/neoessentials/rules_data.json.
Rules are auto-generated with sensible defaults on first startup if no file exists.

Commands#

Color codes#

Use & color codes in rule text (e.g. &cNo griefing). They are converted to § automatically when displayed.

Data file#

Rules are stored in config/neoessentials/rules_data.json:

{
  "rules": [
    "&6Be respectful to all players and staff members",
    "&cNo griefing, stealing, or destroying other players' builds",
    "&eNo spamming in chat or using excessive caps"
  ]
}

Location: config/neoessentials/rules_data.json
Generated automatically: Yes — 10 default rules are written on first start if the file is absent.
Edit in-game: Use /rules add, /rules edit, /rules remove.
Edit on disk: Modify rules_data.json directly, then run /rules reload in-game.

Legacy migration: Servers upgrading from NeoEssentials <1.0.2.6 may have rules.json.
NeoEssentials automatically detects and migrates it to rules_data.json on first load — no manual action needed.

Console feedback#

NeoEssentials logs detailed guidance to the console when rules fail to load:

╔══════════════════════════════════════════════════════╗
║  RULES LOAD ERROR: rules_data.json is corrupt JSON  ║
║  File: config/neoessentials/rules_data.json         ║
║  Error: Unexpected character ...                    ║
║  Fix:  Delete the file and run /rules reload to     ║
║        regenerate defaults, then re-add your rules. ║
╚══════════════════════════════════════════════════════╝

If the file is simply missing, NeoEssentials creates it automatically and logs its absolute path along with quick-start edit instructions.

Dashboard API#

The dashboard exposes /api/rules for full rule management:

All /api/rules endpoints require Bearer-token authentication (same as every other dashboard endpoint).

Helpop#

The /helpop command lets players send requests to online staff. Staff receive them if they have the neoessentials.helpop.receive permission.

Commands#

Permission nodes#

Behaviour#

• Messages are broadcast to all online players who have neoessentials.helpop.receive.
• The sender's name is prefixed in the staff notification (e.g. [HelpOp] PlayerName: message).
• Console operators always receive helpop messages.

Suicide#

Commands#

Behaviour#

1. /suicide displays a confirmation prompt. Players have 10 seconds to type /suicide confirm.
2. If the confirmation window expires, the prompt is silently cancelled.
3. After a successful suicide, a 30-second cooldown prevents spamming.
4. /suicide is blocked in Creative and Spectator modes.
5. Death uses DamageTypes.GENERIC_KILL (does not count as PvP; no attacker credited).

Note: /kill is the vanilla admin command (can target entities). NeoEssentials' /suicide is strictly self-only and is intentionally not aliased to /kill.

Depth#

Shows Y-coordinate information including depth below sea level and height above bedrock.

Commands#

Output#

• Current Y level
• Depth below / height above sea level (Y=63)
• Height above bedrock (Y=−64)
• Layer description (e.g. Deepslate Region, Nether, Diamond Level)

Player State Commands#

Per-Player Time & Weather#

Server Admin Commands#

World Interaction#

Fun Commands#

Mail#

Back to Wiki Home