Give players a reliable route home and to friends
A named home is useful only if players can remember how to return to it and understand why a teleport sometimes cancels. Start with one home and one friend request, then add public warps once you have checked the arrival spots.
Add Homes and Teleports to your world
- Open the plugin page and choose an existing world you own, or create a new world with the plugin selected.
- Check the included requirements. Each world supports up to eight plugins, including dependencies.
- Start a sleeping world, or use the dashboard restart option for a running world. Adding, removing and updating plugins takes effect when the world restarts; coordinate with anyone playing.
Save a home on safe ground
Stand where you want to arrive, with a floor and clear headroom, then save a short name. Reusing that name moves the home. List homes to check the saved name, walk away and return while standing still through warmup. Operators bypass the usual wait, so use a regular player when testing that behavior.
/sethome base
/homes
/home baseAsk rather than teleporting someone silently
Send a request to an online friend, replacing Alex with their name. The recipient accepts or denies it; requests can expire and disappear when a participant leaves. Movement or damage during warmup cancels a pending teleport. The destination must still pass safety checks at the time it happens.
/tpa Alex
/tpaccept
/tpdeny
/tpcancelCreate a shared destination deliberately
An operator can stand at an accessible location and create a warp. Players can list and use it without receiving operator powers. Inspect home-teleport status before changing private settings and reload after editing. Use back for the previous plugin teleport or recorded death position only when a safe destination exists.
/setwarp meeting
/warps
/warp meeting
/back
/hometp statusCheck the result
- Move during a regular player’s warmup and verify cancellation, then test a clear landing successfully.
- Restart normally and check homes and warps, including a deliberately blocked arrival that should be refused safely.
Limits and compatibility
- Back-history is kept in memory and is forgotten when the player leaves; it is not a persistent travel log.
- Player requests are same-dimension by default, while homes can cross dimensions unless the operator changes those settings.
These instructions are for JetRift’s own Homes and Teleports plugin. JetRift does not install arbitrary Paper, Spigot, Forge or Fabric extensions. Commands use player names from your world; replace example names before running them. Operators can use the dashboard Console without the leading slash.
Full command reference · Current client and hosting limits
Related plugin guides
Create a world with Homes and Teleports Add to an existing world