Tags
Creators
Details
Licensed GPL-3.0-only
Published 8 months ago
Updated 2 months ago
All versions
2.3-snapshot-1
Beta
Teleport Commands Fabric (TPC) 2.3-snapshot 14 months ago 32
Compatibility
Minecraft: Java Edition
26.2
26.1.x
Platforms
Fabric
Quilt
Supported environments
Server-side
Client and server
Changes
TeleportCommandsFabric v2.3-snapshot 1
This is a beta / snapshot build for the upcoming v2.3 release.
Build Variants
- Standard build: includes all core teleport features plus bundled map integrations for Xaero and JourneyMap.
- Core build: includes only the core teleport command features, without bundled map integrations.
What's New
- Added JourneyMap integration for synced homes, warps, and death-location teleport handling
- Added a shared map integration sync protocol used by bundled map integrations
- Added
Standard/CoreMod Menu badges to distinguish build variants - Added Mod Menu parent metadata so bundled integration jars are grouped under the main mod entry
Changes
- Renamed the runtime map integration module to
integration- Example:
/tpc enable integration - Example:
/tpc config integration syncIntervalSeconds <seconds>
- Example:
- Kept the config file section name as
xaerofor backward compatibility - Updated README and Wiki docs for standard/core builds and map integrations
- Improved map waypoint synchronization so unchanged waypoint snapshots are not resent
- Changed invalid-dimension cleanup behavior:
- home/warp entries are preserved during storage load
deleteInvalidcleanup now happens only when a teleport attempt finds that the target world is unavailable
- Added a defensive timeout fallback for parallel target teleport safety checks
Bug Fixes
- Fixed a data-loss risk where enabling
deleteInvalidcould remove valid warp data during server startup before all dimensions were available
Compatibility
- Core teleport commands remain server-side and are not affected by client version mismatch
- Map integrations require compatible TeleportCommandsFabric versions on both client and server
- TeleportCommandsFabric 2.3 map integration is not compatible with 2.2 map integration
- 2.3 client + 2.2- server: map waypoint sync is not expected to work
- 2.2- client + 2.3 server: map waypoint sync is not expected to work
- If you use Xaero or JourneyMap integration, update both the client and server to 2.3
Notes
- If you use map integrations, install the standard build on both client and server
- If you only need server-side commands, the core build is sufficient
- Existing configs remain compatible; the map integration config section is still named
xaero
这是即将发布的 v2.3 的 beta / snapshot 构建。
构建版本
- 标准版:包含所有核心传送功能,并内置 Xaero 与 JourneyMap 地图联动。
- 核心版:仅包含核心传送命令功能,不包含内置地图联动。
新增功能
- 添加 JourneyMap 联动,支持同步 home、warp 和死亡位置传送
- 添加通用地图联动同步协议,用于内置地图联动模块
- 添加
Standard/CoreMod Menu 标记,用于区分构建版本 - 添加 Mod Menu parent metadata,使内置 integration 子 jar 归入主 mod 条目下显示
变更
- 运行时地图联动模块名改为
integration- 示例:
/tpc enable integration - 示例:
/tpc config integration syncIntervalSeconds <seconds>
- 示例:
- 配置文件中的字段名仍保留为
xaero,以兼容旧配置 - 更新 README 和 Wiki 中关于标准版/核心版与地图联动的说明
- 改进地图航点同步,避免重复发送未变化的航点数据
- 调整无效维度清理行为:
- 加载存储时会保留 home/warp 数据
deleteInvalid只会在传送时发现目标世界不可用后执行清理
- 为并行目标安全检查添加超时回退,避免 worker 异常卡住时长期阻塞服务器 tick
Bug 修复
- 修复开启
deleteInvalid时,服务器启动阶段可能错误删除有效 warp 数据的风险
兼容性说明
- 核心传送命令仍然是服务端功能,不受客户端版本不一致影响
- 地图联动需要客户端和服务端安装兼容版本的 TeleportCommandsFabric
- TeleportCommandsFabric 2.3 的地图联动协议不兼容 2.2 的地图联动协议
- 2.3 客户端 + 2.2- 服务端:地图航点同步预计无法正常工作
- 2.2- 客户端 + 2.3 服务端:地图航点同步预计无法正常工作
- 如果使用 Xaero 或 JourneyMap 联动,请将客户端和服务端都更新到 2.3
说明
- 如果需要地图联动,请在客户端和服务端都安装标准版
- 如果只需要服务端传送命令,核心版即可
- 现有配置保持兼容;地图联动配置字段仍然叫
xaero
Optional dependencies
Any compatible version
Any compatible version
Any compatible version
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| tpc-fabric-26.1.2-2.3-sources.jar | Sources jar | 433.46 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:qi3DFHz0"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ez3Wxkfr:qi3DFHz0"
}

