Can't find what could have led to the crash but I was putting 2 coal in a furnace after I had already inserted 11 Iron, for some reason It can't be replicated, If anyone can replicate this crash It will be great since 1.8 is released Monday and we need the least amount of possible patches, and we need to get every glitch/crash/Code fail out before the first patch is finished. Also I just woke up so my usual sophisticated act isn't on yet.
soooooo get to et!
soooooo get to et!
11
I found 2 villages in my new generated world
I have yet to find a village, Tons of ravines, just no villages as of yet,
I've had multiple crashes, all of them relating to the furnace in some sense or the other. Sometimes when I'm putting in fuel, sometimes when I'm putting in ore. Oh, and if you leave items on the crafting table and walk away, it'll kick the items out and you can't always pick them up again. But when you CAN, they become perma-items. Probably not what was intended. Oh, and if you put the perma-items into the furnace, that'll cause a chunk crash.
Ahhh ok now I can replicate it... I see what the problem is, just gotta handle crafting tables and furnaces very carefully until the update.
hey guys.,,,find any villages..can i have the seeds?
ahhh well that's odd since it hasn't happened again, can't make it happen again, kinda wierd
I have the same poblem
This appears to actually not happen on Multiplayer, which is weird since MP is generally buggier than SP. But ye on the one Multiplayer 1.8 Server I've been on nothing's crashed, just a server-wide shutdown caused by an NPC village.
thats weird i never crash and i have alot of furnances in my house
dont use the furnace it crashes the game
i have this problem anytime the fuel for a furnace is empty. as soon as i put fuel in, the game crashes. it works after i open it again and start playing the world again, but as soon as i run out of fuel (Coal), then it will crash again when i put more in, Assuming it is instantly used.
You're not the only one that has the problem so I'm sure the bug has been reported.
You're not the only one that has the problem so I'm sure the bug has been reported.
