Actual version: 13w07a (wouldn't let me submit with this as the version, so I picked the closest match)
I didn't think anything of it at the time, but the world quit loading for some reason very near my base (once I got there). Anyway, I go in my base to sleep to set my spawn & At first I was having trouble with breaking blocks and my sprinting not appearing to be as fast. It started to rain, so I went to sleep, but when I press "Leave Bed", I can't it won't let me. It doesn't leave me lying in bed, but it doesn't stand me up. I couldn't press Esc to reach the menu to quit the game either. After a friend came and tried to help (he broke the bed & the block I was on/in and it did nothing to release me (though I still fell down to the next block below (I'll get to that in a moment))), I had to hit Ctrl+Alt+Del to manually quit the game (when I logged back in, I was suffocating in the block I should have been standing on; good thing my friend was still there to help). Because this happened before, I hit F11 to release full screen and exited the game via the "X" button.
The layout of my bed allows me to spawn in one of 3 blocks from the head of the bed to past the foot of the bed on the right side (usually next to the head of the bed). I have a secret chest (or had a secret chest) 2 blocks underneath my bed and a way to get up and down using ladders on the side of the blocks below where I have wool covering it. When I first hit "Leave Bed", it seemed to put me on the top of one of the ladders.
Final notes: I did a search for this bug in Minecraft (saw something similar in Pocket Edition, but that's not the same) & found nothing... Also checked for any mention of this in the bug fix list of the latest snapshot releases and saw nothing even mentioning beds.
Oh, and from what I can figure, this appears to be client side & probably rare, but serious.
PS: I don't control which update we run, so suggestions I update will be ignored
Related issues
Comments
migrated
vashts240
I updated everything to conform with the latest incident (which is recorded). I'll be posting the video shortly.
migrated
try reloging in mc or re download the launcher
vashts240
re-logging works, BUT it is still a bug. It still needs to be re-opened and properly looked at and fixed, not given a generic 'do this to fix it when it happens'. It's VERY annoying to have to F11 or Ctl-Alt-Del, close, re-open, re-launch SMP (and, if needing to get back to items before they despawn, this is valuable time being wasted)
vashts240
http://youtu.be/P6jDc9bdozg (video relating to bug)
vashts240
http://youtu.be/m1BBhdTIjI0 (new video relating to bug, 1.6.2)
vashts240
Would like to add additional comment: may not necessarily be sleeping in a bed per say, but there is a core issue (that several Mindcrackers experience and show in video) that has some of the basics to this (notably, the chunks stop loading and the player has to re-log).
Even if it means getting marked as a duplicate bug (to something that is different that what is currently reported as duplicate, as I believe there is some non-duplication (and this is an older bug)), can this, at least, be linked to a duplicate that someone is working on for the same basic premises (and to reference the potential risk a player has of sleeping in a bed when this bug happens)?
vashts240
this issue seems to have happened in Etho's latest Mindcrack video afaict (ct: can tell). Ep154 apx 19 minutes in.
this issue IS NOT the same as MC-38740 (this happens in pure vanilla) and this issue was created LONG before that one anyway (if anything, THAT issue should have been marked as duplicate).
if this issue is a duplicate of anything, it's the constant server bug that keeps happening to many Mindcrackers where the world just stops loading.
PS: please use logic when determining what are duplicates because issues reported 1st don't duplicate later issues. I'm getting REALLY fed up with NO responses to my comments on what is CLEARLY an issue that STILL EXISTS!!!!!!!!!!
PPS: I'm being really nice and friendly right now...
>:(What really irks me right now is the issue this has been marked as a duplicate of is from a modded client and my issue here IS VANILLA! Also, this was reported 1st. Because it has been falsely marked as duplicate, I cannot be sure if it has actually gotten fixed behind the scenes or if it's still an issue. It is rare, and it is serious.
I JUST WANT AN ANSWER TO KNOW IF I HAVE TO WORRY ABOUT THIS ANY MORE* or if it's still an issue that will never get resolved because no one listens to the little guy.
*specifically, confirmation that it has been fixed or is now made aware that someone goofed on marking this as duplicate of the wrong bug (I otherwise have no faith in this system to catch all major bugs because of the fiasco that has occurred/is occurring here).
Version 13w07a is obsolete. If this happens in the newest Snapshot, feel free to open a new ticket.