Hey. Made a survival map with MCEdit, you can play it with no problems. But when you die, you generate new chunks and spawn on them. You are actually supposed to spawn on a ball high up in the air. I used a premade map, which is an empty map with no other blocks than the ball. The spawnpoint is on the ball. Why does this happen? And why doesn't monsters or animals spawn on the sphere? They only spawn if I use monsterspawners. And also, the spawn works just fine in multiplayer, but not singleplayer.
Hey. Made a survival map with MCEdit, you can play it with no problems. But when you die, you generate new chunks and spawn on them. You are actually supposed to spawn on a ball high up in the air. I used a premade map, which is an empty map with no other blocks than the ball. The spawnpoint is on the ball. Why does this happen? And why doesn't monsters or animals spawn on the sphere? They only spawn if I use monsterspawners. And also, the spawn works just fine in multiplayer, but not singleplayer.
Minecraft won't respawn you below elevation 64. Instead, it will move your spawn point to the nearest suitable spot and respawn you there. Maybe there are some other restrictions on where you can respawn? Try experimenting with different spawn locations and get back to me on what works and what doesn't.
Minecraft won't respawn you below elevation 64. Instead, it will move your spawn point to the nearest suitable spot and respawn you there. Maybe there are some other restrictions on where you can respawn? Try experimenting with different spawn locations and get back to me on what works and what doesn't.
I've tried to put the spawnpoint as high as possible, but still respawned in random chunks when you die... See my signature and download the map and test it, works good in multiplayer :/
Minecraft won't respawn you below elevation 64. Instead, it will move your spawn point to the nearest suitable spot and respawn you there. Maybe there are some other restrictions on where you can respawn? Try experimenting with different spawn locations and get back to me on what works and what doesn't.
Another (seemingly arbitrary) condition is that you always first spawn on sand. I'm not sure if this is the problem here, but it's possible.
I only know this because it was causing a game-breaking bug when I removed sand from world generation. >_>
Rollback Post to RevisionRollBack
I had a mod back in Beta 1.8.1, but I quit for a while so it hasn't been updated since then. WTF <-- If you'd like to try and update it, let me know. (It won't be an easy task, I'm sure)
But why does it work for Multiplayer then? :/ Anyone who knows how to fix this?
Spawning is likely handled differently for multiplayer. I haven't actually looked at the server code at all.
Rollback Post to RevisionRollBack
I had a mod back in Beta 1.8.1, but I quit for a while so it hasn't been updated since then. WTF <-- If you'd like to try and update it, let me know. (It won't be an easy task, I'm sure)
I looked at the server sources and it turns out that you spawn within 20-30 blocks of the single player spawn and on any thing that is considered a block I.E. water but not torches but in single player you can only spawn on sand and above level 64
EDIT: if any of you ask yes i am a modder
http://pcpartpicker.com/p/2kUq0
the average script-follower/lack of common sense: http://www.techtales.com/tftechs.php?m=200504#8418
windoge 8 has the saddest excuse for a BSOD, it just tells you the type of error, no stop code, no nothing, just "something went wrong, all your unsaved work has now been lost to the void that is volatile memory"
I figured it out a while back. I was wrong about the spawn point needing to be at h=64.
There is a really weird rule for a valid spawn point. Minecraft looks at the column the spawn point is in and tries to find the top of the terrain by starting at y=63 and going upward, counting the solid blocks.
What happens is that if y=63 and y=64 are both empty, Minecraft thinks the entire column is empty and moves your spawn point elsewhere. When I found this out, I changed MCEdit to offer to fix the column for you if you try to put your spawn point in a place where Minecraft would reject it.
(This stuff applied to Beta 1.8.1. Not sure if the rule changed for 1.0.0)
Are you playing on 1.8?
Nope. Playing 1.7.
EDIT: I think t=when you select a place to spawn then you spawn somewhere in that chunk (i might be wrong)
"We will absolutely not keep in mind what external mapeditors will have to do to read data from the disk, that makes no sense whatsoever." - Grum
I've tried to put the spawnpoint as high as possible, but still respawned in random chunks when you die... See my signature and download the map and test it, works good in multiplayer :/
Another (seemingly arbitrary) condition is that you always first spawn on sand. I'm not sure if this is the problem here, but it's possible.
I only know this because it was causing a game-breaking bug when I removed sand from world generation. >_>
I had a mod back in Beta 1.8.1, but I quit for a while so it hasn't been updated since then.
WTF <-- If you'd like to try and update it, let me know. (It won't be an easy task, I'm sure)
But why does it work for Multiplayer then? :/ Anyone who knows how to fix this?
Spawning is likely handled differently for multiplayer. I haven't actually looked at the server code at all.
I had a mod back in Beta 1.8.1, but I quit for a while so it hasn't been updated since then.
WTF <-- If you'd like to try and update it, let me know. (It won't be an easy task, I'm sure)
Nobody knows.
You will be the first to figure this out.
"We will absolutely not keep in mind what external mapeditors will have to do to read data from the disk, that makes no sense whatsoever." - Grum
Why would nobody know?
EDIT: if any of you ask yes i am a modder
http://pcpartpicker.com/p/2kUq0
the average script-follower/lack of common sense: http://www.techtales.com/tftechs.php?m=200504#8418
windoge 8 has the saddest excuse for a BSOD, it just tells you the type of error, no stop code, no nothing, just "something went wrong, all your unsaved work has now been lost to the void that is volatile memory"
There is a really weird rule for a valid spawn point. Minecraft looks at the column the spawn point is in and tries to find the top of the terrain by starting at y=63 and going upward, counting the solid blocks.
What happens is that if y=63 and y=64 are both empty, Minecraft thinks the entire column is empty and moves your spawn point elsewhere. When I found this out, I changed MCEdit to offer to fix the column for you if you try to put your spawn point in a place where Minecraft would reject it.
(This stuff applied to Beta 1.8.1. Not sure if the rule changed for 1.0.0)
"We will absolutely not keep in mind what external mapeditors will have to do to read data from the disk, that makes no sense whatsoever." - Grum