No menu, however polished, can make /rtp fast - only the engine behind it can. With most random-teleport plugins, any click can make the server load chunk after chunk after chunk: it picks a spot, loads it on the main thread, and - if it turns out unsafe - tries another, and another, with nothing telling it to stop. That lag spike never shows up in the menu. It shows up in your MSPT, in the stutter every other player feels, and eventually in the players who quietly stop logging in.

LeafRTP was built on one idea: a teleport should cost the server nothing the player can feel. No spike. No spinner. No quiet churn.

Benchmarked, not asserted. 19.8 TP/s sustained at a 4 ms worst-case main-thread tick on Paper (next-best plugin: 70 ms), with audited safety invariants - no unsafe blocks, no force-loaded chunks, no claim-bypassing teleports, no silent failures. Every number on this page is measured on a public harness you can rerun yourself.


Why operators pick LeafRTP

If /rtp is the top entry in your timings report, this is the fix. LeafRTP is the fastest free Random Teleport plugin for Bukkit-native Minecraft servers (Paper, Bukkit, Arclight, Mohist, and other Bukkit-family forks), with Fabric supported as a first-class platform:

• No lag spikes when players spam /rtp. Worst-case main-thread tick stays at 4 ms (vs. 70-852 ms for the next plugins) - your TPS holds at 20.00 during a teleport burst.
• Instant teleports, no "Finding a safe location..." wait. Pre-verified location queue serves /rtp in one tick instead of loading chunks on demand.
• Works on plain Bukkit servers at Paper-class speed. Off-tick .mca Anvil pre-filter, worst tick stays at 3 ms while competitors spike past 3 seconds.
• Runs on Folia out of the box - regionized scheduling + async teleport, no extra config.
• Cross-server /rtp without Redis or SQL - the proxy-direct transport lets a Velocity lobby send players to a backend region over a lightweight TCP socket, no database required.
• Clickable /rtp menu GUI world & region selection - players pick worlds and regions from an interactive book menu (Paper / Folia; chat-paginated elsewhere), no commands to memorize.
• Eight claim-plugin integrations bundled (GriefDefender, GriefPrevention, Lands, WorldGuard, Towny, Factions, HuskTowns, RedProtect) - no add-ons to install.
• Per-player cooldowns & usage limits - per-permission cooldown and limit nodes out of the box, so /rtp spam is capped without an extra plugin.
• Configurable arrival title, sound & effects - the on-screen teleport title/subtitle, sounds, and particle/firework effects are all tunable per region, so the landing looks and feels like your server.
• Audited safety: no unsafe blocks, no force-loaded chunks, no claim-bypassing teleports, no silent failures.

On Paper 1.21, measured on the in-repo benchmark harness, two clients spamming /rtp back-to-back:

Plugin	TP/s	Worst tick (MSPT p99)	CPU per teleport
LeafRTP	19.8	4 ms	16.9 ms
JakesRTP	20.0	70 ms	26.0 ms
BetterRTP	7.3	852 ms	53.6 ms
HuskHomes RTP	6.2	372 ms	52.2 ms

Methodology: Paper 1.21, 2 OPed clients spamming /rtp continuously, in-repo harness linked below. Spigot and Folia results in the full benchmark section.

Already comparing against EzRTP? In the same harness EzRTP managed 1.76 TP/s at a 2,903 ms worst tick (139.6 ms CPU per teleport) - LeafRTP is ~11x the throughput at roughly 1/700th the worst-case tick spike. EzRTP also throws NoSuchMethodError on plain Spigot 1.20.1 (Paper-only API); LeafRTP runs Paper-class on plain Spigot/Bukkit. Numbers and repro in the full benchmark section below.


Same throughput as the next-best plugin, ~17x lower worst-case tick spike, 35% less CPU per teleport. On Spigot, LeafRTP's worst tick stays at 3 ms while competitors spike past 3 seconds. Reproduce on your own rig: helpers/StressTestRTP/.

And free doesn't mean bare-bones. The same off-tick architecture that keeps your TPS steady also runs the clickable /rtp menu, eight bundled claim integrations, the full effects engine, live map heatmaps, and built-in /rtp info diagnostics - speed is what makes the feature set affordable, not a trade against it.

Each capability below is paired with the part of that architecture that makes it cheap to run - the feature set and the performance are the same system, not opposite ends of a dial:

