YuTeleport

# 🎲 YuTeleport / YuTP – Cross-Version Safe Teleport Plugin ## 🛡️ Safe Landing | 🧭 Random Teleport | 📍 Warp | 🏠 Home | 🤝 TPA | 🔙 Back | 📡 Coordinate Sharing | 🧵 Folia Support 😱 Worried that random teleport might drop players into lava, underwater, inside blocks, at the void edge, or onto dangerous platforms in the Nether? 🧭 Want to manage resource‑world scatter points, public waypoints, player homes, TPA, /back, and coordinate sharing all in one plugin? 🐌 Don't want traditional teleport plugins to lag the main thread while searching for chunks, nor maintain cooldowns, costs, permissions, and messages separately? 🔧 Don't want multiple plugins fighting over `/warp`, `/home`, `/tpa`, `/back`, and having to debug conflicts one by one? **YuTeleport (YuTP)** is a cross‑version, safe teleport suite for Minecraft Java servers. It is not just a single RTP tool, but a complete teleport system: random teleport, public warps, player homes, TPA‑based mutual teleport, /back return, coordinate sharing, economy integration, permission groups, PlaceholderAPI, a public Java API, Folia/Paper compatibility – all processed through the same teleport pipeline. Current version: **2.0.1.2** Config version: **config‑version 20** --- # 🚀 Core Features - 🧭 **Random Teleport (RTP)**: Per‑world configuration for radius, height range, center point, square/circle distribution, block rules, and biome filtering. - 📍 **Warp (Public Waypoints)**: Supports public, private, and restricted types; includes description, rename, delete, max amount limits, and fine‑grained permissions. - 🏠 **Home (Player Homes)**: Each player saves homes independently; supports multiple homes, public homes, cross‑player access, descriptions, and quantity expansion. - 🤝 **TPA (Player‑to‑Player Teleport)**: Supports `/tpa`, `/tpahere`, accept, deny, cancel, ignore requests, and global tpahere. - 🔙 **Back (Return System)**: Records death points, pre‑teleport locations from plugin teleports, and external teleport origins; supports `/back`, `/back death`, `/back list`, `/back clear`. - 📡 **Coordinate Sharing**: After a successful teleport, players can share their current location to all online players; others can click to teleport. - 🧩 **Unified Teleport Pipeline**: All handling – wait, interrupt, cooldown, cost deduction, refund, safety re‑check, events, status tracking, and hooks – is processed uniformly. - ⚡ **Asynchronous Safe‑Point Search**: On Paper 1.13+ can use async chunk loading to reduce main‑thread stress; falls back to sync mode automatically when unsupported. - 📦 **Landing‑Point Pre‑caching**: Background preparation of safe landing points; when cache is hit, online search wait time is reduced. - 🌿 **Biome Filtering**: Supports black/whitelists, `*` wildcards, and single‑use `biome:<pattern>` specification. - 💰 **Vault / PlayerPoints Economy**: Prices are set per teleport type, per world, and per permission group; failed, cancelled, or Folia‑retired scenarios automatically refund. - 👥 **Permission Group Overrides**: Use `yuteleport.group.<group>` to configure different cooldowns, costs, warp limits, and home limits per group. - ⏳ **Multi‑Channel Countdown**: Chat, BossBar, ActionBar, or silent wait – freely combinable; move, damage, interact, chat, and command interruptions can be toggled individually. - 🎵 **Full Audio‑Visual Feedback**: Countdown sounds, success arpeggios, fail/cancel/cost/refund sounds, titles, particles, click‑to‑retry, and hover coordinates. - 📊 **PlaceholderAPI Extension**: Provides module states, cooldowns, costs, home/warp counts, teleport stats, and back status. - 🧑‍💻 **Java API & Events**: External plugins can initiate teleports, read module data, listen to and cancel teleport lifecycle events. - 🧵 **Folia Scheduling Adaptation**: Uses Region / Entity / Global Schedulers to avoid cross‑region entity access issues. --- # 🧠 Design Philosophy YuTeleport's goal is not merely to "move a player", but to make every teleport request controllable, rollback‑able, and observable – from request to arrival. - Does the player have permission? - Is the target world allowed? - Is the cooldown active? - Does a countdown need to be waited? - During the countdown, did the player move, take damage, chat, or execute commands? - Is a cost required? How to handle balance changes during the wait? - Is the target point safe? Is the target world still loaded? - Should the cost be refunded on failure, cancellation, or entity retirement? - Can third‑party plugins listen to, cancel, or read the result? - Can the player return to their death point or previous location before teleport? These logic pieces are no longer scattered across multiple plugins or modules; they are handled by the unified teleport pipeline. Server owners can use it as the foundational teleport system for production servers, not just a temporary scatter tool. --- # 🧩 Feature Modules ## 🧭 Random Teleport (RTP) Ideal for resource worlds