Whitelist, trust & ownership

Ownership

A spawner belongs to whoever placed it. One with no owner — a dungeon or fortress spawner AtlasSpawner has taken over via natural.manage — is “natural” instead, and is governed by ownership.rights.natural rather than by an owner.

ownership.limit in config.yml caps how many spawners a player may own across every server sharing the database (world baseline default: 100, raised by the largest atlasspawner.limit.owned.<key> a player holds). ownership.chunk-limit (default 0, off) additionally caps spawners per chunk — this limits placement, not production.

Per-spawner whitelist

Each spawner has its own list of players allowed to use it, capped by whitelist.limit (world default 10, raised by atlasspawner.limit.whitelist.<key>). Manage it with:

• /atlasspawner whitelist — opens the whitelist menu for the spawner you are looking at.
• /atlasspawner whitelist add <player> / whitelist remove <player> — add or remove one name.

A newly added player is granted whitelist.default-actions (default [OPEN, COLLECT]) — not every right, unless you change that list.

Bulk trust

/atlasspawner trust add <player> grants a player access to every spawner you currently own in one command, instead of whitelisting them one spawner at a time. /atlasspawner trust remove <player> revokes it the same way. What a trusted player is granted comes from ownership.rights.trusted in config.yml, not from whitelist.default-actions — by default this grants every right.

How a right is resolved

Whenever a player does something to a spawner — break, stack, change (spawn egg), upgrade, open, collect, or sell — AtlasSpawner asks, in order, and stops at the first answer:

1. atlasspawner.bypass (or atlasspawner.bypass.<action>) — always allowed.
2. No owner — governed by ownership.rights.natural.<action> (all true by default).
3. The player is the owner — always allowed.
4. A grant on this specific spawner — the spawner’s own whitelist (which is what /atlasspawner trust writes in bulk) answers exactly what it was given, nothing more and nothing less.
5. The land’s team role — only if teams.enabled and a team plugin is installed; the player’s role on that island or town (OWNER, MEMBER, COOP, VISITOR, or the land plugin’s own role name) is checked against teams.roles in config.yml. Team rights only ever add to what the spawner’s own whitelist already allows.
6. Otherwise — ownership.rights.stranger.<action> (all false by default).

Returns

When teams.return-on-leave is true (the default) and a player leaves an island or town — by leaving, being kicked, or the island/town being disbanded — every spawner they own on that land is lifted and set aside rather than left to whoever takes the land over. The player gets it back through /atlasspawner returns. Leaving a team does not affect spawners you own elsewhere, only the ones on that specific land.