Tags
Creators
Details
2.2-core
Compatibility
Changes
TeleportCommandsFabric v2.2
This release introduces separate build variants and adds a few small teleport-flow usability improvements.
๐ฆ Build Variants
Starting with this release, TeleportCommandsFabric provides two build variants:
-
Standard build
- Includes the core teleport features
- Includes bundled Xaero integration
- Recommended for most players and servers
-
Core build (with
-coresuffix)- Includes only the core teleport features
- Does not include bundled map integration
- Intended for servers that only need server-side teleport commands, or for setups that do not need map integration
If you are not sure which one to use, choose the standard build.
โจ New Features
-
Added
/back preview- Shows your recorded previous teleport location and death location
- Displays world, position, facing, and pitch
- Includes clickable teleport buttons
- Does not start a teleport, cooldown, or delay
-
Added
/tpcancel- Lets players cancel their own pending teleport
- Works for delayed home, warp, back, worldspawn, RTP, and accepted TPA/TPAHere teleports
- Does not cancel TPA requests that have not been accepted yet
-
Added version and integration status to admin pages
/tpc help/tpc status
๐ Changes
-
Reworked Xaero integration packaging
- Xaero support is now packaged as a bundled integration jar in the standard build
- Core teleport features are separated from bundled map integration
- This enables both a standard build and a core-only build
-
Improved admin CLI output consistency with clearer page headings
๐ Fixes
- Fixed silent Xaero map visibility commands generated from waypoint-delete actions when page arguments were not included
๐ Notes
- Normal server-side teleport features remain available without a client-side mod
- Xaero integration still requires the relevant both-side Xaero map environment for enhanced map behavior
- Config and storage schema versions are unchanged from 2.1
- Standard version may not be compatible with Xaero in 26.2
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| tpc-fabric-26.1.2-2.2-core-sources.jar | Sources jar | 432.26 KiB |
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:ez3Wxkfr:6tGU3xZt"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ez3Wxkfr:6tGU3xZt"
}

