Multiverse / Multiverse-Core

The original Bukkit Multi-World Plugin!
BSD 3-Clause "New" or "Revised" License
960 stars 298 forks source link

[Bug]: Vanilla `/spawnpoint` does not change player’s spawn #3089

Open 6ins opened 3 months ago

6ins commented 3 months ago

/mv version -p output

https://paste.gg/p/anonymous/a446a92ecb84427cb62ad8eeba06ed68

Server logs

https://mclo.gs/CxGRR6e

Server Version

This server is running Paper version 1.21-104-master@9aea240 (2024-07-20T20:07:24Z) (Implementing API version 1.21-R0.1-SNAPSHOT)
You are 26 version(s) behind
Download the new version at: https://papermc.io/downloads/paper
Previous version: 1.21-78-ef96a69 (MC: 1.21)

^ This was ran today,

Bug Description

(Copy-pasted from Discord, this info is about two weeks old but still valid aside from some paper updates)

Upon installing Multiverse Core, /spawnpoint command does not function, instead being replaced with whatever the multiverse world spawn is.

Steps to reproduce

  1. Start a server with only Multiverse Core installed
  2. Set a player /spawnpoint
  3. Kill the player

Agreements

zax71 commented 3 months ago

What plugin is /spawnpoint from?

6ins commented 3 months ago

It's a Vanilla Minecraft command

zax71 commented 3 months ago

Oh, so it is well I never knew that. We’ll have to look in to what events that calls and maybe implement something

6ins commented 3 months ago

I am pretty sure it is related to something regarding 1.21, as I did not have this issue in 1.20.x

zax71 commented 3 months ago

That’ll be useful info for reproducing this. Ty

Craft374 commented 2 months ago

I have this problem too

Coolreindeer100 commented 2 months ago

same problem here. my parkour uses /spawnpoint and the command block is saying that it has saved my spawn to x y z location but when i die i spawn at the mv spawn which is the place where when i type mvsetspawn x y z i spawn.

donutStudio commented 1 month ago

I am pretty sure it is related to something regarding 1.21, as I did not have this issue in 1.20.x

i recall having this issue before 1.21 as well but im not entirely sure