I was starting new games this weekend, trying to get one on islands so I could play an island hopping game.
One of the games, I actually started underwater. The screen came up and it was dark and at first I thought it was still loading, then I saw the little air bubbles disappearing. So I aimed "Up" and pushed forward and sure enough I got out of the water to find myself in a swamp.
But does this indicate there is something wrong with my Minecraft program and I should reload? Or does it really choose a location underwater to start a person on occasion?
It's perfectly normal. There are cases where it sometimes spawns you in the middle of a huge ocean with no land for a very long distance. Be glad you didn't get that.
It's perfectly normal. There are cases where it sometimes spawns you in the middle of a huge ocean with no land for a very long distance. Be glad you didn't get that.
Yikes! I guess I've just been lucky. The closest to this I've gotten is the occasional small island in the middle of the ocean (Which was basically what I was looking for in starting and restarting)
This is normal. The game doesn't care (or sometimes even know) what is there when it selects a spawn point for you. I've spawned in water, in mid-air over a ravine, and in one of my modded worlds I even spawned in dead because an AE2 meteor was placed right next to where I spawned (broke the bonus chest and everything).
The game has several measures in place to make sure that you do not spawn in an ocean although it can fail if the ocean is large enough; first, it checks for a plains, forest, jungle, or taiga within 256 blocks of the origin (0,0) and sets the world spawn point at a randomly chosen spot (sort of, it favors locations towards +x and +z) within one of these biomes (these biomes have not been changed since before 1.7) if it find a grass block at y=63 or higher (note - sea level is at y=62 in terms of the highest water block), otherwise, it will move the spawn point in a random walk until it finds one; however, this not however consider features that generate after the terrain does, such as water and lava lakes.
If you create a new world and happen to spawn right at or very close to 0,0 (note - the player's spawn point on each respawn is randomized within a 20x20 block area around the exact world spawn point, so it can spawn you over things like ravines, though I've always spawned at the bottom, not in mid-air) this is because it could not find one of the aforementioned biomes, but a biome covered in grass was at 0,0. If the game takes longer than usual to create a new world and you spawn much further away, sometimes 1000 blocks or more, then it is because there was an ocean or very large desert around the origin and the game makes up to 1000 attempts at finding a chunk with exposed grass before giving up; this was much more common prior to 1.7 due to the much larger oceans, as well as with larger biomes (Large Biomes or Customized).
Here is an example of what the game does in the worst-case scenario, using the seed "-1984348358409562691" (default) in 1.6.4:
The world spawn point is at the center of the big square on the left side, while the origin is near the right side, with a trail of chunks leading away from it. A few chunks did land on some exposed seafloor (1.6.4's version of "islands" in oceans) and a couple Mushroom Islands but neither were seen as valid spawn points.
I was starting new games this weekend, trying to get one on islands so I could play an island hopping game.
One of the games, I actually started underwater. The screen came up and it was dark and at first I thought it was still loading, then I saw the little air bubbles disappearing. So I aimed "Up" and pushed forward and sure enough I got out of the water to find myself in a swamp.
But does this indicate there is something wrong with my Minecraft program and I should reload? Or does it really choose a location underwater to start a person on occasion?
It's perfectly normal. There are cases where it sometimes spawns you in the middle of a huge ocean with no land for a very long distance. Be glad you didn't get that.
My Survival Island map: http://www.minecraftforum.net/forums/mapping-and-modding/maps/2734254-survisland-a-simple-survival-island-map-1-8
Looking for some help developing this mod (I'm new to modding): http://www.minecraftforum.net/forums/mapping-and-modding/minecraft-mods/wip-mods/2769007-the-bucketeer-mod
Yikes! I guess I've just been lucky. The closest to this I've gotten is the occasional small island in the middle of the ocean (Which was basically what I was looking for in starting and restarting)
This is normal. The game doesn't care (or sometimes even know) what is there when it selects a spawn point for you. I've spawned in water, in mid-air over a ravine, and in one of my modded worlds I even spawned in dead because an AE2 meteor was placed right next to where I spawned (broke the bonus chest and everything).
Yesterday one of my friends spawned inside of a mooshroom and suffocated to death.
my current world has half of the spawn area underwater lol
The game has several measures in place to make sure that you do not spawn in an ocean although it can fail if the ocean is large enough; first, it checks for a plains, forest, jungle, or taiga within 256 blocks of the origin (0,0) and sets the world spawn point at a randomly chosen spot (sort of, it favors locations towards +x and +z) within one of these biomes (these biomes have not been changed since before 1.7) if it find a grass block at y=63 or higher (note - sea level is at y=62 in terms of the highest water block), otherwise, it will move the spawn point in a random walk until it finds one; however, this not however consider features that generate after the terrain does, such as water and lava lakes.
If you create a new world and happen to spawn right at or very close to 0,0 (note - the player's spawn point on each respawn is randomized within a 20x20 block area around the exact world spawn point, so it can spawn you over things like ravines, though I've always spawned at the bottom, not in mid-air) this is because it could not find one of the aforementioned biomes, but a biome covered in grass was at 0,0. If the game takes longer than usual to create a new world and you spawn much further away, sometimes 1000 blocks or more, then it is because there was an ocean or very large desert around the origin and the game makes up to 1000 attempts at finding a chunk with exposed grass before giving up; this was much more common prior to 1.7 due to the much larger oceans, as well as with larger biomes (Large Biomes or Customized).
Here is an example of what the game does in the worst-case scenario, using the seed "-1984348358409562691" (default) in 1.6.4:
The world spawn point is at the center of the big square on the left side, while the origin is near the right side, with a trail of chunks leading away from it. A few chunks did land on some exposed seafloor (1.6.4's version of "islands" in oceans) and a couple Mushroom Islands but neither were seen as valid spawn points.
TheMasterCaver's First World - possibly the most caved-out world in Minecraft history - includes world download.
TheMasterCaver's World - my own version of Minecraft largely based on my views of how the game should have evolved since 1.6.4.
Why do I still play in 1.6.4?
ohhh that explains some random chunks i got in a water world i got in the generator
I created a *custom* (Frozen Ocean) world the other night and spawned under water. At least the water above my head was clear of ice!
I think I've only spawned in the ocean once or twice, and both times, there was an island nearby. I've spawned in rivers probably at least four times?
But I'm disappointed, because I thought this thread would be about how to actually start with an underwater base.