StayPut Remixed -----
Return to your last location when returning to a multiverse worldStayPut Remixed (v3.0.0) (1.18-1.21+)
Return to your last location when returning to a Multiverse world
By default, when one switches between multiverse worlds, they are always spawned at the destination world's spawn. This could be particularly annoying to players - instead of returning to a world and resuming where they were, they have to walk from spawn to their last location first.
This plugin fixes that by keeping track of your last location in a world and making sure you return there.
The Remixed fork was created after the original author dropped support and other forks introduced problematic solutions. Remixed aims to keep the original vision of the plugin while fixing issues and keeping it updated.
Install
This plugin uses a database. MariaDB is recommended but MySQL works too. If you don't have a DB server you can also just use SQLite, which saves the DB to a file in your plugins.
To install, download the jar and put it in your plugins folder.
Make sure users have the stayput.use permission or their teleports will not be recorded! In most cases, you will want to apply the permission to the default user group.
Configuration
The configuration file is automatically generated the first time the plugin is run. You can also view the file for the current version here. The file should be called config.yml and be placed in the StayPut folder inside your plugins folder.
Commands
Permissions
Help, I'm still getting teleported to spawn!
This usually happens because another plugin other than Multiverse is currently in charge of your world's spawn location. Turn on debug mode in the config.yml and look at the server console when you teleport. You might see something like this.
[StayPut] PlayerName: world1 --> world2
[StayPut] Not redirecting teleport because the destination appears to be a specific location in the world.
[StayPut] Location{world=CraftWorld(name=world2),x=0.5,y=135.0,z=0.5,pitch=0.0,yaw=-180.0} != Location{world=CraftWorld(name=null),x=0.0,y=135.0,z=0.0,pitch=0.0,yaw=0.0}
In this instance, we can see that the teleport took us to that first location on the third line. But, Minecraft reported the world spawn as that second location and we can see that the x, z, and yaw were different.
In order to fix this, we need to set the world spawn with Multiverse to be identical to the spawn we have set with our other plugin. You can do this by moving your character in game to the position you want to set the spawn, run /mv set spawn to set the Multiverse spawn position, then without moving your position or camera angle, run the command to on your other plugin to set the spawn on it.
To test it, move to somewhere else in the world and teleport out and back to it. Double-check the logs to see if it detects correctly now or if it still thinks the locations are different. If it does still think they are different, you can ask for help as mentioned above.
Extra info
The Spigot API doesn't make a distinction between a teleport to a world with a specific destination (ex. /tp player1 player2 if it goes to another world) and a teleport to a world without a specific destination (ex. /mv tp player1 world). This means that in order to tell if we should redirect a player to their last location, we need to check if they are getting sent to that world's spawn.
However, other plugins that can set spawn often do so without changing the world spawn on Spigot or Multiverse. This creates a disconnect where the other plugin sends you to its spawn location, but that location is different from what Spigot or Multiverse reports.
Return to your last location when returning to a Multiverse world
By default, when one switches between multiverse worlds, they are always spawned at the destination world's spawn. This could be particularly annoying to players - instead of returning to a world and resuming where they were, they have to walk from spawn to their last location first.
This plugin fixes that by keeping track of your last location in a world and making sure you return there.
The Remixed fork was created after the original author dropped support and other forks introduced problematic solutions. Remixed aims to keep the original vision of the plugin while fixing issues and keeping it updated.
Install
This plugin uses a database. MariaDB is recommended but MySQL works too. If you don't have a DB server you can also just use SQLite, which saves the DB to a file in your plugins.
To install, download the jar and put it in your plugins folder.
Make sure users have the stayput.use permission or their teleports will not be recorded! In most cases, you will want to apply the permission to the default user group.
Configuration
The configuration file is automatically generated the first time the plugin is run. You can also view the file for the current version here. The file should be called config.yml and be placed in the StayPut folder inside your plugins folder.
Commands
- /stayput reload - Reload the config file (Requires the stayput.admin permission)
Permissions
- stayput.use - Allow a player to use the StayPut plugin, if the player doesn't have this plugin it will not be teleported. Make sure the players/groups that need to be recorded have this.
- stayput.admin - Allows the usage of the /stayput reload command.
Help, I'm still getting teleported to spawn!
This usually happens because another plugin other than Multiverse is currently in charge of your world's spawn location. Turn on debug mode in the config.yml and look at the server console when you teleport. You might see something like this.
[StayPut] PlayerName: world1 --> world2
[StayPut] Not redirecting teleport because the destination appears to be a specific location in the world.
[StayPut] Location{world=CraftWorld(name=world2),x=0.5,y=135.0,z=0.5,pitch=0.0,yaw=-180.0} != Location{world=CraftWorld(name=null),x=0.0,y=135.0,z=0.0,pitch=0.0,yaw=0.0}
In this instance, we can see that the teleport took us to that first location on the third line. But, Minecraft reported the world spawn as that second location and we can see that the x, z, and yaw were different.
In order to fix this, we need to set the world spawn with Multiverse to be identical to the spawn we have set with our other plugin. You can do this by moving your character in game to the position you want to set the spawn, run /mv set spawn to set the Multiverse spawn position, then without moving your position or camera angle, run the command to on your other plugin to set the spawn on it.
To test it, move to somewhere else in the world and teleport out and back to it. Double-check the logs to see if it detects correctly now or if it still thinks the locations are different. If it does still think they are different, you can ask for help as mentioned above.
Extra info
The Spigot API doesn't make a distinction between a teleport to a world with a specific destination (ex. /tp player1 player2 if it goes to another world) and a teleport to a world without a specific destination (ex. /mv tp player1 world). This means that in order to tell if we should redirect a player to their last location, we need to check if they are getting sent to that world's spawn.
However, other plugins that can set spawn often do so without changing the world spawn on Spigot or Multiverse. This creates a disconnect where the other plugin sends you to its spawn location, but that location is different from what Spigot or Multiverse reports.
Resource Information
Author:
----------
Total Downloads:
4,625
First Release:
Jul 21, 2019
Last Update:
Nov 16, 2025
Category:
---------------
All-Time Rating:
Find more info at github.com...
13 ratings
Version
-----
Released:
--------------------
Downloads:
------
Version Rating:
----------------------
-- ratings