Suffocation/jittering/stuck when spawning in a newly created world

Confirmed. I started creating a series of worlds, and after around 3 I spawned inside blocks suffocating. I jumped once and was met with the screenshot.

Basically, from top down, the blocks were:
Leaves on tree
Tall grass
Grass block
Dirt block (I spawned with my feet in this one)

This doesn't happen with plains biomes. I'm in the process uploading a video showing that it will happen on almost every world generation. SOME island types will not have this issue. Also, you can spawn underwater and in rivers. And it's NOT always suffocation.

Edit: http://www.youtube.com/watch?v=p8eLjY4hNeE&hd=1 (Video - it may be 9+ minutes, but it's for each variation of the bug. May have to wait for HD to process.)

Can I request that this bug be upgraded to a major bug because of the suffocation issues? If so, I would like to request that this bug be upgraded because of that.

It is VERY annoying in Hardcore world!

And yet, Mojang has no plans to fix it ever yet. (1.4.5 shows such it seems.) The bug shouldn't be simply named "Suffocation when spawning--" it should be "Player 'stuck' in blocks when spawning in newly created worlds."

Affects also 1.4.5

Game mode: survival and creative

Seed "80000000008" (worked fine with 1.4.2)

Biome: "Plains"

Players stuck in ground and bounces.

This happens a lot more (50% of all new worlds I start) with the 1.4 series where I didn't have them before (<1.4). My OS = OX X 10.8.2. Java: 1.6.0_37

Seed -6805991508691440641 can/will spawn you in water after breaking the block you spawn in or on. The bug may be caused by improper spawn fixing / updating.

@Ian Carlson: Do you mean when you die and respawn, or in some other more specific circumstances?

If it's when you die and respawn, this may be intended, although the Minecraft Wiki does state you should respawn in a position above sea level. The fact that you're respawning in water may need the creation or alteration of another bug report to handle that because it's not actually directly related to the suffocation issue.

Your default spawn on creating a new world can land you in water, although perhaps a lot more rarely nowadays than it used to. It is, however, still possible to spawn, and therefore respawn, above water on creation of a new world, even if the generated spawn point in the map file is under or at the surface of land nearby.

Respawning only seems to pick an x/z pair of coordinates within 25 tiles of your spawn point, not place you at the first point you actually spawned at on a map.

well, it's possible that the spawn was meant for right above the water, and that due to the bug here, the "fixed" spawn was in sand / whatever. When breaking the sand, the spawn reverted back to its "un-fixed" state. iirc, Jeb / etc. are still trying to fix all the water spawns. Some DO spawn you UNDER sea level though still, although rarer than over water spawns.

I suggest you do some experimentation and see if you can separate the spawning/respawning in water issue from the stuck in block issue, because I think they may really be two separate issues. If that really is the case, simply create a new issue regarding the spawning/respawning in water and see how it gets categorized, maybe it's intended behavior, maybe not.

I'm pretty sure this is related to the spawn/join protection being removed (or reimplemented in a different fashion?). If someone fills an area with stone (for example) while you are offline, then when you join, you will be in the blocks and taking suffocation damage. If the old join code were added back in, I'm pretty sure it would completely resolve this issue (and make logoutivators possible again, but some people like that part!).

@Colton: As far as I can recall, they have been taking out spawn protection for the last couple of updates now. Regarding the SMP part to which you appear to be referring, the post appears to imply that the original poster was recreating worlds in single player. If Ian is indeed experiencing this problem in SMP or SSP worlds other players can join, it shouldn't really matter, anyway, for if Mojang fixes this bug, it will be fixed for both cases, since the client already runs a local server.

If a player is indeed placing blocks at the spawn point when another player dies and tries to respawn there, there may have to be special case handling code that moves the player outside the area where the other player is placing blocks. At the very least, it should spawn the player just above the blocks, not in them.

I doubt any player seriously wanting to actually play with friends on a Minecraft server would have malicious intent towards any other players, however, the ban system already exists to deal with this particular aspect.

There is already code that handles players being pushed out of blocks. It still works too. For instance, if you put gravel or sand on top of you, and the game notices there's either half-slabs or air adjacent to you, it will push you out. Same goes for if you log out and come back in stuck in blocks (But again, half-slabs and air have to be adjacent. If it's solid walls on all four sides, then you're screwed. This is intended.)

