# Minecraft Essentials Ops

> Operate EssentialsX on Minecraft 26.x and 1.21.x servers, including configuration, permissions, economy, kits, warps, homes, and moderation. Use for EssentialsX administration, not plugin development or general server deployment.

- Skill: `gabrielmoreira/minecraft-essentials-ops` (Agent Skill)
- Install (CLI): `npx skillmds@latest add gabrielmoreira/minecraft-essentials-ops`
- Raw SKILL.md: https://api.skillmd.com/api/skills/gabrielmoreira/minecraft-essentials-ops/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: gabrielmoreira (https://skillmd.com/u/gabrielmoreira)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/gabrielmoreira/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

### 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

```text
/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`:
   ```yaml
   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`:
```yaml
kits:
  starter:
    delay: 86400
    items:
      - stone 64
      - oak_planks 32
      - bread 16
```

Common commands:

```text
/kit
/kit starter
/createkit starter 86400
```

### Warps and homes

```text
/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.

```text
/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:

```yaml
groups:
  admin:
    permissions:
      - essentials.*
  staff:
    permissions:
      - essentials.kick
      - essentials.mute
      - essentials.tempban
      - essentials.togglejail
      - 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

```text
/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 the EssentialsX core module loaded,
the actor has `essentials.mute`, the target has no mute-exempt state, and no
other moderation or chat plugin is overriding the result. EssentialsXChat
formats chat; it is not a prerequisite for core mute enforcement.

## Workflow: Jail

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

Practice:
- define clear jail reasons
- pair with rollback/repair actions when relevant
- grant `essentials.setjail` only to roles authorized to create or move jail
  locations; staff who only need to jail or unjail players use
  `essentials.togglejail`

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

## Workflow: Temporary Ban

```text
/tempban Alex 7d Repeated harassment
/unban Alex
```

Practice:
- align durations with policy tiers
- document evidence and staff actor

IP bans are separate: `/banip Alex <reason>` resolves the player's last IP and
can affect other players sharing it. Undo an authorized IP ban with
`/unbanip <address>` using the exact banned address; `/unban Alex` only removes
the account ban.

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

1. Backup current Essentials config files.
2. Apply targeted config edits.
3. Reload only if plugin docs explicitly support live reload for changed sections.
4. Prefer maintenance restart for sensitive changes.
5. Validate:
   - login flow
   - homes/warps
   - economy transactions
   - moderation commands
6. 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/modules
- https://essentialsx.net/wiki/Module-breakdown.html
- https://essentialsx.net/wiki/Configuration-file.html
- https://essentialsx.net/wiki/Sign-Tutorial.html
- https://github.com/EssentialsX/Essentials/discussions/6552
- https://www.spigotmc.org/resources/vault.34315/