Tags
Creators
Details
Licensed Apache-2.0
Published 8 months ago
Updated 8 months ago
All versions
2.0.0
Release
Ly+ TPA 2.0.08 months ago 132
Compatibility
Minecraft: Java Edition
1.21.x
1.20.4–1.20.6
Platforms
Bukkit
Geyser Extension
Paper
Purpur
Spigot
Required content
Unavailable version
Changes
Ly+ TPA — Changelog
2.0.0 — Major Rewrite
2026-03-11
Full rewrite as a proper Ly+ addon using the LyPlusAddon API.
✨ Added
- Sender-side Request GUI — opens when you run
/tpaor/tpahere; shows the target's player head, name, and current dimension block before anything is sent to them- 🌿 Grass Block = Overworld · 🔴 Netherrack = Nether · 🪨 End Stone = The End
- Lime = confirm & send · Red = cancel without sending
- Request is only sent when the sender clicks confirm
- Receiver-side Warning GUI — shown to the receiver on
/tpahereacceptance if "TPA-Here Warning" is enabled; displays where they will be teleported before they commit - Action bar countdown — replaces chat messages during the teleport countdown:
✦ Teleporting to <Player> ●●●○○ 3s ✦— progress dots + seconds remaining - Teleport cancels on movement — configurable via
tpa_cancel_on_move - Per-player settings managed entirely in the
/settingsGUI:- Auto-Accept, Countdown, TPA-Here Warning, TPA Reception, TPA-Here Reception
- Friends-only reception — reads friend data from LyPlusFriends addon data (optional)
- Distinct sounds for every interaction: send, receive, countdown tick, teleport, deny, cancel
- Paper Brigadier commands — uses
LifecycleEvents.COMMANDSandpaper-plugin.yml
🔧 Changed
- Plugin rebuilt as a
LyPlusAddon— registers withLyPlusSettingscore on startup - Command registration moved to Paper's Brigadier API
plugin.ymlreplaced bypaper-plugin.yml
🐛 Fixed
- TPA reception settings ("Nobody", "Friends Only") now correctly block requests
- GUI closes properly after teleport acceptance
🗑️ Removed
- Old flat-file data storage replaced by shared
PlayerDatafrom LyPlusSettings core CommandExecutor/TabCompleterinterfaces replaced by Brigadier
1.x.x — Legacy
No public changelog. These versions are no longer supported.
💬 Questions or issues? Join our Discord
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:N3ouNM5A:155Asi7R"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:N3ouNM5A:155Asi7R"
}

