SafeRTP

WHY SAFERTP

• There is a way back. One command undoes the last teleport, with its own cooldown. Players stop losing the base they forgot to set a home at
• Nobody lands on top of spawn. Destinations are drawn from a ring between a minimum and a maximum radius, sampled evenly by area, so arrivals spread out instead of clustering near the middle
• Nobody lands in lava or in the sea. The destination is checked before the player gets there, and you can whitelist or blacklist biomes per world on top of that
• The server does not freeze while it looks. Chunk loading, the biome check and the safety scan all happen off the main thread, so a busy server does not stutter every time somebody runs the command
• Cooldowns can follow your ranks. A permission sets the wait, the lowest one wins, and one of them removes it entirely

WHAT YOU GET

• Safe destinations — checked before arrival, never inside lava, water or a wall
• Ring distribution — minimum and maximum radius per world, sampled so the whole ring is used evenly
• The back command — undoes the last teleport, with a lifetime and a cooldown of its own
• Biome filters — a whitelist or a blacklist of biomes, set per world
• Warmup countdown — cancels if the player moves or takes damage, so it cannot be used to escape a fight
• Tiered cooldowns — set by permission, lowest wins, and a node for no cooldown at all
• Optional cost — charge for a teleport through Vault, with a different price per world and a bypass permission
• Per-world access — a permission node per world, so the nether can be off limits until you say so
• Discovery titles — an optional title or broadcast the first time a player reaches a biome they had never visited
• Staff teleport — send another player to a random safe spot, in their world or another
• PlaceholderAPI — remaining cooldown and the last world visited
• English and Spanish included, and every string a player reads lives in messages.yml in MiniMessage format

HOW IT WORKS IN PLAY

A player types /rtp, the countdown starts, and if nobody hits them they land thousands of blocks away on solid ground, in a biome you allowed. A title tells them they have found a jungle for the first time. Two minutes later they decide it was a mistake and take the back command home. Nothing on the server stuttered while any of that happened.

CONFIGURATION

• config.yml — minimum and maximum radius per world, biome filters, warmup length, cooldowns, the optional cost, discovery titles and how long a return point is kept, every key with a comment beside it
• messages.yml — every string a player reads, so you can reword or re-colour the plugin without touching anything else

COMMANDS AND PERMISSIONS

• /rtp [world] · /rtp back · /rtp other <player> [world] · /rtp reload
• safertp.use defaults to everyone; safertp.back, safertp.other, safertp.cooldown.<n>, safertp.world.<world> and safertp.bypass.cost are yours to hand out
• Every node is declared in plugin.yml, so your permissions plugin lists them all

Commands

Full command and permission reference in the docs ↗