How to Manage Teleport Requests, RTP, and Queued Teleports in Essential Commands

guide

Essential Commands handles player-to-player teleport requests, random teleports, and delayed teleports through chat commands and its interface rather than through crafting.

Sending a Teleport Request

You can ask another player to teleport in one of two directions: you can request to go to them, or request that they come to you. After you send one, you receive confirmation that the request reached the other player. If you already have an unanswered request open with that same player, the new one is not sent and you are told about the existing request instead.

Receiving and Answering Requests

When someone asks to teleport to you, or asks you to teleport to them, you get a message naming that player and explaining how to respond. The message tells you to type the accept command or the deny command, each followed by the player's name. Use the accept action to approve the request and the deny action to reject it. Accepting produces a confirmation that the request was accepted; denying produces a confirmation that it was denied.

If you try to accept without naming a player and only one request is waiting, it goes through. If several requests are pending, you are told there is more than one and asked to specify which player's request you mean. If you name a player who has not sent you a request, you are told there is no pending request from them. If nothing is pending at all, you are told there are no pending teleport requests.

Canceling a Request You Sent

A request you sent can be withdrawn before it is answered. Doing so gives you a confirmation that the request to that player was canceled. If you have no open request, you are told there is nothing active to cancel.

Expiration

Requests do not stay open forever. A request you sent can expire, and you are notified of this as the sender. A request you received can also expire, and you are notified of this as the receiver.

Random Teleport (RTP)

The RTP command sends you to a random location. It picks that location a set distance away from spawn, so spawn must already be defined; if it is not, you are told spawn is not set. RTP must be enabled in the world you are in, and if it is not, you are told so for that world by name. The command can also fail before running, in which case you see the reason. A cooldown can apply, and when it does you are told how many seconds remain. The mod also measures how long it takes to work out whether a candidate RTP location is valid.

Queued Teleports

Some teleports are delayed rather than instant. When one starts, you are told which destination it is heading to and how many seconds it will take. When it finishes, you get a confirmation naming where you arrived.

A queued teleport can be interrupted before it completes. Two stated reasons are taking damage and moving. Interdimensional teleportation can be disabled, in which case the teleport fails and you are given that reason.

Starting a new teleport cancels a queued one that is already in progress. You are told which destination was canceled and which new destination replaced it.

Several other teleport destinations exist alongside requests and RTP: homes, warps, and spawn. Homes and warps can be listed, and both can fail to resolve when a name does not match anything. A home or warp can also fail to be created because the name is taken or, for homes, because a limit was reached. Where a command needs a name and more than one match exists, you are asked to give the specific name.