EN 2 Features Overview

2 Features Overview

中文版本 | English version

TeleportCommandsFabric is centered around one thing: server-side teleport management. It puts common teleport features (death return, homes, TPA, public warps, world spawn teleport, random teleport) into one system, and organizes them under a unified command and configuration model. For players, this means common teleport commands are in one place. For administrators, maintenance becomes more centralized through module toggles, config changes, and data management.

This page explains what is included, how features relate to each other, and what to focus on when reading later pages.

What the Mod Includes

Functionally, TeleportCommandsFabric can be viewed as three parts.

The first part is player-facing teleport capability: back handles death return, home handles personal homes, tpa handles player-to-player requests, warp provides shared server points, worldspawn returns players to a configured world spawn, and rtp provides random teleport. These form the core of the mod.

The second part is the admin control surface. Admins can use /tpc to enable/disable modules, reload config, and modify common runtime values directly.

The third part is Xaero integration. Existing server warp data and each player’s home data can be synced into map waypoints so players can view and use locations more directly in Xaero.

If you only want the high-level structure, keep these three points:

• Players mainly interact with teleport commands.
• Admins mainly interact with module switches and config commands.
• Xaero integration sits on top of existing teleport data for map display and linkage.

From the Player Perspective

Players usually do not treat modules as isolated systems. In practice they are a toolbox used together. home and warp are typically the most stable fixed-point teleports. tpa is for temporary grouping. back handles death recovery. worldspawn and rtp are often used for reset, regroup, exploration, or escape.

Even though each command has a different purpose, experience remains consistent. For example, global delay and cooldown can affect multiple teleport commands. If a command executes but teleport is not immediate, root causes are often shared across modules.

From the Admin Perspective

Admins care about maintainability. One key design goal is to keep module management consistent. Module toggles are centralized in /tpc enable and /tpc disable. Common values are updated online via /tpc config .... Combined with reload, this covers most daily adjustments.

As a result, troubleshooting flow is also consistent. If a command is unavailable, first check module state. If command runs but teleport is delayed, check global delay and cooldown. If behavior still mismatches expectation, check module-specific config next. This pattern works well for both small servers and long-running environments.

How Modules Relate

Module names look parallel, but their roles differ in practice:

• home and warp: stable fixed-point teleport features for long-term use.
• tpa: temporary coordination with request/accept/expire behavior.
• back: death-triggered recovery path.
• worldspawn: explicit shared return point.
• rtp: exploration/escape with randomized outcomes.

Understanding this helps when reading module pages. All are teleport features, but each has different priorities: some focus on data management, some on safety checks, some on world/environment constraints.

Impact of Unified Global Config

An important characteristic of this mod is that broad-impact behavior is configured globally. The clearest examples are teleport delay and cooldown. Any command path that uses the shared teleport pipeline will be affected by these values.

This is also why troubleshooting should not focus on one command only. A command that appears “not immediate” may simply be respecting global delay. Conversely, a command that is completely unavailable is more likely tied to module enablement or module-level settings.

Xaero Integration at a Glance

Xaero integration builds on existing teleport data. The server packages warp and home into waypoint payloads and syncs them to eligible clients when the module is enabled. Players can then discover common/public points more easily via map UI.

This does not replace base commands. Even without Xaero, home/warp continue to work. With Xaero enabled, changes are mostly in map visibility and interaction. For detailed switch/interval/behavior settings, see 5.7 Xaero Integration. For architecture-level understanding, this overview is enough.

What to Read Next

If you are new, continue with 3 Commands and Configuration to understand command entry points. If you are ready to tune behavior, go to 4 Configuration File. If you already know which module you need, jump to 5 Module Details.