I have now encountered two different dungeons in two different worlds that had empty spawners (please see attached pictures.)
They did not appear to contain a chest of any kind, although, in the second one, I mined the mossy stone blocks and one of them threw up wooden chips and made the sound of wood being broken/chopped (please see attached pictures). At first, I assumed that this was yet another bug, but, when the block was finally mined, a chest appeared, which suggests to me that one of the blocks (at floor level, as in, in the floor, not on it), was an empty chest despite looking like a mossy stone block.
Linked issues
is duplicated by 10
Attachments
Comments 111

Can confirm on 0.10.5.
Can confirm on 0.10.5.
Confirmed for 0.11.1 on iPhone 6 plus (iOS 8.3). Attempting to reprogram the spawner with a spawn egg causes it to disappear.
It is the same in the windows 10 edition.
Also happens in the nether, there are some locations with invisible blocks that might be chests inside fortresses and the blaze spawners are empty.
It is the same in the windows 10 edition.
Also happens in the nether, there are some locations with invisible blocks that might be chests inside fortresses and the blaze spawners are empty.
Confirmed 0.12.1 Build 8 !
Confirmed 0.12.1 Build 8 !
Same for me 0.12.1 Build 9. I believe the cheat have been fixed for this version but the spawners in the nether aren't. Fix?
Same for me 0.12.1 Build 9. I believe the cheat have been fixed for this version but the spawners in the nether aren't. Fix?
Can confirm in 0.12.2 Windows 10 edition as well, spawners in nether fortress are empty...
Can confirm in 0.12.2 Windows 10 edition as well, spawners in nether fortress are empty...
Found same thing in windows 10 edition. I could still destroy the invisible chests, but could not open them. Putting a chest beside an invisible chest (tried every possible orientation) does not create a wide chest.
Found same thing in windows 10 edition. I could still destroy the invisible chests, but could not open them. Putting a chest beside an invisible chest (tried every possible orientation) does not create a wide chest.
I'd like to put emphasis on the importance of this issue. This has gone on for almost a month for me. No matter what device I use, installing on a device that's never had the game yet or reinstalling on the other devices that already have it, the chests are all invisible and monster spawners are broken. This being Windows 10 Edition (latest build available as there are no updates available in the store for me).
If a future fix is implemented, will worlds I've already created have to be scrapped to get it going?
I'd like to put emphasis on the importance of this issue. This has gone on for almost a month for me. No matter what device I use, installing on a device that's never had the game yet or reinstalling on the other devices that already have it, the chests are all invisible and monster spawners are broken. This being Windows 10 Edition (latest build available as there are no updates available in the store for me).
If a future fix is implemented, will worlds I've already created have to be scrapped to get it going?
@unknown: if a fix were implemented, previously generated invisible spawners/chests would remain invisible. You would need to explore new terrain in that world to find the fixed structures.
Since the (yesterday's) updating of the version to 0.12.1 of Android, all spawners stoped working on my survival map.
On the previous version, i had several mob spawning farms (found on the map), which are now seems useless.
The spawners present fire particles but with no mobs inside. Nothing goes out in all difficult levels. The same happens to skeleton, spider and zombie spawners.
Same problem appears to new spawner which have discovered after the updating.
PS: I am using Android 5.0.2, Samsung SM P905
Since the (yesterday's) updating of the version to 0.12.1 of Android, all spawners stoped working on my survival map.
On the previous version, i had several mob spawning farms (found on the map), which are now seems useless.
The spawners present fire particles but with no mobs inside. Nothing goes out in all difficult levels. The same happens to skeleton, spider and zombie spawners.
Same problem appears to new spawner which have discovered after the updating.
PS: I am using Android 5.0.2, Samsung SM P905
@unknown: you may report this issue in a new ticket.
Can't Confirm on Alcatel Ot 995,but i can confirm on Huawei Y220
Can't Confirm on Alcatel Ot 995,but i can confirm on Huawei Y220
Confirmed on Samsung Galaxy Note 5. Android 5.1.1 Version: 0.12.1
Spawners in the nether for blazes are empty for me. Not good for my survival world 😞
Confirmed on Samsung Galaxy Note 5. Android 5.1.1 Version: 0.12.1
Spawners in the nether for blazes are empty for me. Not good for my survival world 😞
Confirmed in 0.12.1 final release. Went to the nether for the first time, located a fortress and the blaze spawner was empty.
Confirmed in 0.12.1 final release. Went to the nether for the first time, located a fortress and the blaze spawner was empty.
Confirm on iPad 4
Confirm on iPad 4
I just found my first dungeon and the chests are invisible. I'm very disappointed. It wouldn't so bad except according to Katt, the chests won't be fixed even if the code is. Couldn't some sort of validation be implemented (maybe right after installing an update) to fix up glitched blocks? Maybe I'll create a feature request...
I just found my first dungeon and the chests are invisible. I'm very disappointed. It wouldn't so bad except according to Katt, the chests won't be fixed even if the code is. Couldn't some sort of validation be implemented (maybe right after installing an update) to fix up glitched blocks? Maybe I'll create a feature request...
This is just a bug as dungeons use to work. No need to feature request Kevin Perkins.
This is just a bug as dungeons use to work. No need to feature request Kevin Perkins.
Same for me on 0.12.1 alpha / iOS. A nether fortress had an invisible chest and an empty spawner which was supposed to have blazes in it. The spawner silently disappeared when I tried to reprogram it with a blaze spawn egg.
Same for me on 0.12.1 alpha / iOS. A nether fortress had an invisible chest and an empty spawner which was supposed to have blazes in it. The spawner silently disappeared when I tried to reprogram it with a blaze spawn egg.
I don't believe MCPE-10792 is the same issue; perhaps related but I think it's different. I've added some additional comments to that bug number. Is there a way to re-mark it as unresolved. I don't consider it a duplicate.
I don't believe MCPE-10792 is the same issue; perhaps related but I think it's different. I've added some additional comments to that bug number. Is there a way to re-mark it as unresolved. I don't consider it a duplicate.
Windows 10 Edition on PC, 0.12.1 - empty blaze spawners and empty invisible chests that can be broken, but not opened.
Windows 10 Edition on PC, 0.12.1 - empty blaze spawners and empty invisible chests that can be broken, but not opened.
I tested my suggestion in MCPE-10792 and I could transfer my saves from the S3/S5, MPCE, onto the Surface Pro 3, Windows 10 Beta. The level loaded fine and all things worked as expected except the spawners. So I used the same seed for the level to test if the spawners would work if they were created in the 0.12.1 version. I dug to the exact location of one of my spawners and it isn't even there - the dungeon layout is different. Did you guys change the way the seed creates the dungeons? Is this what is impacting the spawners? The above-ground details are an exact match but the layout under the surface seems to be different. I noticed too that when levels are created now you're obfuscating the folder name of the level - the .DAT and .LDB files seem to be the same so this shouldn't have an impact either should it?
I tested my suggestion in MCPE-10792 and I could transfer my saves from the S3/S5, MPCE, onto the Surface Pro 3, Windows 10 Beta. The level loaded fine and all things worked as expected except the spawners. So I used the same seed for the level to test if the spawners would work if they were created in the 0.12.1 version. I dug to the exact location of one of my spawners and it isn't even there - the dungeon layout is different. Did you guys change the way the seed creates the dungeons? Is this what is impacting the spawners? The above-ground details are an exact match but the layout under the surface seems to be different. I noticed too that when levels are created now you're obfuscating the folder name of the level - the .DAT and .LDB files seem to be the same so this shouldn't have an impact either should it?
Just to reiterate for clarification and testing purposes: my spawners are working fine in the level I created in Windows 10 Beta v0.12.1 and on my android phone v0.12.1 but any level that was created in older versions seems to have spawners that no longer function (flames but missing mob avatar) and newly found spawners are empty and there is often an invisible chest in the adjacent area.
Just to reiterate for clarification and testing purposes: my spawners are working fine in the level I created in Windows 10 Beta v0.12.1 and on my android phone v0.12.1 but any level that was created in older versions seems to have spawners that no longer function (flames but missing mob avatar) and newly found spawners are empty and there is often an invisible chest in the adjacent area.
Examples where the mob avatar is now missing inside spawn box which was working prior to 0.12.1 update.
Examples where the mob avatar is now missing inside spawn box which was working prior to 0.12.1 update.
@john McDowel that's different to the bug I originally reported - the spawners are completely empty with no flame at all. Yours might be a different bug.
@john McDowel that's different to the bug I originally reported - the spawners are completely empty with no flame at all. Yours might be a different bug.
I have this problem as well. Some spawners are completely empty (no flames). Some spawners have flames but aren't spawning mobs. This is for a world created in version 10. If I use the same seed to create a new world the spawners have both flames and spawn mobs.
I have this problem as well. Some spawners are completely empty (no flames). Some spawners have flames but aren't spawning mobs. This is for a world created in version 10. If I use the same seed to create a new world the spawners have both flames and spawn mobs.
I also had this problem. But, as a matter of fact, the chest was not invisible and had loot in it.
I also had this problem. But, as a matter of fact, the chest was not invisible and had loot in it.
@Paul Hunnisett, I agree, I think it's a different issue (though probably related) but they closed down my logged issue: MCPE-10792.
Just double checked this issue to confirm it's either version/copy related. I loaded the original one I had working on my S3 (started in 0.9.4 and updated now to version 0.11.1) and it's definitely spawning and has a mob avatar in the one's I've discovered. I copy it onto both my Surface Pro 3 and the S5 (using version 0.12.1) and they're broken - as per uploaded screenshots (flame but no mob avatar). Note too that any new mob spawners I find using that world are empty with no flame at all and invisible box. Levels created in 0.12.1 version seem to behave correctly (at least on my Surface I haven't found a spawner yet on a new world I created on the S5 - I'll keep you posted).
@Paul Hunnisett, I agree, I think it's a different issue (though probably related) but they closed down my logged issue: MCPE-10792.
Just double checked this issue to confirm it's either version/copy related. I loaded the original one I had working on my S3 (started in 0.9.4 and updated now to version 0.11.1) and it's definitely spawning and has a mob avatar in the one's I've discovered. I copy it onto both my Surface Pro 3 and the S5 (using version 0.12.1) and they're broken - as per uploaded screenshots (flame but no mob avatar). Note too that any new mob spawners I find using that world are empty with no flame at all and invisible box. Levels created in 0.12.1 version seem to behave correctly (at least on my Surface I haven't found a spawner yet on a new world I created on the S5 - I'll keep you posted).
I had a similar issue on my iOS device. None of the spawners that I have encountered after the recent update spawn or show any sort of life in them (i.e. flames). I think this is a bug in my case because first spawner I encountered with this problem WAS ACTIVE before the update and went dead afterwards. Is there a way to fix??
And I already tried adjusting difficulty setting and that didn't work either.
I had a similar issue on my iOS device. None of the spawners that I have encountered after the recent update spawn or show any sort of life in them (i.e. flames). I think this is a bug in my case because first spawner I encountered with this problem WAS ACTIVE before the update and went dead afterwards. Is there a way to fix??
And I already tried adjusting difficulty setting and that didn't work either.
Just to add, I have found an invisible chest at a Stronghold also. There were other loot chests that generated correctly, but also came across this one. See attached image of particles appearing when hitting the chest..
( 0.12.1 Win 10 PC )
Just to add, I have found an invisible chest at a Stronghold also. There were other loot chests that generated correctly, but also came across this one. See attached image of particles appearing when hitting the chest..
( 0.12.1 Win 10 PC )
Confirm that Nether Fortress' are generating with some invisible chests as well. World generated in Android 0.12.1, and updated to 0.12.2, chests are still invisible. Like others, breaking the chests yield only the chest and throws wood chips while breaking... not the loot. Some chests in the fortress are visible, some are not... right now it's 2 visible 2 invisible.
EDIT: Corrected version.
Confirm that Nether Fortress' are generating with some invisible chests as well. World generated in Android 0.12.1, and updated to 0.12.2, chests are still invisible. Like others, breaking the chests yield only the chest and throws wood chips while breaking... not the loot. Some chests in the fortress are visible, some are not... right now it's 2 visible 2 invisible.
EDIT: Corrected version.
Windows 10 edition
I have found so many empty mob spawners, especially in abandoned mineshafts and the nether. I have 250+ hours of play in my world and when I visited the nether and found the close fortress, every spawner was just an empty cage and their was also no chests to be found anywhere. No blaze or wither skeletons either.
After a few weeks I traveled for ages in the nether and found another fortress. This one had chests and spawners. I think because I found it after the 0.12.1 update, it was working. Its just such a hassle that it is so far away. Running takes like 5-10min just to get there while the defective fortress is like 30 sec away.
I have also visited 10-12 underground mineshafts and all of them have had empty spawners (poisonous cave spiders) and no chests. I have literally spent weeks looking for melon seeds but since every mineshaft I visit is damaged I cant seem to find any melons or melon seeds anywhere. My map is almost 400MB and I havnt found a jungle either.
Im hoping that their is a feature implemented where the user can refresh a seeds spawners once they get fixed without disrupting everything that has been built.
Maybe a feature can be implemented in the menu that will refresh a seeds mineral deposits and spawners but the feature can only be used once a month or something like that. Even if it is only a one time thing when the beta is over I would be good with that. I really like my seed and have spent 250+ hours in it, the broken spawners and and glitched mineshafts just take the fun out of everything.
Windows 10 edition
I have found so many empty mob spawners, especially in abandoned mineshafts and the nether. I have 250+ hours of play in my world and when I visited the nether and found the close fortress, every spawner was just an empty cage and their was also no chests to be found anywhere. No blaze or wither skeletons either.
After a few weeks I traveled for ages in the nether and found another fortress. This one had chests and spawners. I think because I found it after the 0.12.1 update, it was working. Its just such a hassle that it is so far away. Running takes like 5-10min just to get there while the defective fortress is like 30 sec away.
I have also visited 10-12 underground mineshafts and all of them have had empty spawners (poisonous cave spiders) and no chests. I have literally spent weeks looking for melon seeds but since every mineshaft I visit is damaged I cant seem to find any melons or melon seeds anywhere. My map is almost 400MB and I havnt found a jungle either.
Im hoping that their is a feature implemented where the user can refresh a seeds spawners once they get fixed without disrupting everything that has been built.
Maybe a feature can be implemented in the menu that will refresh a seeds mineral deposits and spawners but the feature can only be used once a month or something like that. Even if it is only a one time thing when the beta is over I would be good with that. I really like my seed and have spent 250+ hours in it, the broken spawners and and glitched mineshafts just take the fun out of everything.
Windows 10 edition
As far as I see, the mob spawners work again in 0.12.2, but the spawned monsters (zombies in this case) don't drop any loot, not even rotted flesh.
Windows 10 edition
As far as I see, the mob spawners work again in 0.12.2, but the spawned monsters (zombies in this case) don't drop any loot, not even rotted flesh.
@James T. Kirk I was unable to duplicate the problem. I was testing this in 0.12.2.
@James T. Kirk I was unable to duplicate the problem. I was testing this in 0.12.2.
@James T. Kirk I tested this 2 ways with a zombie spawner and at night. Zombies spawned from spawner gave items when killed. Zombies naturally spawning at night also gave items when killed. What you explained is not happening to me in 0.12.2.
@James T. Kirk I tested this 2 ways with a zombie spawner and at night. Zombies spawned from spawner gave items when killed. Zombies naturally spawning at night also gave items when killed. What you explained is not happening to me in 0.12.2.
That may be due to me writing "Windows 10 edition" when I meant to write "Pocket Edition on Windows Phone 8.1". Sorry... Can you perhaps try in that version? I just stood in front of the spawner for some time, no drops at all - with the exception of one zombie who wore armor, which dropped beautifully.
That may be due to me writing "Windows 10 edition" when I meant to write "Pocket Edition on Windows Phone 8.1". Sorry... Can you perhaps try in that version? I just stood in front of the spawner for some time, no drops at all - with the exception of one zombie who wore armor, which dropped beautifully.
Confirmed to affect 0.12.2 on iPhone 6 Plus (iOS 9.0.2). Reproduced with a monster room (seed: shroomzy). It appears that blaze spawners are generated correctly. Blaze spawners as well still have a chance to be empty
@@unknown: Like the above members, neither mobs from naturally-generated spider spawners' nor player-created zombie spawners had any issues with their drop rates.
I tested a little further, and after opening the spawner chamber, I found out that the problem is not the spawner, but the mode of death. When attacking the zombies, they drop loot, when they die in the chamber's water trap, they don't. I have not tested with other mobs yet, but maybe monsters no longer drop anything when drowning? Or is that intended? It makes sense that drowning monsters do not drop XP.
I tested a little further, and after opening the spawner chamber, I found out that the problem is not the spawner, but the mode of death. When attacking the zombies, they drop loot, when they die in the chamber's water trap, they don't. I have not tested with other mobs yet, but maybe monsters no longer drop anything when drowning? Or is that intended? It makes sense that drowning monsters do not drop XP.
I can confirm that drowning / smothering some mobs produce no loot, but DOES drop whatever chance armor they may possess.
I did this by dropping a bunch of gravel on a bunch of pigmen. No nuggets or rotten flesh was produced, but I did get an enchanted helment.
I can confirm that drowning / smothering some mobs produce no loot, but DOES drop whatever chance armor they may possess.
I did this by dropping a bunch of gravel on a bunch of pigmen. No nuggets or rotten flesh was produced, but I did get an enchanted helment.
I can confirm my spawners from 0.9.4 are working again. The 0.12.1 update was the only buggy version for me. The 0.12.2 update seems to have rectified the issue.
I can confirm my spawners from 0.9.4 are working again. The 0.12.1 update was the only buggy version for me. The 0.12.2 update seems to have rectified the issue.
My world generated in 12.1 on IOS iPad Air 2 is still not working in the nether. Overworld dungeons appear to be working as expected, but Blazes only spawn on fortress generation and not after, chests are invisible or not present and Blaze spawners are not active.
New worlds created in Creative mode are working as expected.
My world generated in 12.1 on IOS iPad Air 2 is still not working in the nether. Overworld dungeons appear to be working as expected, but Blazes only spawn on fortress generation and not after, chests are invisible or not present and Blaze spawners are not active.
New worlds created in Creative mode are working as expected.
Blaze spawners generated in version 12.1
Blaze spawners generated in version 12.1
Blaze spawners in the Nether and dungeons seam to have been fixed as of 0.12.2.
Dungeons spawners - Steps to duplicate
-Create new world. I used seed: mamaMOOSE
-Fly to the middle of the two villages.
-Dig straight down near the well until you fall into a cave.
-A stronghold is about 10-15 blocks from where you are now.
The stronghold has an active zombie spawner.
EDIT: Chests in dungeons appear to be visible and have loot in them.
Blaze spawners - Steps to duplicate
-Create a new world.
-Create a portal to the Nether.
-While in the Nether look for a Fortress.
You will see that blaze spawners are no longer empty.
Blaze spawners in the Nether and dungeons seam to have been fixed as of 0.12.2.
Dungeons spawners - Steps to duplicate
-Create new world. I used seed: mamaMOOSE
-Fly to the middle of the two villages.
-Dig straight down near the well until you fall into a cave.
-A stronghold is about 10-15 blocks from where you are now.
The stronghold has an active zombie spawner.
EDIT: Chests in dungeons appear to be visible and have loot in them.
Blaze spawners - Steps to duplicate
-Create a new world.
-Create a portal to the Nether.
-While in the Nether look for a Fortress.
You will see that blaze spawners are no longer empty.
Does this bug still appear in 0.12.2? If so please respond.
Does this bug still appear in 0.12.2? If so please respond.
Yes it still does. I have a seed of -571837837 and have encountered this on windows 10 edition, and notably the spawners which are in error are DIFFERENT with this latest update (0.12.2) than in 0.12.1. In 0.12.1 we had a survival world in which at least two "real world" spawners worked, but at least one was blank. And ALL nether spawners encountered are blank.
So then I re-created it in creative for speed of getting to the nether and checking things out. At least one of the real-world spawners is dead, but the nether ones are active.
Go south from spawn, near two trees, and there's two cavern entrances there near the border with Savannah biome. Take the left one to a MASSIVE cave. Follow the left wall of the cave and up, and there will be a skeleton spawner. It'll be dead or alive. It was dead for me, but alive when it was created in 0.12.1. Put a nether portal near the swamp by there, and then head directly EAST to a fortress, and those spawners work.
I'll test further, but still, different results, different versions, but NOT all fixed.
So not completely fixed.
Yes it still does. I have a seed of -571837837 and have encountered this on windows 10 edition, and notably the spawners which are in error are DIFFERENT with this latest update (0.12.2) than in 0.12.1. In 0.12.1 we had a survival world in which at least two "real world" spawners worked, but at least one was blank. And ALL nether spawners encountered are blank.
So then I re-created it in creative for speed of getting to the nether and checking things out. At least one of the real-world spawners is dead, but the nether ones are active.
Go south from spawn, near two trees, and there's two cavern entrances there near the border with Savannah biome. Take the left one to a MASSIVE cave. Follow the left wall of the cave and up, and there will be a skeleton spawner. It'll be dead or alive. It was dead for me, but alive when it was created in 0.12.1. Put a nether portal near the swamp by there, and then head directly EAST to a fortress, and those spawners work.
I'll test further, but still, different results, different versions, but NOT all fixed.
So not completely fixed.
Yes it still does. I have a seed of -571837837 and have encountered this on windows 10 edition, and notably the spawners which are in error are DIFFERENT with this latest update (0.12.2) than in 0.12.1. In 0.12.1 we had a survival world in which at least two "real world" spawners worked, but at least one was blank. And ALL nether spawners encountered are blank.
So then I re-created it in creative for speed of getting to the nether and checking things out. At least one of the real-world spawners is dead, but the nether ones are active.
Go south from spawn, near two trees, and there's two cavern entrances there near the border with Savannah biome. Take the left one to a MASSIVE cave. Follow the left wall of the cave and up, and there will be a skeleton spawner. It'll be dead or alive. It was dead for me, but alive when it was created in 0.12.1. Put a nether portal near the swamp by there, and then head directly EAST to a fortress, and those spawners work.
I'll test further, but still, different results, different versions, but NOT all fixed.
So not completely fixed.
Edit: I've now re-created this world 2 more times, and while the spawner behavior is "sometimes yes, sometimes no" on the surface, the ones in the nether seem reliable... so far.
Interestingly, I think I've found another bug, in that "surface pools" of water and LAVA are random. IE: it's not the same for the same seed. Most other features are consistent, but surface lava and small "pools" of water aren't consistent. I'll search for another bug for this one (and/or file one) but if you use the seed above, and immediately turn left and cross the river (fly in creative, faster) and survey that spit of land, until you reach the main "tree line" of the forest biome to the south. On those plains (not much of plains, but still) not all the water is consistent between world creations, and sometimes you get surface (or 2 below the surface with a hole or two) lava pockets. ALL ON THE SAME SEED.
So it may be unrelated, but there's definitely things in world creation not tied to the seed, and it may be causing this issue too.
Yes it still does. I have a seed of -571837837 and have encountered this on windows 10 edition, and notably the spawners which are in error are DIFFERENT with this latest update (0.12.2) than in 0.12.1. In 0.12.1 we had a survival world in which at least two "real world" spawners worked, but at least one was blank. And ALL nether spawners encountered are blank.
So then I re-created it in creative for speed of getting to the nether and checking things out. At least one of the real-world spawners is dead, but the nether ones are active.
Go south from spawn, near two trees, and there's two cavern entrances there near the border with Savannah biome. Take the left one to a MASSIVE cave. Follow the left wall of the cave and up, and there will be a skeleton spawner. It'll be dead or alive. It was dead for me, but alive when it was created in 0.12.1. Put a nether portal near the swamp by there, and then head directly EAST to a fortress, and those spawners work.
I'll test further, but still, different results, different versions, but NOT all fixed.
So not completely fixed.
Edit: I've now re-created this world 2 more times, and while the spawner behavior is "sometimes yes, sometimes no" on the surface, the ones in the nether seem reliable... so far.
Interestingly, I think I've found another bug, in that "surface pools" of water and LAVA are random. IE: it's not the same for the same seed. Most other features are consistent, but surface lava and small "pools" of water aren't consistent. I'll search for another bug for this one (and/or file one) but if you use the seed above, and immediately turn left and cross the river (fly in creative, faster) and survey that spit of land, until you reach the main "tree line" of the forest biome to the south. On those plains (not much of plains, but still) not all the water is consistent between world creations, and sometimes you get surface (or 2 below the surface with a hole or two) lava pockets. ALL ON THE SAME SEED.
So it may be unrelated, but there's definitely things in world creation not tied to the seed, and it may be causing this issue too.
@Kevin Anderson I was testing the seed you provided. Could you provide the steps in finding these dungeons? You mentioned a non-functioning spawner upon world generation, I want to confirm this.
@Kevin Anderson I was testing the seed you provided. Could you provide the steps in finding these dungeons? You mentioned a non-functioning spawner upon world generation, I want to confirm this.
@Liam Last - See https://bugs.mojang.com/browse/MCPE-11109
Go south from spawn and find a rather large cave near a large oak. Follow the left wall and up to find a spawner. You will see the cobblestone in the cave but not an actual entrance to the spawner room. If you need more than that, please ask and I will annotate screenshots with instructions.
The problem is that I have made the world 4 times and the spawner has been disabled only once. Current version, today, windows 10 edition, creative mode. But the other 3 times it is functioning fine.
Good luck.
@Liam Last - See https://bugs.mojang.com/browse/MCPE-11109
Go south from spawn and find a rather large cave near a large oak. Follow the left wall and up to find a spawner. You will see the cobblestone in the cave but not an actual entrance to the spawner room. If you need more than that, please ask and I will annotate screenshots with instructions.
The problem is that I have made the world 4 times and the spawner has been disabled only once. Current version, today, windows 10 edition, creative mode. But the other 3 times it is functioning fine.
Good luck.
@unknown Could only test this in Minecraft Windows 10 Edition due to a small difference in land generation. MCPE-11109 The spawner was active. I am assuming this has been fixed.
@unknown Could only test this in Minecraft Windows 10 Edition due to a small difference in land generation. MCPE-11109 The spawner was active. I am assuming this has been fixed.
Please re-read my comments. 3/4 times the spawner worked. Once it did not. This is on 0.12.2, creative mode, TODAY, so it is unfortunately a "happens sometimes" bug. I have no doubt that it worked for you, but it definitely sometimes does not work. If you would like me to upload the world to dropbox or something so you can look at it, I will do so. Please let me know if that's what you would like.
And on a related note, if there is a difference on pocket, I would call that (or the way it generates on win10) a bug.
Please re-read my comments. 3/4 times the spawner worked. Once it did not. This is on 0.12.2, creative mode, TODAY, so it is unfortunately a "happens sometimes" bug. I have no doubt that it worked for you, but it definitely sometimes does not work. If you would like me to upload the world to dropbox or something so you can look at it, I will do so. Please let me know if that's what you would like.
And on a related note, if there is a difference on pocket, I would call that (or the way it generates on win10) a bug.
Not fixed yet. Win 10, 0.12.2: Today: Old (already discovered) empty spawners are still empty. Newly discovered 1/2 times are empty.
Not fixed yet. Win 10, 0.12.2: Today: Old (already discovered) empty spawners are still empty. Newly discovered 1/2 times are empty.
Please comment below if this still affects your game after version 0.12.3.
Please comment below if this still affects your game after version 0.12.3.
Doesn't seem to affect newly-created worlds, but old worlds still bugged, with 3 world creations. That doesn't mean it's fixed, as 3/4 of mine in 0.12.2 were fine, but 1 wasn't.
A fix that would fix broken spawners would be great for those invested in old worlds.
Doesn't seem to affect newly-created worlds, but old worlds still bugged, with 3 world creations. That doesn't mean it's fixed, as 3/4 of mine in 0.12.2 were fine, but 1 wasn't.
A fix that would fix broken spawners would be great for those invested in old worlds.
@unknown duly noted.
@unknown duly noted.
In 0.12.3 Found an empty spawner. It is not all spawners because I have found two zombie spawners and one empty one. My world is an older generated world from 0.12.2.
In 0.12.3 Found an empty spawner. It is not all spawners because I have found two zombie spawners and one empty one. My world is an older generated world from 0.12.2.
Note: On worlds created prior to 0.12.3, this bug will still occur. (That is because the world was generated with the bug, cannot be fixed)
Note: On worlds created prior to 0.12.3, this bug will still occur. (That is because the world was generated with the bug, cannot be fixed)
More specifically, on worlds created prior to 0.12.3 in areas where the chunks you are in were generated before updating to 0.12.3, this bug will still occur because those spawners were created empty in the older version. Does that make sense? So you can get new 0.12.3 generated terrain in an older version world by moving to an area of the world where the chunks had not yet been generated and getting it generated by 0.12.3.
More specifically, on worlds created prior to 0.12.3 in areas where the chunks you are in were generated before updating to 0.12.3, this bug will still occur because those spawners were created empty in the older version. Does that make sense? So you can get new 0.12.3 generated terrain in an older version world by moving to an area of the world where the chunks had not yet been generated and getting it generated by 0.12.3.
I too would have liked to see bugged chests and spawners fixed as part of the bug fix. Does anyone have any technical information about what's wrong with the bugged blocks (especially the chests). If I had that info, I'd be tempted try to use the leveldb fork on GitHub to write a tool to fix my world.
I too would have liked to see bugged chests and spawners fixed as part of the bug fix. Does anyone have any technical information about what's wrong with the bugged blocks (especially the chests). If I had that info, I'd be tempted try to use the leveldb fork on GitHub to write a tool to fix my world.