@Geoffrey, Yes. I understand all of that. It used to be that when you spawn or join, Minecraft would find the closest 2-high set of airblocks above you (if you're in solid blocks) and place you there. This no longer happens, and IMO, is the cause of the issue. SSP is SMP (well, it is basically now).

And besides, a group of people could be landscaping where you are standing. And instead of standing in a plains biome, you are now suffocating inside a mountain. 😉 No malicious intent at all.

it happend to me only when i got the latest snapshot and updated again

Adjusted the title a bit.

I get this too. At first i though it was my mod but im getting this without them.
I spawn in the ground, variable in deep depending on the biome im in.

same here! although i get it whenever i join the world... and i loose my place because it spawns me SOMEPLACE IN a snow biome... i have single player commands and optifine but that wouldnt explain this... I hate this... im gonna start to have to leave minecraft open :/!!!! please fixxx!!!!

Can confirm this, too. Created a bunch of new worlds recently, and in a guesstimated 75% of all cases I either:

• spawned with my feet stuck in dirt, jittering up and down until I dug away the block I was stuck in (most biomes);

• spawned inside the ground and suffocated if I didn't dig up in time (jungle biomes); or

• spawned under water (island/ocean biomes), sometimes without any land in sight

I thought this was resolved in one of the 1.4.6 snapshots, but then it seems to be back in the full version of 1.4.6.

still present in 1.4.7 pre-release

Since snapshot 13w01b every time I create a new world I spawn stuck with only way to get out being /tp.
Java version 1.7.0_09-b05, Win7 x64, Minecraft 13w01b snapshot

Seems I can't edit the affected version, though I'd like to add that it also happens in the 13w02a snapshot.

the latest snapshot is the only time i've actually noticed this happening, have yet to have it happen in any worlds i have created fresh in previous versions.

Just wanted to confirm that the problem persists in 13w02a here.

I could just reproduce the "spawning inside block and suffocate to death" bug. I kept loading the same seed over and over again and noticed, that this only happened to me, when leaves were above me. It might be best to do that in a jungle biome: -6033174565279304444

Seems OK for me in 13w02b. Created several worlds, spawned under leaves and there was no problem.

The first world I created in 13w03a, I got stuck when first spawning in it. However, I did notice that my player character spawned before the terrain did and was immediately affected by gravity, and therefore I sort of 'fell' into a void where a block appeared a moment later when the chunk was finally drawn. Is it possible that the guys at Mojang can resolve this problem by simply 'freezing' the player for about a half-second when first entering a world (no movement, no gravity), to give the client a moment to spawn some solid ground where the player character can stand?

@Jay Eff, the reason why freezing the player could be difficult is due to an SMP version of the same map. If you froze a player, you'd pretty much freeze all players for that half-second unless you specifically wrote the code to handle the random entity id that players are given when they login to the server. But it's more than just that, you'd have to check to see if the player has never logged into the server before now, so that this bug can actually happen, as it doesn't happen any subsequent time after your first generation.

If you want to argue that the server admin / creator is the only one who will end up with this problem, that's not enough to make it so that you SHOULD NOT write such code to handle ALL players. Because it can always happen in the future I'm sure.

Always make more food than what you really are making for, just in case.

Don't freeze the client from the server, freeze the client from the client and let the server know what's going on... I used to mod a multiplayer Star Trek game where players could 'transport' to different areas of the game, and I had to code a 'freeze' into the client to create a transporter visual that hid the 'void' while the client loaded geometry and texture data for a different area of the map from their harddrive. The server received a 'transporting' flag from that client while he was transporting, so he couldn't be affected by gravity or be allowed to move and fall into the 'void', and so he wouldn't get ganked (temporary invulnurability) while waiting for the transporter event to complete. The player was allowed to move after the 'transporting' flag was cleared both at the client and server. Since the freeze was initiated from the client, then managed by both the client and server, it was very easy to match the server's client ID with the actual client that was transporting. That's the Cliff's Notes description, it's hard to explain but it was easy to do. Depending on how Minecraft is programmed, it should be pretty easy to freeze a single client for a moment while spawning into a new world.

ACTUALLY... If this problem ONLY happens on first spawn into a new world... Expand on the 'freeze' idea and create a short, fun, quirky, Minecraft-ian 'Welcome to new world' visual that fades into the game world while the player is frozen on first spawn. By the time the animation and fade has completed, most of the gameworld local to the client will have been loaded and it will definitely be safe to allow the player to unfreeze and stand on solid ground. A visual can be coded into Minecraft where others on the server will see a swirly teleport animation that 'poofs' into your player character once your player character is released from 'freeze' status. Then, every spawn afterwards, don't perform the animation.

I'm just trying to think of some fun easy things mojang can do, there's no sense in re-coding all things collision-related just to fix a first-spawn bug.

this happens some times on my sever when people get tpd to unloaden chunks.

it feels good with redstone

Happens very frequently in multiplayer as well. When I created a new world in 13w04a, I was jittering in a grass block in a forest biome.

it happens to me to, i spawn a new world and get glitched in a block and have to break it.

i created a ton of new worlds but i failed to reproduce it on 05b ... i know it can happen but i cant reproduce it

failed to reproduce on 06a, is it fixed?

I suggest taking a closer look at "Resolution" and "Fix Version" 😉

lol somehow this appeared in my inbox .. weird.

lol somehow this appeared in my inbox .. weird.

Where does it say it is fixed in 1.4.7? I would like to correct it.

Removed my previous comment. I misread the details.

Yes, I am experiencing it in 1.4.7 as well. Had been away from Minecraft for a few months, came back and downloaded the most recent version and noticed the problem immediately. This is running on OS X 10.6.8. Happens about 3/4 of the time when creating a new world, and I've noticed it in plains, jungle, forest, and mountain biomes.

this appears to still be present in 1.5.1, as evidenced by this video i recorded: http://youtu.be/utaKNBbt-8w