Feature you get	What makes it cost the server nothing
Clickable /rtp menu - book UI (Paper / Folia) or chat-paginated menu	Menu rendering runs off the main thread, so opening it never touches your MSPT.
Lifecycle effects engine - particles, sounds, fireworks, potions, titles	Effect math and packet work run async, so they never cost you TPS.
8 bundled claim integrations - GriefDefender, GriefPrevention, Lands, WorldGuard, Towny, Factions, HuskTowns, RedProtect	Claim checks reroll inside the async pipeline, not on the tick that teleports the player.
Live map heatmaps (/rtp scan) - green/red safety painted on a real held map	The .mca Anvil pre-filter and chunk-load passes run off-tick and throttled, so a scan runs on a live server without tanking TPS.
Built-in /rtp info diagnostics - TPS/MSPT (spark-enhanced when spark is installed), heap, latency percentiles, rejection breakdown, and a /rtp info biomes player-occupancy leaderboard	Metrics are sampled without blocking a tick, so the dashboard reads pre-collected numbers at no hot-path cost.
Optional PvP / combat-tag gate - refuse or delay /rtp for players who recently dealt or took PvP damage, with native tracking plus PvPManager / CombatLogX / Simple Combat Log integration	Combat state is checked once at /rtp pre-dispatch through the rtp-api hook, so the anti-escape rule adds no per-tick cost to the teleport path.
Instant teleports - no "Finding a safe location..." wait	A pre-warmed, pre-verified location queue serves /rtp in one tick instead of loading chunks on demand.

See the engine work: real-time visual diagnostics
Most random-teleport plugins are a black box - you find out a region is full of unsafe ground only when players start complaining. LeafRTP turns that into something you can watch.

Run /rtp scan on a region and hold the map: LeafRTP paints each sector green (safe) or red (unsafe) as it verifies it, live, on a real vanilla map item - while the chat readout streams cps, land %, and an ETA so you know exactly how long a pre-warm will take.

• Two passes, and the heavy one runs off-tick. The first pass reads .mca Anvil region files on a background pool - it never touches the main thread (S-005) and throws out most of a region (ocean, wrong biome, obviously unsafe) before any chunk is loaded. Only the survivors reach the second pass, a throttled live chunk-load verification; because the Anvil pre-filter has already discarded the bulk of the region, that live pass is a small fraction of what a naive pre-generator would load, and it is paced so a scan can run on a live server without tanking TPS.
• It is a diagnostic, not a chore. The red/green map and the rejection breakdown in /rtp info tell you why a region rejects coordinates (bad biome, unsafe block, claim), so you can tune safety.yml against evidence instead of guesswork.
• Free, and cross-platform. The held-map heatmap ships in the free build on Paper, Spigot, Fabric, and NeoForge - not a static PNG you export to disk and open over FTP.

Runtime observability built in (/rtp info)
No metrics add-on, no external dashboard. /rtp info reports the numbers an operator actually watches, sampled without blocking a tick:

• TPS (1m / 5m / 15m) and live server MSPT with tick-budget utilisation.
• JVM heap used / max, and current chunk-ticket leak rate.
• Pipeline latency percentiles (P50 / P75 / P90 / P95 / P99) and slow-teleport count.
• Generation success / failure rate with the top coordinate-rejection cause and a full breakdown by cause.
• Queue depth and growth warnings, plus database round-trip latency.

This is the part competitors describe as "enterprise-grade" in their listing copy. Here it is a command you can run, with every field traced to a requirement in TRACEABILITY.md.


Requirements
A few hard requirements. If any are a no, EssentialsX /rtp or HuskHomes are fine free alternatives.

• ✅ Java 21+ on your host (REQ-RTP-SYS-001, non-negotiable).
• ✅ Paper, Spigot, or a Bukkit-family fork (Arclight / Mohist supported for Forge bridges). Fabric and NeoForge (1.21.x / 26.1.x) are supported and regularly tested, at feature parity with the Bukkit family in the latest builds.
• ✅ In-game editing or YAML, your call. Browse and tune config from the clickable /rtp menu (book on Paper / Folia, chat-paginated elsewhere), or edit the plain YAML files directly and version-control them.
• ✅ Runs on Folia out of the box - regionized scheduling + async teleport, no extra config. The tuned, throughput-optimized Folia adapter ships first in LeafRTP-Pro.
• ✅ Vault economy works in the free build - charge players per /rtp with per-region price, biome surcharges, and a balance floor; cost refunded automatically on cancel or pipeline failure; dormant when Vault is not installed.
• ✅ Cross-server /rtp without Redis or SQL - the proxy-direct transport (Velocity) ships in the free build. SQL/Redis shared-state backends ship in LeafRTP-Pro.

Install (30 seconds)

1. Drop LeafRTP-x.y.z.jar into plugins/.
2. Start the server. A default region is generated for you.
3. Type /rtp.
4. Run /rtp menu to browse regions, worlds, and configuration in-game (clickable book on Paper / Folia, chat-paginated fallback elsewhere).

