-
Notifications
You must be signed in to change notification settings - Fork 301
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Vanilla /spawnpoint
does not change player’s spawn
#3089
Comments
What plugin is /spawnpoint from? |
It's a Vanilla Minecraft command |
Oh, so it is well I never knew that. We’ll have to look in to what events that calls and maybe implement something |
/spawnpoint
does not change spawn
/spawnpoint
does not change spawn /spawnpoint
does not change player’s spawn
I am pretty sure it is related to something regarding 1.21, as I did not have this issue in 1.20.x |
That’ll be useful info for reproducing this. Ty |
I have this problem too |
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. |
i recall having this issue before 1.21 as well but im not entirely sure |
I am having this issue aswell, breaks a lot of "checkpoints" and minigames on my server. This all started back on the release of 1.21 as far as I know. Is this issue being worked on? |
/mv version -p
outputhttps://paste.gg/p/anonymous/a446a92ecb84427cb62ad8eeba06ed68
Server logs
https://mclo.gs/CxGRR6e
Server Version
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
Agreements
The text was updated successfully, but these errors were encountered: