{"id":3163,"date":"2023-04-30T23:01:21","date_gmt":"2023-04-30T23:01:21","guid":{"rendered":"https:\/\/xgamingserver.com\/blog\/?p=3163"},"modified":"2026-06-15T19:20:43","modified_gmt":"2026-06-15T19:20:43","slug":"betterrtp-plugin","status":"publish","type":"post","link":"https:\/\/xgamingserver.com\/blog\/betterrtp-plugin\/","title":{"rendered":"BetterRTP Plugin"},"content":{"rendered":"\n

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<\/strong> is the most configurable way to deliver that on a Spigot or Paper server. It goes far beyond the simple \/rtp<\/code> 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.<\/p>\n\n\n\n

What BetterRTP is (and what it is not)<\/h2>\n\n\n\n

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<\/strong> on Minecraft: Java Edition. It does not<\/strong> run on vanilla servers, Bedrock, Fabric, or Forge. It is also not<\/strong> part of EssentialsX. Essentials ships its own lightweight \/rtp<\/code> and \/wild<\/code>, but BetterRTP is a separate download with far more control.<\/p>\n\n\n\n

Because both plugins can register a \/rtp<\/code> command, servers almost always pick one<\/strong> 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<\/a>, to build a complete teleport toolkit.<\/p>\n\n\n\n

Installing BetterRTP<\/h2>\n\n\n\n

Installation follows the standard Bukkit plugin pattern. Download the BetterRTP JAR from its SpigotMC resource page, then drop it into your server’s plugins<\/code> folder and restart.<\/p>\n\n\n\n

    \n
  1. Stop your server (or prepare to restart it).<\/li>\n
  2. Upload BetterRTP.jar<\/code> into the \/plugins<\/code> directory using your file manager or SFTP.<\/li>\n
  3. Start the server so BetterRTP generates its config.yml<\/code> and a per-world setup.<\/li>\n
  4. Edit the config to taste, then run \/rtp reload<\/code> to apply changes without a full restart.<\/li>\n<\/ol>\n\n\n\n

    On a managed Minecraft hosting plan<\/a>, 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<\/a> covers uploading JARs and managing restarts step by step.<\/p>\n\n\n\n

    The base command and its aliases<\/h2>\n\n\n\n

    BetterRTP registers a single base command, betterrtp<\/code>, but it ships with a generous set of aliases so players can use whatever they are used to typing.<\/p>\n\n\n\n

    Base command: \/betterrtp\nAliases:      \/rtp   \/brtp   \/randomtp   \/wild   \/wildtp<\/code><\/pre>\n\n\n\n
    This is the key thing to understand: \/rtp<\/code> and \/wild<\/code> are the same command<\/strong>, just different names for it. Whichever your players prefer, both route through BetterRTP. Throughout this guide we will use \/rtp<\/code> as the canonical example, but you can substitute any alias.<\/p>\n\n\n\n
    Every BetterRTP subcommand<\/h2>\n\n\n\n
    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.<\/p>\n\n\n\n
    \/rtp                          Teleport yourself randomly in your current world\n\/rtp                  Random-teleport another player\n\/rtp player           Explicit form of the above\n\/rtp world  [biome\u2026]   RTP into another world (optionally a biome there)\n\/rtp biome    RTP into one or more specific biomes\n\/rtp location           RTP using a named location preset\n\/rtp reload                   Reload the config\n\/rtp info                     List worlds and their configured RTP parameters\n\/rtp version                  Show the running plugin version\n\/rtp test                     Debug\/test effects without actually teleporting<\/code><\/pre>\n\n\n\n
    A few practical notes. \/rtp info<\/code> 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<\/code> lets staff verify cooldowns, delays, and effects fire correctly without being yanked across the map. And \/rtp world <\/code> is how you send a player from the overworld into, say, a dedicated wilderness or resource world.<\/p>\n\n\n\n
    Permission nodes \u2014 the part that trips everyone up<\/h2>\n\n\n\n
    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<\/strong> the general use permission and<\/strong> a per-world permission. Granting only one of them is the number-one cause of the dreaded “RTP not allowed in this world” message.<\/p>\n\n\n\n
    betterrtp.use                Required to use the RTP command at all\nbetterrtp.world.      Required for the SPECIFIC world (e.g. betterrtp.world.world_nether)\nbetterrtp.world.*            Allows RTP in ALL enabled worlds<\/code><\/pre>\n\n\n\n
    So a player who can random-teleport in the main overworld (usually named world<\/code>) needs:<\/p>\n\n\n\n
    betterrtp.use\nbetterrtp.world.world<\/code><\/pre>\n\n\n\n
    If you want everyone to RTP everywhere, grant betterrtp.use<\/code> plus betterrtp.world.*<\/code> and you are done. The rest of the permission tree covers the more advanced subcommands and bypasses.<\/p>\n\n\n\n
    \n
    Permission<\/th>What it grants<\/th>Default<\/th><\/tr><\/thead>
    betterrtp.use<\/code><\/td>Use the RTP command<\/td>true<\/td><\/tr>\n
    betterrtp.world<\/code><\/td>Use the world<\/code> subcommand<\/td>\u2014<\/td><\/tr>\n
    betterrtp.world.*<\/code><\/td>RTP in all enabled worlds<\/td>\u2014<\/td><\/tr>\n
    betterrtp.world.<\/code><\/td>RTP in the specified world<\/td>\u2014<\/td><\/tr>\n
    betterrtp.player<\/code><\/td>RTP another player<\/td>\u2014<\/td><\/tr>\n
    betterrtp.biome<\/code><\/td>RTP to specific biomes<\/td>\u2014<\/td><\/tr>\n
    betterrtp.location<\/code><\/td>RTP using a named location<\/td>\u2014<\/td><\/tr>\n
    betterrtp.group.*<\/code><\/td>Use a permission group’s restriction profile<\/td>\u2014<\/td><\/tr>\n
    betterrtp.sign<\/code><\/td>Create an RTP sign<\/td>\u2014<\/td><\/tr>\n
    betterrtp.bypass.cooldown<\/code><\/td>Bypass the cooldown timer<\/td>\u2014<\/td><\/tr>\n
    betterrtp.bypass.delay<\/code><\/td>Bypass the warm-up delay<\/td>\u2014<\/td><\/tr>\n
    betterrtp.bypass.economy<\/code><\/td>Bypass the RTP price<\/td>\u2014<\/td><\/tr>\n
    betterrtp.bypass.hunger<\/code><\/td>Bypass hunger cost<\/td>\u2014<\/td><\/tr>\n
    betterrtp.reload<\/code><\/td>Reload config<\/td>op<\/td><\/tr>\n
    betterrtp.info<\/code><\/td>View world RTP info<\/td>op<\/td><\/tr>\n
    betterrtp.edit<\/code><\/td>Edit a world’s center\/radius live<\/td>op<\/td><\/tr>\n
    betterrtp.updater<\/code><\/td>Receive update notifications<\/td>op<\/td><\/tr>\n
    betterrtp.version<\/code><\/td>See running version<\/td>\u2014<\/td><\/tr>\n<\/tbody><\/table><\/figure>\n\n\n\n
    Note on the group node: betterrtp.group.*<\/code> 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.<\/code> \u2014 the exact spelling can depend on your plugin version, so check your own plugin.yml<\/code> if a group profile is not applying.<\/p>\n\n\n\n
    The bypass nodes for staff and donors<\/h3>\n\n\n\n
    The betterrtp.bypass.*<\/code> family is how you exempt trusted players from the friction features. Give moderators betterrtp.bypass.cooldown<\/code> and betterrtp.bypass.delay<\/code> so they can teleport instantly while testing or moderating, and grant betterrtp.bypass.economy<\/code> to staff or VIPs so they are not charged per teleport.<\/p>\n\n\n\n
    # Example: a moderator group\nbetterrtp.use\nbetterrtp.world.*\nbetterrtp.player\nbetterrtp.bypass.cooldown\nbetterrtp.bypass.delay\nbetterrtp.bypass.economy<\/code><\/pre>\n\n\n\n
    Configuring BetterRTP behavior<\/h2>\n\n\n\n
    BetterRTP’s power lives in its config.yml<\/code> and per-world settings. The plugin generates these on first start, and you can reload them with \/rtp reload<\/code>. 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 \u2014 always confirm against your generated config.<\/p>\n\n\n\n