TeleHop

🌐 TeleHop

Cross-server teleportation for Paper and Velocity networks

TeleHop is a full-featured teleportation suite built for multi-server Minecraft networks. Every feature works across servers, players stay connected across your entire network.

All data is stored in MySQL, so homes, warps, teleport requests, and player state stay synced at all times.

---

🔗 Links

- GitHub Repository - Full Documentation - Configuration Guide - Installation Guide - Permissions Reference - Database Structure - Issue Tracker and Support - Releases

---

📦 Version 1.0.2

Focus on stability, cross-server consistency, and feature completeness.

➕ Added

- Random respawn system with safe async location search - Respawn config with full control over behaviour - Generated `WIKI.md` config reference on first run - Improved feature toggles for per-server control

🔧 Improved

- Cross-server sync for homes, warps, and TPA - Teleport safety checks for RTP and respawn - Async handling for teleport and location search - Config migration system with non-destructive updates

🐛 Fixed

- Cross-server teleport failures in edge cases - TPA desync between servers - Back command inconsistencies after death - Permission inconsistencies across modules

---

✨ Features

🚀 Teleportation

- `/spawn` send players to the hub server from anywhere - `/tpa` request teleport to another player across servers - `/tpahere` pull another player to your location - `/tpaaccept`, `/tpadeny`, `/tpacancel` - `/tpatoggle` block incoming requests for the session - `/back` return to last teleport or death location across servers - `/rtp` random teleport with GUI region and dimension selection, configurable radius, safe landing

---

💀 Random Respawn

- Teleport players to a safe random location on death - Async safe location search - Respects beds and anchors - Skips hub server - Controlled via `respawn.yml` - Enabled by default via `features.yml`

---

🌍 Warps

- Admin warps: `/warp`, `/setwarp`, `/delwarp`, `/warps` - Shared across all servers via MySQL - Player warps: `/pwarp` with per-rank limits and public or private toggle

---

🏠 Homes

- `/home`, `/sethome` - Permission-based slots from 1 to 5 - GUI with slot indicators - Cross-server teleport support - Blocked server support

---

🛠 Admin Tools

- `/tp`, `/tphere` cross-server admin teleportation - `/telehop reload` reload config - `/telehop version` show version - `/telehop perms` list permissions - `/telehop help` show help - `/listwarps` list all warps - `/forcedelwarp` remove warp - `/forcedelhome` remove player home

---

⚡ Highlights

- Fully cross-server, all features sync across Velocity - MySQL backed, no per-server duplication, MariaDB supported - Random respawn system with full config control - Modular config, enable or disable features per server - Teleport effects, configurable particles and sounds - Multi-language, 6 built-in languages with fallback support - LuckPerms support for limits and permissions - Tab completion across the entire network - Auto config migration with safe updates - `WIKI.md` generated automatically for full config reference

---

🧩 Multi-Server Support

TeleHop is built for Velocity networks, not single-server setups.

- Velocity handles routing and player tracking - Paper handles teleport execution - MySQL stores shared data

This enables: - Cross-server TPA and teleportation - Shared homes and warps across all servers - `/back` working across server boundaries - Session-based TPA toggle synced across servers

Both Velocity and Paper plugins are required.

---

📥 Installation

Requirements

- Paper 1.21+ - Velocity 3.3+ - Java 21+ - MySQL 8.0+ or MariaDB 10.5+ - LuckPerms 5.4+ optional

---

Setup

1. Create a MySQL database and user 2. Place `telehop-velocity-1.0.2.jar` in the Velocity plugins folder 3. Place `telehop-paper-1.0.2.jar` in each Paper server plugins folder 4. Start Velocity once to generate config, then stop 5. Configure `database.yml` with your credentials 6. Set `server-name` in `general.yml` to match Velocity config 7. Start Velocity, then start all backend servers

Database tables are created automatically on first startup. Random respawn is enabled by default. Disable in `features.yml` if needed.

---

🔄 Updating

- Replace old `.jar` files - New config files are added automatically - Existing configs are not overwritten - Legacy `config.yml` is migrated and renamed to `.old`

---

📁 Configuration Layout

``` plugins/TeleHop/ config/ general.yml database.yml features.yml teleport.yml tpa.yml rtp.yml home.yml respawn.yml WIKI.md storage.yml languages/ ```

---

🗄 Database Tables

- `players` tracks player server - `warps` stores admin warps - `player_warps` stores player warps - `tpa_requests` stores active requests - `homes` stores player homes

---

🔐 Permissions

Use `/telehop perms` in-game for the full list.

Default Permissions

- `telehop.spawn` - `telehop.rtp` - `telehop.warp` - `telehop.pwarp` - `telehop.tpa` - `telehop.tpahere` - `telehop.tpa.accept` - `telehop.tpa.deny` - `telehop.tpa.cancel` - `telehop.tpa.toggle` - `telehop.homes` - `telehop.homes.1`

---

🏠 Home Slots

- `telehop.homes.1` to `telehop.homes.5`

---

🌍 Player Warp Limits

- `telehop.warps.1` - `telehop.warps.3` - `telehop.warps.10` - `telehop.warps.100` - `telehop.warps.unlimited`

---

🔓 Per Warp Access

- `telehop.warp.<name>`

---

🛠 Admin Permissions

- `telehop.admin` - `telehop.back` - `telehop.back.death` - `telehop.tp` - `telehop.tphere` - `telehop.rtp.bypasscooldown` - `telehop.rtp.bypassdelay` - `telehop.tpa.bypasscooldown` - `telehop.warps.unlimited`

---

⚠ Compatibility

- Paper only - Velocity only - BungeeCord not supported - Hybrid servers not supported

---

👤 Credits

Developed by Epildev & GitEpildev from Epildevconnect ltd Licensed under MIT Licence