Skip to main content
Ordinary homes, warps and teleport plugins break on a sharded world. They teleport with Player#teleport, which cannot reach another server; they keep data in files on one server, which the player leaves at the next border; and they look players up in the local player list, which only holds the people on this shard. Atlas ships four that do it properly. Each is its own jar and needs nothing but Atlas.

Installing

Put the jars you want in plugins/ on every shard, next to atlas-paper.jar, and restart. Not on the proxy and not on the hub. Every shard needs them, because a command can be typed on any shard and the far end of it — the shard a home is on, the shard the player you asked to teleport to is on — has to run its half. Each writes a config.yml on first start with every setting commented. Messages are MiniMessage, and setting one to "" silences it.

What they have in common

One command, any distance

Every teleport is an Atlas transfer: a local teleport when the destination is on this shard, a seamless handoff when it is on another one, in this geo or another.

State that follows the player

Homes, /back, pending requests and cooldowns ride in the player’s own record, so they are the same on every shard and cannot be reset by crossing a border.

Safe landing

Before sending a player to a saved spot, the shard that owns it checks for solid ground and moves them to the nearest safe block. A spot that has been dug out is refused instead of suffocating someone.

Warmups and cooldowns

Configurable per plugin. A warmup is cancelled by moving a block or taking damage. Ops bypass both by default.

AtlasHomes

Homes are stored in the player’s record, not on a server. A home set in region 0 works from region 3, or from a shard in another geo. /home with no name goes to the home called home, or to the only home if there is one; otherwise it lists them. /homes lists them as clickable names.

AtlasRTP

/rtp picks a random point in a ring around a centre, anywhere on the grid, and asks the shard that owns it whether there is somewhere to stand. That shard loads the chunk without stalling, finds the surface, and refuses water, lava, and any biome on the avoid list. Only a point that passes is used; a failed one costs a few milliseconds and the next is tried.
Random teleport generates terrain wherever it lands that has not been generated yet. Pre-generating each region with /shard pregen keeps that off your players.

AtlasTeleport

A teleport request is delivered to whichever shard the target is on. It stays with the target until it expires, so if they walk over a border before answering, /tpaccept still works where they end up.
  • /tpa <player> — accepting it summons you from wherever you are to wherever they are.
  • /tpahere <player> — accepting it sends them to wherever you are at that moment.
  • /tpaccept and /tpdeny take an optional name when several are pending; the chat message has clickable buttons.
  • /tptoggle turns incoming requests off.
  • /back returns to where you were before your last teleport — by any plugin, local or cross-shard — or where you died. In the hub, /back is the proxy’s instead: it sends you back into the world.
  • /tp <player> [target], /tphere <player> and /tppos <x> <y> <z> [world] are for staff (atlas.teleport.admin) and find players on any shard. /tp replaces the vanilla command, which cannot see players on other shards; vanilla’s is still minecraft:tp.

AtlasWarps

Warps and the spawn are stored once, in the network’s database. Setting one on any shard makes it exist on every shard straight away, and every shard also refreshes on its own each minute.

Permissions

Writing your own

The four are small, and they are meant to be read. They live under plugins/ in the Atlas repository and use only the plugin API: transfer and summon to move players, locate to find them, safeLanding to check a destination, arrival actions to say something once the player has landed, player data adapters for state that travels, and store().documents(...) for data the whole network shares.