Cuberite Forum
Respawn point after death - Printable Version

+- Cuberite Forum (https://forum.cuberite.org)
+-- Forum: Cuberite (https://forum.cuberite.org/forum-4.html)
+--- Forum: Discussion (https://forum.cuberite.org/forum-5.html)
+--- Thread: Respawn point after death (/thread-1805.html)



Respawn point after death - Sunri5e - 02-26-2015

Hi there,

after i die, i will be respawn at the default respawn point (X=0,Y=65,Z=0) instead my world.ini spawn point.
The command /spawn will get me to my spawn point.

Why does this happen?

Sunri5e

P.S: Sry for my english...


RE: Respawn point after death - NiLSPACE - 02-26-2015

The Core saves the coordinates in memory when using /setspawn and updates the world.ini file, but those actions won't have any effect for the world until the server restarts. The /spawn command works because it uses the coordinates saved in memory.

Try restarting your server. That should fix it.


Notes for MCS team
We should probably add a cWorld::SetSpawnXYZ function. If we were to add it would we also make it update the ini file?


RE: Respawn point after death - Sunri5e - 02-26-2015

Doesn't work. Spawn point is still the default one...


RE: Respawn point after death - NiLSPACE - 02-26-2015

Weird. Then I suggest you open your world.ini and change the coordinates manualy in <worldname>/world.ini->[SpawnPosition]->X, Y and Z. After that start or restart your server.


RE: Respawn point after death - NiLSPACE - 02-26-2015

Hmm.. Weird. I checked if it worked for me, and I'm still send to the initial spawn coordinates. You might have found a bug.


RE: Respawn point after death - NiLSPACE - 02-26-2015

Oh. I think I found the problem. In the user file the bed coordinates of a player is saved. If you didn't sleep in a bed then the coordinates are set to the worlds spawn coordinates. But since the coordinates aren't changed when the worlds spawn point is changed you still end up at the old world coordinates.


RE: Respawn point after death - tonibm19 - 02-26-2015

I already knew that bug.

Until it's fixed, you could try using the Fixes plugin I made some time ago, wich should fix the issue.

https://github.com/tonibm19/Fixes