-
Notifications
You must be signed in to change notification settings - Fork 1
EN 5 7 Xaero
中文版本 | English version
This module connects existing teleport data to supported maps. Xaero and JourneyMap display server warp waypoints, each player's own home waypoints, and subscribed shared homes; BlueMap publishes server warp markers to its web map. Existing teleport commands do not depend on map integration and remain available as usual.
The Standard build currently includes Xaero, JourneyMap, and BlueMap integrations. The Core build does not include bundled map integrations.
/tpc enable integration
/tpc disable integration
/tpc config integration syncIntervalSeconds <seconds>
/maphome <name> <true|false>
/mapwarp <name> <true|false>
/gwarpmap <name> <true|false>Base teleport commands do not require anything on the client. Installation requirements differ by integration:
- Xaero: install the Standard build of TeleportCommandsFabric plus Xaero's Minimap / Xaero's World Map on the client.
- JourneyMap: install the Standard build of TeleportCommandsFabric plus JourneyMap on the client.
- BlueMap: install the Standard build of TeleportCommandsFabric and BlueMap on the server. Players only need the BlueMap web page provided by the server; no client mod is required.
With server-side installation only, commands such as home and warp still work. Xaero and JourneyMap waypoint display, map teleport routing, and synced-waypoint deletion mapping require the corresponding client environment. BlueMap warp markers are provided entirely by the server and web map. Follow launcher or log guidance for dependencies required by each map mod.
This config group controls the global map-integration switch and update interval, plus persistence and display names for client waypoint groups. The config field remains named xaero for backward compatibility; runtime commands use the module name integration. Current config shape:
"xaero": {
"enabled": true,
"syncIntervalSeconds": 10,
"persistWaypointSets": true,
"warpSetName": "Default",
"homeSetName": "Default"
}Xaero and JourneyMap use the client sync path. After joining, an integration-capable client requests a snapshot; the server then sends changed waypoint snapshots no more frequently than syncIntervalSeconds. Subscribing, unsubscribing, or changing personal map visibility for a shared home also marks that player for a refresh.
BlueMap uses a separate server-side path. Under the same module switch and update interval, it publishes existing server warp entries to maps for matching dimensions. It sends no client waypoint payload and does not publish personal homes.
After integration is disabled, locally persisted Xaero or JourneyMap waypoints may not disappear immediately and are reconciled when reconnecting. The marker set created by this mod in BlueMap is cleared by the server.
By default, both warpSetName and homeSetName use Default. If an older config still contains TeleportCommands Warps, TeleportCommands Homes, default, current, or a blank value, it is normalized back to Default during config load.
For Xaero and JourneyMap, TeleportCommands-tagged waypoint teleport actions are routed back into the corresponding home / warp command flow whenever possible. Deleting a synced waypoint is interpreted as a visibility change rather than deletion of server data. Death waypoints matching a recorded location can also route to /back death. BlueMap only provides web marker display and does not provide these client command routes.
The three maps organize data differently. Xaero follows the configured set names. JourneyMap places synced warps and homes into separate TPC groups. BlueMap creates a Warps marker set on every matching world map. persistWaypointSets, warpSetName, and homeSetName affect only client maps that support those concepts; they do not rename the BlueMap marker set.
To hide a point in your own Xaero or JourneyMap data, use /maphome or /mapwarp. Admins can control whether a warp is sent as a public client waypoint with /gwarpmap <name> <true|false> or the controls in /warps. BlueMap is a public server web map and publishes all valid warps, independent of personal and global client-map visibility preferences.
Focus on these points:
-
syncIntervalSecondsdirectly controls server-side periodic sync rhythm. -
Defaultis the default group name, and legacy equivalent values are normalized automatically during load. - Xaero and JourneyMap receive server
warp, current-player home, and subscribed map-visible shared-home data; BlueMap publishes serverwarpdata only. -
maphome/mapwarpaffect the current player's own map visibility, whilegwarpmapaffects global warp waypoint visibility. - After disabling integration, existing client waypoints may not disappear immediately; BlueMap markers are cleared by the server.
Server-side teleport commands work regardless of client mods installed. The table below compares client-side experience.
| Scenario | No Client Mod | Client Mod Only | Client Mod + Supported Map Mod |
|---|---|---|---|
| Personal, shared, and public teleport | Via /home, /sharedhome, and /warp
|
Same | Same, plus waypoints visible on map |
| Command execution feel | Standard vanilla flow | Smoother sending for some clickable commands | Same as middle |
| Point awareness | Relies on command names and chat hints | Still command-driven | Map shows own homes, subscribed shared homes, and warps |
| Daily travel | Often requires re-querying or memorizing names | Command operations smoother | Map targeting more direct, round-trip more efficient |
| Troubleshooting scope | Focus on server commands and config | Also confirm client mod is loaded | Also check map mod install, integration module switch, and syncIntervalSeconds
|
If you prefer pure commands, skip the client mod. If you want smoother command operation, install the client mod. If you also want waypoint visualization and map integration, use the full combination with a supported map mod.
BlueMap is outside the client-installation combinations in this table. When the server runs the Standard build with BlueMap, players can view server warp markers through its web map.