
Tpa +
Tpa+ is a modern teleport request plugin with /tpa and /tpahere, including cooldowns, expiry, delayed teleport safety, and clickable accept/deny actions. It also offers confirmation GUIs, auto-accept, per-player request blocking, and many more features.
1.8.0
Compatibility
Changes
⚡ Tpa+ v1.8.0 — Return Back, Anti-Trap Safe Landing & PAPI Expansions
🌟 What's New in v1.8.0:
- New
/tpaback(or/back) Command:- Teleport back to your previous location before a teleport or after death!
- Fully configurable cooldown, warmup delay, and permission (
aiotpa.back).
- Synchronous Anti-Trap Safe-Landing Engine:
- Completely thread-safe synchronous landing block validation. Zero Paper async block access warnings.
- Enhanced hazard detection: blocks powder snow, wither roses, sweet berry bushes, campfires, lava, void boundaries, and suffocation blocks.
- Interactive Clickable
[✖ Cancel]Button:- When players send
/tpaor/tpahere, an interactive[Cancel]button appears in chat with hover tooltip, allowing one-click cancellation.
- When players send
- Cinematic Warmup Titles:
- Configurable on-screen countdown title & subtitle (
Teleporting in %seconds%s...) and arrival splash title (Teleported!).
- Configurable on-screen countdown title & subtitle (
- Native PlaceholderAPI Expansion (
%tpaplus_...%):%tpaplus_pending_incoming%: Number of incoming requests.%tpaplus_pending_outgoing%: Number of outgoing requests.%tpaplus_cooldown_seconds%: Remaining cooldown time.%tpaplus_autoaccept_status%: Auto-accept status (Enabled/Disabled).%tpaplus_toggle_status%: Request toggle status.%tpaplus_has_back%: Whether a previous location is saved.%tpaplus_in_combat%&%tpaplus_combat_seconds%: Combat tag status.
🛡️ Fixes & Optimizations
- Eliminated all asynchronous chunk/block reading risks on modern Paper/Purpur/Folia.
- Full backwards compatibility with 1.20.x through 1.21.4+.
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:gdzdDRM6:hvxtTaxz"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:gdzdDRM6:hvxtTaxz"
}
