Mod note
The debug world is only for observing how all the blocks in all their possible states render, generally for testing resource packs. You're only supposed to be in spectator mode in the debug world.
So:
Take note of the 2000 entities, this is caused by me walking into and through (continuously) some golden pressure plates. I'm assuming this is relevant to a block update or something which is getting triggered, its thinking it should break the plate but it's being put back by the protection?
Not sure exactly, i'm sure you know what it is - but it's making a hell lot of entities drop as well as a horrific sound generally meaning crash and world has to be deleted.
Comments
migrated
rene_z
Also happens when toggling some of the comparators (the ones that point at another comparator).
This happens because the block gets updated, notices that it shouldn't float in air, drops its item and gets immediately reset by the debug world. Then the new block gets updated on placement, causing an (almost) infinite loop. Sometimes you can break out of the loop, sometimes you can't.
A solution would be to automatically disable block drops in a debug world or not letting the player interact with any blocks (although accessing chests etc. would be useful when this is used for testing resource packs).
Also, Mojang already knows about that "bug":
"Added new world generator for debugging, useful for resourcepack makers (hold shift and cycle through “World Type” to select it. Spectator mode recommended, it may crash otherwise.)" (https://mojang.com/2014/06/minecraft-snapshot-14w26a/)
migrated
They updated that after I made this report. More precisely when they updated to 26b. I wrote this at 26a.
migrated
ironic, debug mode is surprisingly buggy
migrated
I'm bewildered by the fact this has been set to "Wont Fix" why wont they fix it?
It's a bug which caused several thousand entities, the fact its been echoed by multiple people and effects several people makes me think its worth fixing?
Ezekiel
You should use spectator mode in debug mode
migrated
They say they suggest using it, not that you have to use it.
Also if something is a possibility, then its a bug. They shouldn't rely on users changing their gamemode in response to a bug issue being reported by multiple people.
Ezekiel
I'd also like to point out there's a reason it's only accessible by shift clicking the world menu, it's not supposed to be used by regular players.
migrated
Whether you have to shift click to be able to access the world or not, it's still a feature which can be accessed by everyone. it shouldn't be a mandatory action to have to be in spectator mode. If it is, then it should be done by default and not yet another action in order to prevent bugs (of which this is a valid bug)
migrated
Fixed as of 14w26c
migrated
Not for me it aint? Note it doesn't work on all of them, only the end one it seems.
migrated
Fixed!? No, sorry - and I was running out of memory too! 😞
Tested on two OSes.
Windows 7 x64 - Bug present
Ubuntu 14.04 ("Trusty Tahr") - Bug Present
migrated
Can you add a video showing you causing the chain reaction?
migrated
Think my explanation was satisfactory, but here you go:
http://gfycat.com/ClumsyEnergeticFlicker
As good as I can get. But literally, find the golden plates the one on the far left, walk into it (or drop an entity on it like a mob with a spawn egg) and boom bada bing your game crashes or your stuck with 0fps due to several thousand entities.
migrated
Resolved due to the forced spectator mode.
migrated
indeed resolved because of spectator mode
Torabi
migrated
@Torabi That sounds more like causing lag on purpose to me.
kumasasa
Invalid.
The debug world is only for observing how all the blocks in all their possible states render, generally for testing resource packs. You're only supposed to be in spectator mode in the debug world.
That the gamemode is not locked on spectator mode is noted here MC-60033.
migrated
16869 Entities in 5 seconds, New Record ! (MC-82492)
Seriously, this is NOT fixed.
migrated
You're only supposed to be in spectator mode in the debug world.
That the gamemode is not locked on spectator mode is noted here MC-60033.
Won't Fix
Bugs like this in the Debug World are not being tracked.
That's your own fault then.
Confirmed