CompassTeleport · Player use
Docs/compass-teleport/CompassTeleport · Player use

CompassTeleport · Player use

Bind a lodestone, prepare a teleport compass, start a teleport, and handle common invalid-target cases.

Required items

Prepare:

  • one ordinary compass;
  • one lodestone;
  • a safe place where the lodestone can remain;
  • enough experience levels to pay the anvil rename cost.

The compass does not need a specific name. When an anvil produces a lodestone compass, the plugin adds the teleport marker and usage instructions to the result.

Prepare a teleport compass

1. Bind the lodestone

Hold the compass and right-click a placed lodestone. The plugin records the destination and tells you in chat to rename the compass.

2. Rename it in an anvil

Put the compass in an anvil. Enter a name and take the result. The administrator sets the experience cost with cost-level. The result includes a “teleport compass” description, the target world, and the target coordinates.

If the result has no teleport instructions, confirm that the compass was bound to a lodestone and check that the server has enabled CompassTeleport.

3. Start the teleport

Hold the compass produced by the anvil and right-click the air. The plugin shows a status message, waits for the configured delay-sec, and then teleports you near the lodestone.

Right-click the air rather than a block. Right-clicking a lodestone starts the binding flow. Right-clicking the air uses a prepared teleport compass.

Delay, cooldown, and repeated use

  • The delay-sec setting controls the pre-teleport wait. Do not move or start another interaction during this wait.
  • After the teleport task completes, the player enters the cooldown from cooldown-sec. The cooldown applies to that player only.
  • Using the compass while a teleport task is pending does not create a second task. The plugin reports that the attempt cannot continue.
  • When an administrator sets delay-sec to 0, the plugin omits the visible delay message but still keeps a very short internal scheduler wait. It should not be read as an exact same-tick teleport.

Invalid compass

If the chat says that the compass cannot track its lodestone, check these causes:

  1. The lodestone was broken, moved, or is no longer valid.
  2. The compass lost its vanilla lodestone-tracking state.
  3. The held item is an ordinary compass or was not produced by the plugin’s anvil flow.
  4. You do not have compassteleport.use.

After replacing the lodestone, use a fresh ordinary compass and prepare a new result instead of relying on the invalid item.