2.0.1.1
Compatibility
Changes
🎉 YuTeleport 2.0.1.0 Changelog 🎉
📦 Version Upgrade: 2.0.0.0 → 2.0.1.0
🔥 Key Highlight: New /back return module – retrace your every step!
✨ New Features
🔹 Return Command Family
/back– Return to the last returnable location 📍/back death– Return to your last death point 💀/back list– View your return history; click to teleport (requires interactive chat enabled) 📋/back clear– Clear your own back history 🗑️
🔹 Broader Tracking
- Records plugin teleports, death locations, and external plugin teleport positions 🔄
🔹 Data Persistence
- Saves up to 5 recent records by default
- Automatically expires after 30 minutes ⏳
🔹 Independent Configuration
/backhas its own settings for: warm‑up, cooldown, economy cost, safe landing, world whitelist/blacklist, and hooks ⚙️
🔹 New Permission Nodes
yuteleport.back.use– Use permissionyuteleport.back.death– Death return permissionyuteleport.back.clear– Clear permissionyuteleport.back.admin– Admin permission 👑
🔹 PlaceholderAPI Support
- Added a placeholder for the back module toggle 🧩
🔹 API Extensions
- Added Back teleport type and request interface 🧬
🛠️ Adjustments & Fixes
- Config version upgraded to
config-version: 20📄 - Added
teleports.backconfig section, enabled by default ✅ - 🐛 Fixed: Empty world whitelist/blacklist at module level not correctly overriding default restrictions
- Cooldown backend refactored to use shared YuLib bucket‑based cooldown implementation, with a separate back‑specific bucket 🪣
⚠️ Upgrade Notes
-
Before updating, we recommend backing up:
plugins/YuTeleport/config.yml- The data directory (
plugins/YuTeleport/data/)
-
If you do not need
/back:- Set
teleports.back.enabled: falsein the config to disable it 🚫
- Set
-
For servers with custom permission groups:
- Check whether you need to grant or restrict the new back‑related permissions 🔐
🚀 Enjoy the plugin, and may your teleports be flawless! Feel free to report any issues.
— YuTeleport Dev Team ❤️
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:a9538uT9:l1uH5ne7"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:a9538uT9:l1uH5ne7"
}

