
[Bug]: `/mv regen -s` command does not update the world's `spawnLocation`
jfoucher opened this issue ยท 0 comments
/mv version -p
output
Multiverse-Core Version: 4.3.1-b861
Server logs
N/A
Server Version
paper 1.20.4-499
Bug Description
I have a mining that I regenerate regularly so that the resources are replenished. I also change the seed so that the players can't remember where minerals are. For this purpose I use the command /mv regen mine -s
which works fine.
The problem is that as soon as I try teleporting in this world, either I get a "no safe location found" message, or I spawn in the middle of water or other unsafe places.
I gather that this is because the spawnLocation
in the worlds.yml config file remains unchanged after a regen.
I tried editing that file to remove spawnLocation
but it comes back (although more suited to the new world it appears)
I my mind, regenerating a world with a seed change should also reset the spawnLocation.
Steps to reproduce
- start a server with multiverse
- create a world
mv create another NORMAL
- teleport to it
mvtp another
- you are safe
mvtp world
/mv regen another -s
/mv confirm
/mvtp another
- you might get "no safe location found" or arrive in water or arrive on land.
Agreements
- I have searched for and ensured there isn't already an open or resolved issue(s) regarding this.
- I was able to reproduce my issue on a freshly setup and up-to-date server with the latest version of Multiverse plugins with no other plugins and with no kinds of other server or client mods.