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 and runtime sharing, tpa handles player-to-player requests, warp provides public server points, worldspawn returns players to a configured world spawn, and rtp / wild provide nearby random movement and long-range exploration. 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 map integration. Existing server warp data, each player’s own home data, and subscribed shared homes can be synced into map waypoints so players can view and use locations more directly in supported map mods.

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.
• Map integration sits on top of existing teleport data for map display and linkage.

Base teleport functionality is server-side usable. Players can still use /home, /sharedhome, /warp, /back, /tpa, /worldspawn, /rtp, and /wild without installing this mod or a map mod on the client. Client-side installation only improves command sending, map display, and map interaction; it is not required for base command availability.

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; homes can also be published for runtime subscription.
• tpa: temporary coordination with request/accept/expire behavior.
• back: death-triggered recovery path.
• worldspawn: explicit shared return point.
• rtp: nearby randomized movement; wild: long-range surface exploration.

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.

Map Integration at a Glance

Map integration builds on existing teleport data. The Standard build supports Xaero, JourneyMap, and BlueMap: Xaero and JourneyMap receive each player's own home, subscribed shared-home, and server warp waypoints, while BlueMap publishes public warp markers to the server's web map. The Core build does not include these bundled integrations.

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

Client Installation Strategy

This section compares client-side experience only. It assumes the server has TeleportCommandsFabric installed and relevant modules are configured normally.

Item	Client without this mod	Client with this mod only	Client with this mod + supported map mod
Server teleport commands	back/home/sharedhome/warp/tpa/worldspawn/rtp/wild all available	Same as left	Same as left
Command execution feel	Standard vanilla flow	Smoother sending for some clickable commands	Same as middle
Location visibility	Mostly command names and chat feedback	Same as left	Own homes, subscribed shared homes, and warps visible on map
Map interaction	No extra integration	No extra integration	Supported map mods can be used for location awareness and interaction
Best fit	Pure server-side command experience	Command-focused gameplay with smoother operation	Map-oriented visibility and multiplayer coordination

The key distinction is: command availability does not depend on client installation, while interaction quality can improve when the client mod and a supported map mod are installed.

BlueMap is a server-side web-map integration. Players do not need this mod or a map mod on their clients to view its warp markers; they use the BlueMap web page provided by the server.

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.