Configuration

blacklist

Worlds a player cannot /sethome in. HomeService.set checks the player's current world name against this list before doing anything else (before the SetHomeEvent, before the home-limit check) and, if present, aborts and sends HOME_BLACKLISTED_WORLD — the home is neither created nor updated. It only gates setting a home; it does not stop a player from teleporting to an existing home located in a now-blacklisted world. Shipped default blocks the spawn world only. See Homes.

warmup

A permission → Duration map, parsed by AstralCore's DurationTypeSerializer/DurationParser (y, d, h, m, s, ms units, combinable — e.g. "1d 5h"). MainConfiguration.warmup(Player) walks the map entries and, for each permission the player holds, replaces the running value with the entry's duration only if it is strictly lower than the current running value — the running value starts at a hardcoded 3s. In practice this means:

• A player matching no configured permission gets the 3s hardcoded fallback.

• astralhomes.mvp: 0s always wins when held, since 0s is lower than everything else.

• A configured duration greater than the 3s fallback can never be applied on its own. With the shipped defaults, a player holding only astralhomes.default (5s) is not granted 5s — the loop only lowers the running value, so it never rises off the 3s starting point, and the result is identical to holding no warmup permission at all. This is a real quirk of MainConfiguration.warmup(), not a documentation simplification — raising a permission's warmup above 3 seconds by editing this map alone has no effect unless every lower entry is also removed or raised.

The resolved duration is applied by the shared WarmupService (action-bar progress display, cancelled on movement/disconnect) before /home teleports, /warp, /spawn, and /back. Accepted /tpa//tpahere requests teleport immediately and are not subject to this warmup — see Teleport Requests.

limits

A permission → int map. MainConfiguration.limit(Player) walks the map and keeps the highest limit among the permissions the player holds, falling back to 1 if none match. HomeService.set enforces this only when creating a new home (renaming/overwriting an existing home by name is never blocked by the limit) — once data.homes().size() reaches the resolved limit, the player is sent HOME_LIMIT_REACHED with the %limit% placeholder and the home is not created.

worlds-permissions

World name → permission node. Used exclusively by TeleportationRequestService to gate /tpa and /tpahere: when a request's target player is standing in a world present in this map, the sending player must hold the mapped permission, or the request is rejected with WORLD_PROTECTED (checked both for local same-server targets in doPreFlightCheck and for cross-server targets, where the recipient's server reports its world's permission back over the messaging exchange). Shipped defaults protect world_nether (worlds.nether) and world_the_end (worlds.end). See Teleport Requests.

restore-location-on-join-groups

Server groups (AstralPaperAPI.serverInformation().group()) in which HomeSnapshotAdapter.apply restores a player's last known location on join, provided the player wasn't already teleported on join by the teleportation service. The stored location itself is keyed per specific server (serverId:world, set by HomeSnapshotAdapter.unload on quit via HomePlayerData.setLastServerLocation), not per group — so a match requires rejoining that exact server instance in that exact world, with restoration only enabled at all when that server's group is listed here. The restore only happens if the stored location passes LocationUtils.isSafeLocation. Shipped default enables this for the construction and resource groups.