Teleport requests, /back and /rekit
How players visit each other with /tpa, return with /back and put their kit back on with /rekit, and how to give a rank a shorter /rekit wait.
Three commands move a player around once the sandbox worlds exist: /tpa to visit somebody, /back to return to where they were, and /rekit to put their kit back on. None of them works while the player is combat-tagged. Only /rekit has a cooldown.
Before you start#
Players need a kit and at least one world must be ready. See Your first sandbox. The commands and permissions are listed in Commands and Permissions.
Steps#
Ask to teleport with /tpa
A player runs /tpa <player>. The target must already be inside a sandbox world; asking somebody in the lobby is refused. If the requester is already in a sandbox, the request carries the kit they wear. Otherwise the usual kit rule applies: none refuses, one goes straight through, two or more opens the kit list.
The target answers
The target gets a centred message with clickable ACCEPT and DECLINE buttons that run /tpaccept and /tpdeny. With no name, those commands take the newest request still alive. A request expires after 60 seconds, and both sides are told.
Return with /back
/back takes a player to the last place they were inside a sandbox world. Run it again and it returns them to where they stood, so it works as a return trip.
Put the kit back with /rekit
Inside a sandbox world /rekit re-applies the kit the player is wearing (not their favourite) and refills health, food and saturation. Between two uses they wait 30 seconds by default.
Check that it works#
With two players inside a sandbox, one runs /tpa <other>, the other clicks ACCEPT, and the first lands next to them. Then /back sends them to where they were before. After a death, /back brings the player to the spot they died, wearing a kit they pick if they have several.
Going further#
Give a rank a shorter /rekit wait#
Give the rank exyliasandbox.rekit.cooldown.<seconds>, for example exyliasandbox.rekit.cooldown.10. If a player holds several, the lowest wins. For everyone else change rekit.cooldown-seconds in config.yml. See Configuration.
Change how long a request lives#
tpa.request-timeout-seconds in config.yml (60 by default; the settings menu allows 5 to 3600).
When /back has nowhere to go#
The player is told there is no saved location, or that it is not in one of the plugin's worlds. Nothing is saved after a restart.
Technical details
/tpa: a second request to the same player is refused (tpa.already-sent); a disconnect drops every request to and from that player./tpacceptrequires the accepter to be inside a sandbox world (tpa.accept-outside-world);/tpdenyhas no such check. A player building a kit, waiting in a queue, held by another activity or combat-tagged can neither send nor accept; accepting is refused withtpa.player-unavailableif the requester became one of those since. Accepting claims the requester, saves and clears their inventory if they were outside, applies the chosen kit and moves them./tpaneedsexyliasandbox.command.tpa;/tpdenynever needs a permission./back: one point per player, and only a location inside a sandbox world. It is written when a player already inside re-rolls with/rtp, when a/tpathey sent goes through, when a teleport pad picks them up from inside, and when they die (the death location becomes the point)./backfrom the lobby runs the kit rule (none refuses withqueue.no-kit, one goes through, several open the kit list). From inside a sandbox the kit is kept. The point is used once and cleared on disconnect./rekit: refused when not in a sandbox world (rekit.not-in-world) or with no active kit (rekit.no-kit); the cooldown messagerekit.cooldownshows the time left (%time%).- The
/backpoint, pending requests and the worn kit live in memory. A restart clears all three.
Something missing on this page? Tell us on Discord