Permissions

AtlasRealms declares four permission nodes. The player command branch (/realm, /realm create, /realm bank, and so on) needs no permission at all — anyone can run it.

Admin access

`atlasrealms.command.realm.admin`

Default: op.

Access to the whole /realm admin … branch: reload, status, purge, and every realm, world, template and theme command. In a development build it also gates /realm bench.

Building in a realm

`atlasrealms.build.bypass`

Default: op.

Build in any realm, whatever access level you hold there — the checks that would otherwise refuse a visitor or a resident are skipped. It also lets the holder act on realm ground whose record has not finished loading yet, which is normally refused.

Border and member size

`atlasrealms.realm.size` and `atlasrealms.member.size`

Default: false for both. These two are parents only — grant a numbered child instead:

atlasrealms.realm.size.<n> — for example atlasrealms.realm.size.500.
atlasrealms.member.size.<n> — for example atlasrealms.member.size.10.

If a player holds more than one numbered node under a prefix, the largest number wins. Holding no node at all leaves realm.default-size / realm.default-member-size from config.yml in charge.

What the winning number does depends on the matching upgrade ladder in config.yml:

economy.border.step: 0 (the default) — the node sets the realm’s border outright the moment the owner enters. A rank that shrinks, shrinks the realm.
economy.border.step above 0 — the node becomes a ceiling. The owner still has to buy up to it out of the realm bank; see The bank & upgrades.

atlasrealms.member.size.<n> works the same way against economy.members.step.

No wildcard nodes are declared for either prefix. There is no atlasrealms.command.realm node — the player command tree carries no permission check at all.