Repository navigation
Spawner filters
OfficialRell edited this page Oct 14, 2026
·
8 revisions
- Spawner filters let you target specific spawners and apply different configuration values to them.
- They are useful when you want one setup for one group of spawners and a different setup for another group.
- Filters are defined in
settings.ymlfile under theFilterssection. - A filter only matches when all of its enabled conditions are true.
- Each filter has a priority value, higher priority is checked first.
- If multiple filters could match, the one with the highest priority is used.
- If no custom filter matches, the plugin falls back to
DEFAULTvalue. - Filters with no valid conditions are ignored.
-
priority- filter priority (0 if unset). -
worlds- list of world names the filter will apply to. -
worlds-exclude- list of world names the filter will not apply to. -
natural:-
trueto apply only to natural spawners. -
falseto apply only to player owned spawners.
-
-
types- list of spawner types the filter will apply to. -
types-exclude- list of spawner types the filter will not apply to. -
stack:- checks the spawner stack size.
- supported operators:
=,!=,>,<,>=,<=. - example:
stack: '>15' # only apply to spawners with stack size greater than 15-
tags:- list of spawner tags the filter will apply to.
-
#anymeans any tagged spawner.
-
tags-exclude:- list of spawner tags the filter will not apply to.
-
#anymeans exclude all tagged spawners.
-
metadata:- list of metadata keys the filter will apply to.
-
#anymeans any spawner that has metadata.
-
metadata-exclude:- list of metadata keys the filter will not apply to.
-
#anymeans exclude all spawners that have metadata.
-
upgrade-level:- checks total upgrade level with a comparison.
- supported operators:
=,!=,>,<,>=,<=. - example:
upgrade-level: '>=5' # only apply to spawners with total upgrade level greater than or equal to 5- upgrades.:
- checks individual upgrade levels with comparisons.
- upgrades:
range,delay,amount, 'nearby',xpanddrops. - supported operators:
=,!=,>,<,>=,<=. - example:
upgrades:
delay: '<3' # less than 3
amount: '!=2' # not 2-
sub-filters:- list of spawner filters.
- applies the filter only if any of the sub-filters match.
- this mostly should be used to group other filters for easier use.
- example:
Filters:
FRIENDLY:
sub-filters: [COW, PIG, SHEEP, ...]
HOSTILE:
sub-filters: [ZOMBIE, SKELETON, CREEPER, ...]Plugin already has all the spawner types as built-in filters (See types here).
UNIQUE - only unique spawners (EMPTY, ARMOR_STAND, BOAT, CHEST_BOAT, ENDER_DRAGON, EXPERIENCE_BOTTLE, EXPERIENCE_ORB, GIANT, MINECART, MINECART_CHEST, MINECART_COMMAND, MINECART_FURNACE, MINECART_HOPPER, MINECART_SPAWNER, MINECART_TNT, ITEM).
REGULAR - all types except unique ones.
- Use either include or exclude for the same category (
typesvstypes-exclude, etc.), not both together. - Names and keys should match exactly (world names, type names, metadata keys, tag names).
- Keep filter names clear and unique so they are easier to manage.
- Start with broader filters and give very specific filters a higher priority.
- If a filter is not working, first check spelling, operator format, and whether the condition values exist in your server setup.