1.2.0+sponge-1.21.6-1.21.7
Compatibility
Changes
1.2.0
New
/tpa back(/tpaback) returns you to where you were before your last teleport; use it again to swap back. The spot is remembered across restarts./tpa trust <player>accepts that player's requests automatically;/tpa trustlists who you trust./tpa all(/tpaall) asks everyone online to come to you (yeths.tpa.all, OPs by default)./tpa version, and/tpa setting <key>explains what a setting does.- Shortened names:
/tpa stefinds Steve when no one else matches, for/tpa accepttoo. - No more teleporting to a player who is flying or gliding with nothing below them (
void-check). - Settings
allow-cross-dimension,allow-tpahere,back-enabled,allow-trustandvoid-check, and theyeths.tpa.bypass.dimensionpermission. - A chat
prefixand the Accept/Deny button labels can be set inmessages.properties. - When an update adds settings or messages, they are added to your existing files, which keep your values.
config.propertiesnow explains every key. - Clickable Accept/Deny buttons on Forge 1.7.10 and 1.12, Fabric 1.14 – 1.15 and Forge 1.14.4 – 1.15.
Platforms
- One Paper/Spigot/Purpur/Folia jar for 1.8.8 – 26.3, replacing the separate Bukkit and Folia jars.
- New: Forge 26.3, 1.14.4 and 1.15.x; Forge 1.18.x, 1.19 – 1.19.2 and 1.19.3 – 1.19.4 as separate builds; NeoForge 1.20.5 – 1.20.6; Sponge now has one jar per SpongeAPI version, from API 8 (1.16.4) to API 21 (26.3), which adds 1.16 – 1.19 and 1.21.2 – 1.21.11. NeoForge 26.3 is built against the stable release.
- The Forge 1.20 jar is also listed for NeoForge 1.20.1.
- The Velocity and BungeeCord companions are discontinued. They only forwarded
/tpa, which proxies already do, and registering the command on the proxy hid the backend's tab completion. Install the mod or plugin on the backend servers. - Rift 1.13.2 is rebuilt against a Rift built from source (its old artifacts are gone; see
versions/rift/).
Corrected version ranges
Several 1.1.0 jars were built against the newest version of their range and listed for older versions they can't run on. Their Modrinth listings are narrowed to what they were built for, and the gaps are filled by new builds where possible:
| 1.1.0 jar | Listed for | Built for | 1.2.0 |
|---|---|---|---|
| Forge 1.7 | 1.7.2 – 1.7.10 | 1.7.10 | 1.7.10 |
| Forge 1.8 – 1.12 | 1.8 – 1.12.2 | 1.12.x | 1.12.x |
| Forge 1.13 – 1.16 | 1.13 – 1.16.5 | 1.16.x | 1.14.4, 1.15.x and 1.16.x jars |
| Forge 1.17 – 1.20.1 | 1.17 – 1.20.1 | 1.20.x | 1.18.x, 1.19 – 1.19.2, 1.19.3 – 1.19.4 and 1.20.x jars |
| NeoForge 1.20.2 – 1.20.6 | 1.20.2 – 1.20.6 | 1.20.2 – 1.20.4 | separate 1.20.5 – 1.20.6 jar |
| Fabric 1.14 – 1.15 | 1.14 – 1.15.2 | 1.15.x | separate 1.14 jar |
| LiteLoader | 1.7.10 – 1.12.2 | 1.12.2 | 1.12.2 |
| Legacy Fabric | 1.7.2 – 1.13.2 | 1.13.2 | 1.13.2 |
| Ornithe | 1.7.2 – 1.13.2 | 1.13.x | 1.13.x |
| Sponge 1.21 | 1.21 – 1.21.11 | 1.21 – 1.21.1 (API 12) | a jar for each later API |
| Sponge 26 | 26.1 – 26.2 | 26.1.x (API 19) | separate 26.2 jar |
Fixes
- Folia: the plugin no longer blocks the global region thread while it waits for player and block data, which could freeze servers running few region threads. A safety check is now one hop to the destination's region instead of one per block, and teleports run on the player's own thread.
- Cross-dimension teleports on Ornithe 1.0 – 1.6.4, Legacy Fabric and Babric used Minecraft's death respawn and could clear the player's inventory.
- Forge 1.7.10 and 1.12 and LiteLoader no longer build a nether portal next to the destination of a cross-dimension teleport.
- Forge 1.7.10 registered its tick handler on the wrong event bus, so countdowns and request expiry never ran.
- Forge 1.7.10 and 1.12 looked up the attacker by name through reflection, which only works in a development environment; PvP was never recognised on real servers.
- Legacy Fabric found the player behind a command the same way, so every command silently did nothing.
- Rift called Minecraft by dev-time names through reflection too, so chat, teleports and permission checks failed on real servers; it now calls them directly.
- LiteLoader never noticed players leaving, so their requests and teleports lingered.
- On Fabric 1.14 – 1.19.3, Legacy Fabric, LiteLoader and Ornithe 1.13, damage is detected reliably. It used to depend on the exact tick it was checked in.
- A PvP hit now cancels the countdown even with
combat-timeout 0, and when the destination player is hit, both players are told who took damage. - Hits that another mod or plugin cancels (claims, protection) no longer count as damage on Forge, NeoForge, Fabric 1.21+ and Sponge.
- Standing on the bottom block of the world no longer counts as a hazard on Fabric, Forge and NeoForge.
- Slimes, magma cubes, ghasts, phantoms, shulkers and hoglins count as hostile mobs on Fabric, Forge and NeoForge.
&codes in a name typed into a command are no longer turned into colours.- Magma blocks and campfires count as hazards on Forge 1.16 and Sponge.
- Player data files are replaced atomically, so a crash mid-save can't wipe someone's ignore list.
- Indented messages (like the
/tpa listentries) keep their leading spaces in new message files.
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:2eBnbq9r:vXHekYMX"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:2eBnbq9r:vXHekYMX"
}

