v2.3.1-26.1
TeleportCommandsFabric v2.3.1
This is the first GitHub release for the v2.3 release line. It includes all features and improvements introduced in v2.3, together with the stability fixes delivered in v2.3.1.
What's New:
-
Add JourneyMap integration
- Sync TPC homes and warps to JourneyMap
- Route teleport actions from synchronized JourneyMap waypoints through TPC commands
- Support
/back deathteleport handling for matching JourneyMap death waypoints
-
Add BlueMap integration
- Publish server-side warp markers to BlueMap web maps
-
Add a shared map synchronization layer for bundled client map integrations
Changes:
-
Expand the Standard build to include bundled Xaero, JourneyMap, and BlueMap integrations
-
Keep the Core build focused on core teleport and storage functionality without bundled map integrations
-
Add a legacy Xaero synchronization compatibility path for the transition between v2.2 and v2.3 clients and servers
-
Improve map synchronization so unchanged waypoint snapshots are not repeatedly sent to clients
-
Improve waypoint persistence behavior across supported map integrations
-
Rename the Xaero-specific admin module wording to the more general
integrationname- Keep the historical
xaeroconfig section name for configuration compatibility
- Keep the historical
-
Preserve home and warp entries during profile loading when their dimensions are temporarily unavailable
-
Move
deleteInvalidcleanup to teleport-time validation and ensure cleanup only removes the exact unchanged invalid waypoint -
Normalize command return values across modules for clearer command-block and administration behavior
-
Improve teleport execution state handling
- Capture the previous location before teleport execution
- Save it only after the teleport succeeds
-
Improve target teleport safety checks
- Treat doors as passable space
- Prevent fences, walls, and fence gates from being accepted as safe standing support
- Add a timeout fallback for parallel safety checks
-
Limit the configurable target chunk preload radius to a maximum of
3chunks- Existing larger values are normalized automatically
/tpc config teleporting preloadRadiusenforces the same range
-
Update
/tpc helpand/tpc statusto report whether client map synchronization is available -
Keep config schema version at
3and storage schema version at1
Bug Fix:
-
Fix
deleteInvalidpotentially removing valid warp data during server startup before all dimensions become available -
Fix asynchronous invalid-waypoint cleanup potentially deleting a newly created or updated waypoint with the same name
-
Fix creative and fall-flying state remaining active after teleport, especially during cross-dimension teleportation
-
Fix camera and player-state reset edge cases after teleport
-
Fix a BlueMap lifecycle race that could access an outdated API instance while BlueMap is being disabled or reloaded
-
Prevent malformed current or legacy map synchronization packets from requesting unsafe client-side memory allocation
-
Fix teleport safety workers attempting to synchronously create missing chunks before the warmup region finishes loading
-
Ensure parallel safety checks only read already loaded chunks instead of falling back to worker-thread world chunk loading
Other:
-
The Standard build is recommended for players and servers using supported map integrations
-
The Core build is intended for servers that only need core teleport functionality or do not need bundled map integrations
-
Core teleport commands remain fully usable as a server-side mod without requiring client installation
-
Matching v2.3 client and server builds are recommended for map synchronization features
-
No config or storage migration is required when upgrading from v2.2 or v2.3
这是 v2.3 版本线首次在 GitHub 上正式发布,包含 v2.3 引入的全部功能与改进,以及 v2.3.1 提供的稳定性修复。
新增功能:
-
添加 JourneyMap 联动
- 将 TPC 的 home 和 warp 同步到 JourneyMap
- 从同步的 JourneyMap 航点执行传送时,通过 TPC 命令处理
- 对匹配的 JourneyMap 死亡航点提供
/back death传送支持
-
添加 BlueMap 联动
- 将服务端 warp 标记发布到 BlueMap 网页地图
-
添加供内嵌客户端地图联动使用的通用地图同步层
变更:
-
扩展标准版,现在内嵌 Xaero、JourneyMap 和 BlueMap 联动
-
核心版继续只提供核心传送与存储功能,不包含内嵌地图联动
-
添加旧版 Xaero 同步兼容路径,用于 v2.2 与 v2.3 客户端和服务端之间的过渡
-
改进地图同步,未发生变化的航点快照不会被重复发送给客户端
-
改进受支持地图联动中的航点持久化行为
-
将管理命令中 Xaero 专属的模块名称调整为更通用的
integration- 为保持配置兼容性,配置文件继续使用历史遗留的
xaero配置段名称
- 为保持配置兼容性,配置文件继续使用历史遗留的
-
加载玩家和全局数据时,即使对应维度暂时不可用,也会保留 home 和 warp
-
将
deleteInvalid清理移至传送目标验证阶段,并确保只删除那个确切且未发生变化的无效航点 -
统一各模块的命令返回值,改善命令方块和管理工具中的执行语义
-
改进传送执行状态处理
- 在执行传送前捕获上一位置
- 仅在传送成功后保存该记录
-
改进目标传送安全检查
- 将门视为可通行空间
- 不再将栅栏、墙和栅栏门视为安全的站立支撑
- 为并行安全检查添加超时回退
-
将目标区块预加载半径的最大值限制为
3个区块- 现有的更大数值会被自动规范化
/tpc config teleporting preloadRadius也会执行相同的范围限制
-
更新
/tpc help和/tpc status,现在会显示客户端地图同步是否可用 -
配置结构版本保持为
3,存储结构版本保持为1
Bug修复:
-
修复服务器启动期间维度尚未全部可用时,
deleteInvalid可能误删有效 warp 数据的问题 -
修复异步无效航点清理可能误删后来创建或更新的同名航点的问题
-
修复传送后创造模式飞行或鞘翅飞行状态可能未被正确清除的问题,尤其是跨维度传送场景
-
修复传送后玩家状态和相机状态重置的边缘情况
-
修复 BlueMap 禁用或重载期间可能继续访问已失效 API 实例的生命周期竞态
-
修复异常的新版或旧版地图同步数据可能请求不安全客户端内存分配的问题
-
修复安全检查预热区域尚未完成加载时,安全检查工作线程可能尝试同步创建缺失区块的问题
-
确保并行安全检查只读取已加载区块,不再回退到工作线程中的世界区块加载路径
其他:
-
推荐使用受支持地图联动的玩家和服务器选择标准版
-
核心版适合只需要核心传送功能,或不需要内嵌地图联动的服务器
-
核心传送命令仍然可以作为纯服务端模组使用,不要求客户端安装
-
使用地图同步功能时,建议客户端和服务端均使用匹配的 v2.3 版本
-
从 v2.2 或 v2.3 升级不需要迁移配置或存储数据