Skip to main content
Spawners are declared in Mobs/ — a spot in a world that keeps a population of one mob alive around itself. These commands place them, inspect them and switch them on and off. Alias: /nme spawners Permission: nmentities.spawner (one permission for all of them — it’s one job, not nine unrelated powers)

Inspecting

The status shown by list and info is the half of a spawner that isn’t in its config file:

Placing and removing

remove refuses to edit a file that also declares mobs — saving that YAML back would eat its comments — and names the path for you to delete by hand instead.

Driving

<target> on enable, disable and reset is a spawner id, a group name, or the literal all.
Use all, not *. Brigadier rejects * in an unquoted argument.

Examples

Notes

  • Every mutating command goes through the same path the addon API uses, so a plugin and an admin have identical effects — including the on/off decision surviving a restart, which is stored in spawner-state.yml.
  • Only “an admin switched this off” persists. Cooldowns, warmups and live counts are runtime state and start fresh.
  • trigger reports afterwards: on Folia the spawn happens on the region owning the spawner, so what came out is only known once it has.