Spawners

Trust and protection

Owners, trusted players, staff access, ownerless spawners, and the claim and region plugins asked through ExyliaLib build zones.

Two checks guard every spawner, and both must allow an action: the spawner's own owner and trusted players, and the claim and region plugins of the server.

Owners

Whoever places a spawner owns it. The owner:

opens, mines and stacks it, and cleanses it when it corrupts;
is paid for every sale of its storage, whoever sells (see Who gets paid);
gets the corruption notices, and is the player whose global boosts apply to it;
is the only one, besides staff, who decides who else is trusted.

Trusted players

The Trusted players card of the hub opens the trust list: every trusted player with the date they were added. Trust a player asks for a name; right-clicking a player on the list stops trusting them, after a confirmation. The same from chat, looking at the spawner (within six blocks):

Command	Does
`/spawners trust <player>`	Trusts that player on the spawner you look at.
`/spawners untrust <player>`	Stops trusting them.

The name must belong to a player who is online or has played on the server. Only the owner and staff can change the list; trusted players see it read-only.

A trusted player can open the spawner, take from and sell its storage (the money still goes to the owner), buy upgrades with their own money, insert boosters, stack, mine and cleanse it. The list is kept per spawner in the database and goes away with the last spawner of the stack.

Staff

Players with exyliaspawners.admin pass the trust check on every spawner: they can open, mine and stack any of them. They still need the claim plugins to allow it.

Ownerless spawners

A vanilla spawner converted on first touch, and a spawner brought in by an import that kept no owner, has no owner. Until it gets one, anyone the claim plugins allow can open, mine and sell it, and its sales pay the player who sells. The first player to stack a spawner onto it or change it with a spawn egg becomes its owner.

Imported spawners

SmartSpawner, WildStacker and RoseStacker keep no owner, so every spawner imported from them starts ownerless. In a claim, the claim plugin still decides who may touch it; in the wild, claim the important ones by stacking onto them. See Importing.

Claims and regions

Before a spawner is placed, mined, stacked or opened, ExyliaSpawners asks the region and claim plugins through ExyliaLib's build zones:

Action	Asked as
Placing a spawner	building
Stacking onto one	building
Mining it	breaking
Opening it (and selling with a wand, cleansing)	opening a container

protection:
  enabled: true
  sources:
  - WORLDGUARD
  - EXYLIA_REGIONS
  - EXYLIA_PROTECTIONS
  - LANDS
  - GRIEF_PREVENTION
  - TOWNY
  - SUPERIOR_SKYBLOCK

Source	Denies when
`WORLDGUARD`	WorldGuard's own build test with the action's flag says no.
`EXYLIA_REGIONS`	An ExyliaLib region declares `build`, `break` or `interact: false`.
`EXYLIA_PROTECTIONS`	An ExyliaProtections protection lacks the player's permission.
`LANDS`	The player's role in a Lands area lacks the action's flag.
`GRIEF_PREVENTION`	A claim lacks the player's build, container or access trust.
`TOWNY`	Towny's build, destroy or switch permission says no.
`SUPERIOR_SKYBLOCK`	A SuperiorSkyblock2 island lacks the player's privilege.

A source that is not installed always allows; an unknown name in the list is ignored. protection.enabled: false stops asking any of them, leaving only the owner and trust check.

Something missing on this page? Tell us on Discord