- This topic has 11 replies, 4 voices, and was last updated 3 months, 2 weeks ago by
.
-
Posts
-
Normal logoffs in specific locations result in resends back to spawn area on next login.
You need to login in order to like this post: click here
Really? That is weird. It shouldn’t be doing that. That happens if your bed was destroyed I think. I’m going to check.
You need to login in order to like this post: click here
Yep. You’re right. Dying currently brings you back to the main spawn point. I’ll look into this more.
You need to login in order to like this post: click here
Seems like whatever did this is also the reason people have been getting knocked back all over recently.
You need to login in order to like this post: click here
Wow, so its happening on OG mesecraft too? Players on Centeria have been complaining about this…
You need to login in order to like this post: click here
let me know if you find a solution!
You need to login in order to like this post: click here
Yeah, I go exploring, set my spawn location and then die 2 minutes later, but I end up back at Portbarrow
You need to login in order to like this post: click here
Did you have to reset server ? Everything is new!
You need to login in order to like this post: click here
The server was being very buggy for certain users. When I logged in as “Komodo” I could not even get the map to load. I was stuck on the same chunk as spawn and could not go anywhere. After I reset the game, it worked again OK. I think maybe there was corruption in the world somehow. How is it working for you?
You need to login in order to like this post: click here
I guess you had to reset the server. Everything is new again!
You need to login in order to like this post: click here
RE the respawn bug, I have a hypothesis that it occurs if the game cant find your bed because it was dug since the last time you slept in it
You need to login in order to like this post: click here
The re-spawn bug is resolved. There was some sort of database corruption for users or beds or something it was odd. Fixed by a world reset on the server.
You need to login in order to like this post: click here
- You must be logged in to reply to this topic.