Tags
Creators
Details
Licensed GPL-3.0-only
Published 5 months ago
All versions
2.4-snapshot-1
Beta
Teleport Commands Fabric (TPC) 2.4-snapshot 1yesterday 13
Compatibility
Minecraft: Java Edition
26.2
26.1.x
Platforms
Fabric
Quilt
Supported environments
Server-side
Client and server
Required content
Any compatible version
Changes
TeleportCommandsFabric v2.4-snapshot 1
✨ New Features
Shared Homes
- Added a runtime Shared Home publish/subscribe system
- Publish or rebroadcast a permanent Home with:
/sharehome <name>[Share]and[Broadcast]controls in the Home management page
- Subscribe to shared Homes directly from chat announcements
- View subscribed Homes with
/sharedhomes- Supports pagination, sorting, and filtering
- Includes teleport, map visibility, and unsubscribe controls
- Teleport directly to a uniquely named subscribed Home with:
/sharedhome <name>
- Withdraw a published Home to remove all associated subscriptions
- Renaming or updating a published Home automatically updates its subscribers
- Shared Home teleports support the existing delay, cooldown, preload, safety-check, rotation, effects, and previous-location behavior
Shared Home Configuration
- Added
/tpc config home sharedMax <count>- Controls how many Homes each player may publish
- Defaults to
1
- Added
/tpc config home sharedBroadcastCooldown <seconds>- Controls the minimum interval between broadcasts
- Defaults to
60seconds - Has a minimum value of
10seconds
- Subscription count is not limited
Map Integrations
- Added Shared Home waypoint synchronization for Xaero and JourneyMap
- Subscribers can independently control whether each shared Home appears on their map
- Added map synchronization protocol v2 for Shared Home support
- Existing protocol v1 clients remain compatible with regular Home and Warp synchronization
- BlueMap remains limited to server Warp markers
🛠 Improvements
Home and Warp Pages
- Reworked
/homesand/warpsactions around dedicated management pages - Replaced crowded inline editing controls with a clearer
[Manage]action - Management pages provide teleport, rename, update, default Home, sharing, and deletion controls where applicable
- Added confirmation before deleting a Home or Warp
- Management actions use stable waypoint identities instead of relying only on names
- Page, sorting, and filtering context is preserved when returning from supported management actions
🐞 Bug Fixes
- Fixed parallel target safety checks applying the 5-second timeout separately to each worker result, which could block a server tick considerably longer than intended
- Fixed timed-out safety checks performing an additional synchronous main-thread fallback after the timeout
- Safety batches now use one shared 5-second deadline; timed-out operations fail safely, late results are discarded, and unfinished workers cancel cooperatively
⚠️ Snapshot Notes
- This is a beta snapshot intended for testing before the final v2.4 release
- Shared Home publications and subscriptions are runtime-only and reset when the server restarts
- Temporary Homes cannot be shared
- Shared Home map synchronization requires v2.4 integration support on both the client and server
- The Standard build includes Xaero and JourneyMap Shared Home integration
- The Core build supports Shared Homes through commands and chat UI without bundled map integrations
- No storage schema version change is required
Optional dependencies
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| tpc-fabric-26.1.2-2.4-SNAPSHOT-sources.jar | Source jar | 467.66 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:iE66rlMa"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ez3Wxkfr:iE66rlMa"
}

