Screenshot 1 of 1. MinecraftHub-generated cover art for EzRTP: a floating snowy block island with server racks, under a night sky
What EzRTP works with.
| Platform | Java Edition |
|---|---|
| Loaders | Bukkit, Folia, Paper, Purpur, Spigot |
| Minecraft versions | 1.7.2, 1.15.2, 1.16.5, 1.17.1, 1.18.2, 1.19.4, 1.20.6, 1.21.11, 26.1.2, 26.2 |
EzRTP is a random teleport plugin for Bukkit, Paper, Spigot, Purpur and Folia servers. It picks safe landing spots, filters them by biome and lets admins cap how often players jump. It runs on the server only, so players need nothing installed.
Server software and versions
- Bukkit, Folia, Paper, Purpur and Spigot: Minecraft 1.7.2 to 26.2. The newest build needs no dependencies, optionally PvPManager, Teams API, WorldGuard, Simple Combat Log, Chunky, PlaceholderAPI, EzCountdown and EzEconomy; some builds for 1.13 to 26.1.2 require WorldGuard, Chunky, PlaceholderAPI, EzCountdown and EzEconomy; some builds for 1.13 to 26.1.2 require WorldGuard, Chunky and PlaceholderAPI.
What it does
Teleports reject unsafe blocks through a configurable list, with recovery behaviour when a spot fails. Search patterns include random, circle, square, triangle and diamond. Biome include and exclude lists work with a pre-cache and a weighted rare-biome search, and a queue throttles busy periods.
Cooldowns and daily or weekly limits apply per world and per group. A GUI selector offers destinations with their own permissions, and named centers let admins anchor a jump to a chosen spot. Pre-generation runs through Chunky with /rtp pregenerate, and region-based jumps use a WorldGuard region command when enabled.
Commands and permissions
- /rtp starts the default flow, either the GUI or a direct teleport. The ezrtp.use permission is granted to everyone by default.
- /forcertp sends a target player, with the ezrtp.forcertp permission (operators by default).
- /rtp reload reloads configuration, and /rtp stats shows overall metrics, biome activity and timing, all operator-only.
- /rtp heatmap hands out an in-game map of where players landed, and /rtp heatmap save writes a PNG to the plugin folder.
- /rtp setcenter and /rtp addcenter manage world and named centers through ezrtp.setcenter.
Installation and configuration
Put the plugin file in the plugins folder and restart, as covered in the plugin installation guide. Configuration is split by concern into rtp.yml, limits.yml, gui.yml, queue.yml, network.yml, force-rtp.yml, performance.yml and storage.yml, which can keep limits in MySQL.
Questions about EzRTP.
4 questions
How do I install EzRTP?
Place the plugin file in the plugins folder of a Bukkit, Paper, Spigot, Purpur or Folia server and restart it. Players join with a normal client and install nothing. Edit rtp.yml, limits.yml and gui.yml afterwards; the /rtp reload subcommand reloads the configuration.
Does EzRTP work on Folia?
Yes. Folia is a listed loader, and the plugin describes its runtime behaviour as Folia-compatible for modern scheduling models. The newest release, 3.4.3, lists Folia alongside Paper, Purpur, Spigot and Bukkit.
Does EzRTP need a permissions plugin?
No. The ezrtp.use permission defaults to true, so every player can use /rtp, while reload, stats, heatmap and /forcertp default to operators. A permissions plugin only becomes useful when you want per-destination GUI access or cooldown and limit bypasses for specific groups.
Can EzRTP pre-generate chunks?
Yes, through the optional Chunky integration. With Chunky installed, /rtp pregenerate takes an optional world and radius and starts Chunky-assisted warmup tasks. Access to the command is controlled by the ezrtp.pregenerate permission. In the newest release Chunky is optional, so the rest of the plugin runs without it.
