Spawn Rule Commands - Lode Entities

Natural spawn rules are the type: spawn entries in Mobs/ — mobs appearing where the world suits them, rather than at a placed spawner. These commands inspect them, test them and switch them on and off. Aliases: /le spawnrules, /le naturalspawn Permission: lodeentities.spawnrule

Inspecting

Command	What it does
`/le spawnrule list`	Every loaded rule and what it currently has alive.
`/le spawnrule info <rule>`	One rule in full: what it spawns, where it may, and its caps.
`/le spawnrule test [rule]`	Whether each rule would spawn where you’re standing, and why not. `[rule]` narrows it to one. Player-only.

test is the important one. A compiled condition can’t be taken apart to name the clause that failed, so the report gives the verdict per rule plus the caps — which is what separates “your condition is wrong” from “you’re at the cap”.

Driving

Command	What it does
`/le spawnrule trigger <rule>`	Spawns a rule’s pack where you’re standing, ignoring its `rate`. Conditions and caps still apply. Player-only.
`/le spawnrule enable <target>`	Switches a rule, or all of them, back on.
`/le spawnrule disable <target>`	Switches it off. Remembered across restarts.
`/le spawnrule reset <target> [kill]`	Forgets a rule’s tracked mobs. `[kill] true` also removes them.

<target> is a rule id or the literal all.

Examples

/le spawnrule list
/le spawnrule info taiga_alpha
/le spawnrule test
/le spawnrule test taiga_alpha
/le spawnrule trigger taiga_alpha
/le spawnrule disable all
/le spawnrule reset taiga_alpha true

Notes

A rule whose cond: fails to parse loads disabled rather than being skipped: a gate that silently disappeared would spawn mobs exactly where the config said not to. /le spawnrule info and /le debug "Spawn rules" both say so.
Enable/disable decisions are stored in spawnrule-state.yml and survive a restart. Live counts do not.
The same operations are available to addons — see Natural Spawns in the API section, including explain(location), which returns exactly what test prints.