-
Notifications
You must be signed in to change notification settings - Fork 1
EN 8 Troubleshooting
中文版本 | English version
First check if the module is disabled. Use /tpc enable <module> if needed. Then verify sender permission and command spelling (for example worldspawn vs rtp).
If config file was edited manually, run /tpc reload.
If values were changed via admin commands, they are usually saved immediately and no extra reload is needed. Also confirm JSON itself is valid.
When troubleshooting intermittent issues, temporarily run /tpc debug true to enable extra diagnostic logs. After reproducing the issue and collecting logs, run /tpc debug false to avoid long-term diagnostic noise.
/back defaults to the latest death location, and that record is cleared after server restart. Also, if target is unsafe and safety check is not bypassed, teleport can fail. If you recently used home, warp, worldspawn, or rtp, try /back tp as well.
Usually check whether rtp.maxRadius and rtp.minRadius are set appropriately or not suitable. In some terrains/restricted regions, finding safe points may consistently fail.
Confirm that the wild module is enabled and that wild.minRadius is not above wild.maxRadius. Wild does not support dimensions with a natural ceiling, such as the Nether. Distant chunk-load failures, world-border limits, or no safe surface destination across all four batches can also fail the operation. Changing dimension or running /tpcancel cancels the current search.
Confirm that you are using the Standard build and that the integration module is enabled (the config file field is xaero.enabled=true). If syncIntervalSeconds is large, updates may appear delayed. If config was edited manually, run /tpc reload first.
For Xaero or JourneyMap, confirm that the client has the Standard build of TeleportCommandsFabric and the corresponding map mod installed. If only specific homes, shared homes, or warps are missing, check the corresponding list visibility controls. A shared home must also be subscribed. Reconnecting establishes a fresh sync state and reconciles locally synced waypoints.
For BlueMap, confirm that BlueMap is installed and enabled on the server and that the warp dimension has a matching BlueMap world/map. BlueMap publishes warps only, not personal homes, and is independent of /mapwarp and /gwarpmap client-map visibility settings.
If synchronization still fails after these checks, run /tpc debug true and look for server log entries showing waypoint snapshots being sent. The server does not send waypoint snapshots when the client has no supported map mod or is using the Core build.