EN 9 FAQ

9 FAQ

中文版本 | English version

Is this a pure server-side mod?

Core features can run server-side only. If clients also install the mod, user experience is more complete and can integrate further with Xaero.

Do clients have to install this mod?

No. Base commands such as home, warp, back, tpa, worldspawn, and rtp work server-side only.

Client installation mainly improves command-sending experience and enables map integration when Xaero map mods are also installed.

Does this mod heavily modify game behavior?

No. Server-side mixin usage is intentionally small and mainly records player death locations. Command registration, config, storage, and teleport services are handled by the mod's own systems.

Client-side mixins mainly support Xaero map integration and command-sending experience. Without the client mod installed, base server commands are unaffected.

How do I enable/disable a module?

/tpc enable/disable <module>

Currently available module names:

• back
• home
• tpa
• warp
• worldspawn
• rtp
• xaero

What does warp.maximum=0 mean?

It means no limit on total global warp count.

Is debug logging enabled by default?

No. Extra debug logs are disabled by default. When troubleshooting, temporarily run:

/tpc debug true

After collecting the needed logs, turn it off:

/tpc debug false

Why does defaultSafetyCheck not trigger target safety checks by itself?

Known-target teleport safety checks require target preloading plus either the default safety setting or an explicit per-command override:

• teleporting.preloadEnabled=true
• teleporting.defaultSafetyCheck=true, or the command explicitly passes <disableSafetyCheck>=false

If target preloading is disabled, known-target teleports such as home, warp, back, and worldspawn use the original target directly. RTP is not affected by this rule; it uses its own independent random-destination safety logic.

Can xaero.syncIntervalSeconds be set to 0?

No. The current minimum is 1 second, and both config loading and admin commands clamp lower values to that minimum. Client-side request throttling still follows its own separate logic.