Tune plugins/RTP/config.yml and plugins/RTP/regions/*.yml later - via /rtp menu or by editing the YAML directly. Full admin guide is auto-unpacked into plugins/RTP/docs/ on first run, and lives online at the admin guide.


Core capabilities

• Deterministic spiral selection — bounded math, no unbounded re-roll loops. Predictable on huge worlds.
• Spatial memory that persists across restarts — LeafRTP learns which sectors keep failing and stops trying them.
• ⏱️ Most /rtp calls serve instantly from a pre-generated location queue — destinations are chunk-loaded and verified before you type the command.
• ️ Safety pipeline — radius check, invulnerability timer, optional landing platform, movement / damage cancel timers, material allow/deny list.
• Optional PvP / combat-tag gate - off by default; when enabled, /rtp is refused or delayed for players who recently dealt or took PvP damage, so a teleport can't be used to escape a fight. Native combat tracking, with optional PvPManager / CombatLogX / Simple Combat Log integration.
• ️ Per-region arrival schematics — drop a .schem named after a region into plugins/RTP/schematics/ and every teleport into that region pastes it (a lobby pad, arrival shrine, or custom platform) on the landing spot. Cross-platform Sponge .schem, decoded in-house (no WorldEdit required), claim-aware and audited.
• Per-region, per-world config — shapes (square / circle / rectangle), curve weighting, vertical adjustors, sky-light check, world overrides, hot-reloadable YAML.
• ✨ Effects on every lifecycle phase — particles, sounds, fireworks, potion, note effects via the in-tree effects-api, gated by rtp.effects.<name> permissions.
• Eight claim-plugin integrations bundled — GriefDefender, GriefPrevention, Lands, WorldGuard, Towny, Factions, HuskTowns, RedProtect.
• Iris, Terra, and custom datapack generators work out of the box, with modded biome IDs preserved. PlaceholderAPI and ProtocolLib are supported as optional soft-deps.
• Optional Vault economy - charge players per /rtp with per-region price, priceOther, params/biome surcharges, and a balance floor (economy.yml); cost refunded automatically on cancel or pipeline failure (refundOnCancel: true default); dormant when Vault is not installed.
• ️ Public rtp-api - same surface as Pro. Trigger LeafRTP from a GUI, NPC, or quest; build your own UX without forking.
• ️ Live map / heatmap visualizations - /rtp scan paints region safety state (green safe / red unsafe) onto a real held map item while the chat readout streams cps, land %, and ETA. Free on Paper, Spigot, Fabric, and NeoForge.
• Built-in runtime observability - /rtp info reports TPS/MSPT (spark-enhanced when spark is installed), JVM heap, pipeline latency percentiles, generation success/failure breakdown, and a /rtp info biomes player-occupancy leaderboard - no metrics add-on needed.
• 12 locales, parity-enforced - shipped locales are CI-verified so a translated server never silently falls back to English on a new key.
• Unusually thorough engineering docs - 28+ dated ADRs and a requirements-to-tests trace, public: docs/dev/INDEX.md.

Platform support

Platform	Status	Notes
Paper (+ forks: Purpur, Pufferfish, Leaf, Leaves, DivineMC)	✅ Recommended	Fully async via native getChunkAtAsync.
Spigot (+ Spigot forks)	✅ Supported	Off-tick .mca Anvil pre-filter → Paper-class throughput on plain Spigot.
Arclight / Mohist (Forge bridges)	✅ Officially supported	Use the Spigot/Paper jar. Recommended way to run on Forge.
Folia	✅ Supported	Runs on Folia via regionized scheduling + async teleport. The tuned, throughput-optimized adapter ships first in LeafRTP-Pro.
Multi-server / proxy (Velocity)	✅ proxy-direct (free) / full SQL+Redis (Pro)	proxy-direct transport ships in the free build: cross-server /rtp over a lightweight TCP socket, no Redis/SQL. SQL/Redis shared-state backends ship in LeafRTP-Pro.
Fabric	✅ Supported	First-class, stable, in-scope platform; tested regularly, at feature parity with the Bukkit family in the latest builds.
Native NeoForge	✅ Supported	First-class adapter on Minecraft 1.21.x / 26.1.x.
Native Forge	Use Arclight / Mohist	No native adapter planned.

Need tuned Folia throughput, SQL/Redis backends, or paid support?
LeafRTP-Pro is a drop-in upgrade - same configuration, same data files, same commands. It adds:

• Tuned Folia adapter (Region Scheduler + off-tick pre-filter, no 1-tick stalls) - the free build runs on Folia with a correctness-first scheduler; this throughput-optimized adapter ships here first, with the guaranteed-response support a region-threaded server needs
• SQL / Redis shared-state backends (H2, SQLite, MySQL, PostgreSQL, Jedis) for multi-server deployments that need a durable shared store - the free build's proxy-direct transport covers the no-database case
• Multi-server / proxy support validated on the in-repo devstack (2 proxies, 2 lobbies, 2 backends behind shared Redis)
• Full curated lang/** locale set (free ships a trimmed set), login-reserve cache, visitor mode
• The richer safety.yml grammar: vanilla block tags (#minecraft:leaves), state predicates (OAK_SLAB[waterlogged=true]), wildcards (*[waterlogged=true])
• Earliest releases on each version, and first access to new platforms and features + priority support within a documented response window

Links

• LeafRTP admin & configuration guide - install, configure, command reference
• LeafRTP addon / API developer guide - rtp-api and examples
• LeafRTP changelog & roadmap
• LeafRTP on Modrinth - latest builds, Folia-tagged releases, and beta channels (auto-updater friendly)
• LeafRTP source on GitHub - star, watch, contribute, file issues
• LeafRTP-Pro (Folia, proxy, SQL/Redis) - the high-performance paid build of this random teleport engine