Minecraft Essentials Ops

Minecraft EssentialsX Operations Skill

Skill Scope

Routing Boundaries

• Use when: the task is EssentialsX command, config, permissions, economy, or moderation operations.
• Do not use when: the task is generic server deployment/proxy/performance architecture (minecraft-server-admin).
• Do not use when: the task is writing Java plugin code (minecraft-plugin-dev).
• Do not use when: the task is WorldEdit selection/build workflows (minecraft-worldedit-ops).

Support Assets

• Read references/permissions-and-rollout-checklists.md when the task is a permissions audit, economy rollout, or moderation-policy change and you need a compact preflight list.

Module Overview and Install Notes

Common EssentialsX modules in production:

• EssentialsX (core commands and user tools)
• EssentialsXChat
• EssentialsXSpawn
• EssentialsXProtect

Operational install checklist:

• Match EssentialsX build to your Paper/Spigot API generation.
• Install Vault if using economy providers or permission/chat bridges.
• Start server once and inspect logs for dependency warnings.
• Keep plugin jar versions documented for rollback.

Version-alignment rule:

• update EssentialsX and companion plugins as a tested batch in staging first.

Vault and Economy Basics

Economy stack model

• EssentialsX can provide economy commands and balances.
• Vault provides a shared bridge so other plugins (shops, jobs, ranks) can read/write balances.

Verify provider chain:

• Server starts without Vault hook errors.
• Economy commands respond without permission errors.
• Third-party plugin transactions affect balances consistently.

Core economy commands

/bal
/baltop
/pay Alex 250
/eco give Alex 1000
/eco take Alex 100
/eco reset Alex

Use admin economy commands through staff roles only.

Shop Pricing and Sign Shops

If using EssentialsX signs and economy interactions:

• Define pricing policy:
• starter-tier prices
• anti-inflation sinks
• admin-only item exceptions
• Enable only the sign types you intend to support in config.yml:

   enabledSigns:
     - buy
     - sell

• Restrict creation permissions to trusted groups:
• essentials.signs.create.buy
• essentials.signs.create.sell
• Grant use permissions only to groups that should transact:
• essentials.signs.use.buy
• essentials.signs.use.sell
• Validate buy/sell math with a non-op player account after config changes.

Sign shop formats

[Buy]
<quantity>
<item>
<price>

[Sell]
<quantity>
<item>
<price>

Example (stone at spawn market):

[Buy]
32
stone
$50

[Sell]
32
stone
$20

Use separate [Buy] and [Sell] signs when you want different buy and sell

prices. Line 4 is a single transaction price for that sign.

Operational guardrails:

• never enable broad player access to unrestricted admin shop signs
• monitor rapid balance spikes for dupes/exploit patterns

Kits, Warps, Homes, Nicknames, Spawn

Kits operations

Typical kit lifecycle:

• create/edit kit definition
• set cooldown and permission
• test with player-rank account

Kit entry in config.yml:

kits:
  starter:
    delay: 86400
    items:
      - stone 64
      - oak_planks 32
      - bread 16

Common commands:

/kit
/kit starter
/createkit starter

Warps and homes

/setwarp spawn
/setwarp market
/warp spawn
/sethome
/home
/delhome

Control limits through permissions and Essentials config values.

Nicknames and spawn management

/setspawn and /spawn require the EssentialsXSpawn module. Confirm the jar is

installed, the startup log has no module-load errors, and player groups have

essentials.spawn before treating a spawn command failure as a location issue.

/nick BuilderOne
/realname BuilderOne
/setspawn
/spawn

Keep nickname policy explicit for moderation and impersonation prevention.

Permissions Patterns

Use a permission manager (for example LuckPerms) to model role tiers.

Suggested role intent:

• admin: full EssentialsX admin + moderation + economy controls
• staff: moderation and support commands, limited economy tools
• player: basic homes/warps/msg/pay with guardrails

Example permission outline:

groups:
  admin:
    permissions:
      - essentials.*
  staff:
    permissions:
      - essentials.kick
      - essentials.mute
      - essentials.tempban
      - essentials.jail
      - essentials.warp
      - essentials.msg
  player:
    permissions:
      - essentials.home
      - essentials.sethome
      - essentials.delhome
      - essentials.spawn
      - essentials.warp
      - essentials.msg
      - essentials.pay

Avoid wildcard permissions outside trusted admin roles.

Moderation Workflows

Workflow: Mute

/mute Alex 30m Chat abuse after warning
/unmute Alex

Practice:

• include reason and duration
• log escalation path for repeat behavior

Troubleshooting: mute not applying → verify essentials.mute permission and that EssentialsXChat is installed for chat filtering.

Workflow: Jail

/setjail intake
/jail Alex intake 20m Griefing spawn edge
/unjail Alex

Practice:

• define clear jail reasons
• pair with rollback/repair actions when relevant

Troubleshooting: jail not working → confirm jail location exists with /setjail intake and player has no bypass permission.

Workflow: Temporary Ban

/tempban Alex 7d Repeated harassment
/banip Alex Severe evasion case
/unban Alex

Practice:

• align durations with policy tiers
• document evidence and staff actor

Troubleshooting: tempban not sticking → check essentials.tempban permission and that no override plugin (e.g., LiteBans) is conflicting.

Config Pitfalls and Hardening Notes

Common pitfalls:

• mismatched EssentialsX/Vault/provider versions after partial plugin updates
• permissive wildcard grants that expose admin economy commands
• high home/warp limits causing navigation abuse or command spam
• inconsistent chat/nickname rules across staff shifts

Hardening checklist:

• keep a tested baseline config backup before edits
• change one policy area at a time (economy, homes, moderation, chat)
• run staff and player smoke tests after every config rollout
• maintain written policy mapping to command permissions

Operations Runbook: Safe Config Rollout

• Backup current Essentials config files.
• Apply targeted config edits.
• Reload only if plugin docs explicitly support live reload for changed sections.
• Prefer maintenance restart for sensitive changes.
• Validate:
• login flow
• homes/warps
• economy transactions
• moderation commands
• Keep rollback bundle ready for immediate restore.

References

• https://essentialsx.net/wiki/Home.html
• https://essentialsx.net/commands
• https://essentialsx.net/permissions
• https://essentialsx.net/wiki/Module-breakdown.html
• https://essentialsx.net/wiki/Configuration-file.html
• https://essentialsx.net/wiki/Sign-Tutorial.html
• https://www.spigotmc.org/resources/vault.34315/