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).

References

• 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

Platform gate

Use EssentialsX only on a supported Paper or Spigot server build. EssentialsX 2.22.0 warns that Folia and Folia forks are unsupported and can lose userdata; it also does not support Forge, NeoForge, or Fabric Bukkit-hybrid servers. If the current platform is in either category, stop before enabling or configuring EssentialsX and verify a supported operational path. This guide does not recommend a migration.

Common EssentialsX modules in production:

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

Operational install checklist:

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

Version-alignment rule:

• update EssentialsX and companion plugins as a tested batch in staging first.
• verify the exact EssentialsX release or development build supports the target Paper release; do not assume a build for 26.1 also supports 26.2.

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:

1. Server starts without Vault hook errors.
2. Economy commands respond without permission errors.
3. 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:

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

   enabledSigns:
     - buy
     - sell

3. Restrict creation permissions to trusted groups:
   • essentials.signs.create.buy
   • essentials.signs.create.sell
4. Grant use permissions only to groups that should transact:
   • essentials.signs.use.buy
   • essentials.signs.use.sell
5. 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:

1. create/edit kit definition
2. set cooldown and permission
3. test with player-rank account

Kit entry in plugins/Essentials/kits.yml:

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

Common commands:

/kit
/kit starter
/createkit starter 86400

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.