If you run a survival or SMP Minecraft server, a random teleport command is one of the first quality-of-life features players ask for. It spreads people out across the map, gives newcomers a fresh patch of wilderness, and takes pressure off the spawn area. BetterRTP is the most configurable way to deliver that on a Spigot or Paper server. It goes far beyond the simple /rtp baked into EssentialsX, giving you per-world radius and center control, biome targeting, blacklists, cooldowns, warm-up delays, and even economy pricing. This guide walks through installing BetterRTP, every command and alias, the permission nodes that actually matter, and the config behavior you need to understand to avoid the most common support tickets.
What BetterRTP is (and what it is not)
BetterRTP, sometimes listed as “Random Wild Teleport,” is a standalone plugin for the Bukkit API. That means it runs on Spigot, Paper, and Paper forks like Purpur on Minecraft: Java Edition. It does not run on vanilla servers, Bedrock, Fabric, or Forge. It is also not part of EssentialsX. Essentials ships its own lightweight /rtp and /wild, but BetterRTP is a separate download with far more control.
Because both plugins can register a /rtp command, servers almost always pick one random-teleport solution. The usual approach is to disable the Essentials RTP (or simply let BetterRTP claim the aliases) and let BetterRTP handle everything. If you are already running EssentialsX for warps, homes, and economy, BetterRTP slots in alongside it cleanly. You can pair it with our other EssentialsX walkthroughs, like creating warp points with EssentialsX, to build a complete teleport toolkit.
Installing BetterRTP
Installation follows the standard Bukkit plugin pattern. Download the BetterRTP JAR from its SpigotMC resource page, then drop it into your server’s plugins folder and restart.
- Stop your server (or prepare to restart it).
- Upload
BetterRTP.jarinto the/pluginsdirectory using your file manager or SFTP. - Start the server so BetterRTP generates its
config.ymland a per-world setup. - Edit the config to taste, then run
/rtp reloadto apply changes without a full restart.
On a managed Minecraft hosting plan, you typically get a one-click plugin manager or a drag-and-drop file browser, so you can skip manual SFTP entirely. If you want a deeper walkthrough of the panel and plugin handling, our Minecraft server documentation covers uploading JARs and managing restarts step by step.
The base command and its aliases
BetterRTP registers a single base command, betterrtp, but it ships with a generous set of aliases so players can use whatever they are used to typing.
Base command: /betterrtp
Aliases: /rtp /brtp /randomtp /wild /wildtpThis is the key thing to understand: /rtp and /wild are the same command, just different names for it. Whichever your players prefer, both route through BetterRTP. Throughout this guide we will use /rtp as the canonical example, but you can substitute any alias.
Every BetterRTP subcommand
Beyond a bare random teleport, BetterRTP exposes a set of subcommands for targeting other players, worlds, and biomes, plus admin utilities. Here is the full verified list.
/rtp Teleport yourself randomly in your current world
/rtp Random-teleport another player
/rtp player Explicit form of the above
/rtp world [biome…] RTP into another world (optionally a biome there)
/rtp biome RTP into one or more specific biomes
/rtp location RTP using a named location preset
/rtp reload Reload the config
/rtp info List worlds and their configured RTP parameters
/rtp version Show the running plugin version
/rtp test Debug/test effects without actually teleporting A few practical notes. /rtp info is your friend when something is misconfigured: it prints each world’s radius, center, and other parameters so you can confirm the server sees the values you set. /rtp test lets staff verify cooldowns, delays, and effects fire correctly without being yanked across the map. And /rtp world is how you send a player from the overworld into, say, a dedicated wilderness or resource world.
Permission nodes — the part that trips everyone up
BetterRTP’s permission model is where most server owners get stuck. The single most important rule: to teleport in a given world, a player needs both the general use permission and a per-world permission. Granting only one of them is the number-one cause of the dreaded “RTP not allowed in this world” message.
betterrtp.use Required to use the RTP command at all
betterrtp.world. Required for the SPECIFIC world (e.g. betterrtp.world.world_nether)
betterrtp.world.* Allows RTP in ALL enabled worlds So a player who can random-teleport in the main overworld (usually named world) needs:
betterrtp.use
betterrtp.world.worldIf you want everyone to RTP everywhere, grant betterrtp.use plus betterrtp.world.* and you are done. The rest of the permission tree covers the more advanced subcommands and bypasses.
| Permission | What it grants | Default |
|---|---|---|
betterrtp.use | Use the RTP command | true |
betterrtp.world | Use the world subcommand | — |
betterrtp.world.* | RTP in all enabled worlds | — |
betterrtp.world. | RTP in the specified world | — |
betterrtp.player | RTP another player | — |
betterrtp.biome | RTP to specific biomes | — |
betterrtp.location | RTP using a named location | — |
betterrtp.group.* | Use a permission group’s restriction profile | — |
betterrtp.sign | Create an RTP sign | — |
betterrtp.bypass.cooldown | Bypass the cooldown timer | — |
betterrtp.bypass.delay | Bypass the warm-up delay | — |
betterrtp.bypass.economy | Bypass the RTP price | — |
betterrtp.bypass.hunger | Bypass hunger cost | — |
betterrtp.reload | Reload config | op |
betterrtp.info | View world RTP info | op |
betterrtp.edit | Edit a world’s center/radius live | op |
betterrtp.updater | Receive update notifications | op |
betterrtp.version | See running version | — |
Note on the group node: betterrtp.group.* lets a player use a permission group’s restriction profile, which is how you give donor ranks shorter cooldowns or larger radii. On some older documentation this same concept appears as betterrtp.config. — the exact spelling can depend on your plugin version, so check your own plugin.yml if a group profile is not applying.
The bypass nodes for staff and donors
The betterrtp.bypass.* family is how you exempt trusted players from the friction features. Give moderators betterrtp.bypass.cooldown and betterrtp.bypass.delay so they can teleport instantly while testing or moderating, and grant betterrtp.bypass.economy to staff or VIPs so they are not charged per teleport.
# Example: a moderator group
betterrtp.use
betterrtp.world.*
betterrtp.player
betterrtp.bypass.cooldown
betterrtp.bypass.delay
betterrtp.bypass.economyConfiguring BetterRTP behavior
BetterRTP’s power lives in its config.yml and per-world settings. The plugin generates these on first start, and you can reload them with /rtp reload. The following features are all supported. Exact YAML key names vary between versions, so treat the descriptions below as the behavior you are looking for rather than copy-paste keys — always confirm against your generated config.
- Minimum and maximum radius with a center point. You define how far from the center a teleport can land, and a minimum that creates a “dead zone” around the center so players never spawn right on top of the same spot. Set this per world.
- World blacklist. Disable RTP entirely in specific worlds — for example, a creative build world or a minigame world where teleporting would be disruptive.
- Biome blacklist / whitelist. Keep players out of (or restrict them to) certain biomes. Common use: stop people landing in oceans or deep frozen biomes.
- Block blacklist. Prevent landings on dangerous blocks like water or lava so the teleport always picks a safe surface.
- Cooldown timer. How long a player must wait between random teleports. Holders of
betterrtp.bypass.cooldownignore it. - Delay / warm-up timer. A countdown before the teleport actually fires, useful for discouraging combat-logging via RTP. Bypassed with
betterrtp.bypass.delay. - Economy price. Charge a fee per teleport (requires a Vault-compatible economy). Exempt players with
betterrtp.bypass.economy.
Community references mention config keys such as center-X/center-Z, max/min radius, and an option to teleport inside the vanilla world border instead of a fixed radius, but exact key spellings differ by build. The safe move is to open the generated config.yml, find the matching section, change the value, and run /rtp reload. If you set an economy price, remember it depends on Vault and an economy plugin being present — many servers use the EssentialsX economy for this, which you can learn to manage in our guide on giving balances with EssentialsX.
BetterRTP vs. EssentialsX RTP
EssentialsX gives you a basic /rtp and /wild that drop a player somewhere random within a configured radius. That is fine for a tiny server. BetterRTP adds the controls a growing community actually needs: per-world radius and center, biome targeting, multiple blacklists, cooldowns, warm-up delays, economy pricing, and permission-based restriction groups for donor perks. If you only need “teleport me somewhere,” Essentials is enough. If you want to shape where, how often, and at what cost players teleport, BetterRTP is the upgrade. Because they collide on the same command names, run one or the other, not both.
Common problems and fixes
- “RTP not allowed in this world.” The player has
betterrtp.usebut is missingbetterrtp.world.for that specific world. Grant the matching world node orbetterrtp.world.*. - Command does nothing / unknown command. Another plugin (often EssentialsX) is claiming the
/rtpalias. Use/betterrtpdirectly to confirm BetterRTP works, then resolve the alias conflict. - Players land in lava or oceans. Add those blocks/biomes to the block or biome blacklist and reload.
- Config changes not applying. You forgot to run
/rtp reload(needsbetterrtp.reload), or you edited the wrong world’s section.
Frequently asked questions
Does BetterRTP work on Bedrock, Fabric, or Forge?
No. BetterRTP is a Bukkit-API plugin, so it runs only on Spigot, Paper, and Paper forks like Purpur on Minecraft: Java Edition. It does not run on vanilla, Bedrock, Fabric, or Forge servers.
Why does a player get “not allowed in this world” when they have permission?
Because /rtp requires two permissions: betterrtp.use and the per-world node betterrtp.world. for the world they are standing in. Having only betterrtp.use is not enough. Grant the matching world node, or betterrtp.world.* for every world.
Can I use BetterRTP and EssentialsX together?
Yes, you can run both plugins, and many servers do because they use EssentialsX for homes, warps, vanish, and economy. But you should only use one RTP solution since both register /rtp and /wild. Most owners disable the Essentials RTP and let BetterRTP own those commands. EssentialsX itself is worth pairing with BetterRTP — see our guides on using the EssentialsX vanish ability and creating a jail with EssentialsX.
How do I charge players to use random teleport?
Set an economy price in the BetterRTP config. This requires a Vault-compatible economy plugin (the EssentialsX economy is a common choice). Players are then charged per teleport, and anyone with betterrtp.bypass.economy teleports for free.
How do I reload the config after editing it?
Run /rtp reload in-game or from the console. It needs the betterrtp.reload permission (default op). Use /rtp info afterward to confirm your radius and center values were picked up correctly.
Can I send a player to a different world or biome?
Yes. Use /rtp world to teleport into another world (requires betterrtp.world plus the target world node), and /rtp biome to land in a specific biome (requires betterrtp.biome). You can even combine them, as in /rtp world .
Wrapping up
BetterRTP turns a one-line convenience command into a tunable system for spreading players across your map, protecting fragile worlds, and even monetizing teleports for donor ranks. The two things to remember are the dual-permission rule (betterrtp.use + betterrtp.world.) and the reload-after-edit habit (/rtp reload). Get those right and the rest is just dialing in radius, cooldown, and price to fit your community. If you are setting up a fresh server to host all of this, grab a Minecraft hosting plan with one-click plugin support and you will have BetterRTP running in minutes.
Free Minecraft Tools
Speed up your server with our free Minecraft tools:
Ready to play?
Run your own Minecraft server with XGamingServer
Spin up an always-on Minecraft server your friends can join in minutes — no port-forwarding, no tech headaches.
