All versions
3.1
Release
Tpa 3.1last week 649
Compatibility
Minecraft: Java Edition
26.3
26.2
26.1.x
1.21.x
1.20.x
Platforms
Bukkit
Folia
Paper
Purpur
Spigot
Changes
Changelog
3.1
New
- Folia support - the plugin now runs on Folia (regionized multithreading) as well as Spigot, Paper and Purpur.
- One jar for Minecraft 1.20 - 26.3 - built for Java 17, so it also runs on older 1.20.x servers.
- Update checker - checks Modrinth for a new version. Admins (
tpa.update.notify, ops by default) get a chat message with a download button when they join. /tpahere <player>- ask a player to teleport to you./tpacancel- cancel your outgoing request./tpatoggle- stop receiving requests (saved across restarts)./tpaaccept [player]and/tpadeny [player]- choose which request to answer when you have more than one. Tab completion included.cancel-on-damageoption - cancel the countdown when the player takes damage.tpa.bypass.cooldownandtpa.bypass.delaypermissions, plustpa.adminfor everything.- Hex colors in messages:
&#RRGGBB. - Sounds can also be given as keys like
entity.enderman.teleport(works with resource pack sounds). - Set any message to
""to turn it off.
Fixed
- The countdown skipped a second and showed the first number twice.
- A new request no longer silently replaces an older request from another player - each player can have several incoming requests.
- Rejoining the server no longer resets cooldowns.
- When a player leaves, requests they sent are now removed too and the other player is told.
/tpaacceptno longer removes the request when the teleport is blocked by a cooldown or a running countdown, so it can be accepted again.- Cooldown times are rounded up, so you no longer see "wait 0 seconds".
/tpa,/tpaacceptand/tpadenynow check thetpa.usepermission.- Vanished players can no longer be found with
/tpa. - Sounds work on every version (the sound API changed in 1.21.3).
- Teleports use the
COMMANDcause, so combat and region plugins can block them. - All remaining Polish text was translated to English.
Config
New options are added to your existing config.yml automatically - your values are kept.
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:ZRgKHQlC:kWJGqAN3"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ZRgKHQlC:kWJGqAN3"
}

