The following bug has appeared on the bug tracker, designation MC-3917, but the moderator that closed it appears to have mis-interpreted the issue. He/she has quoted that " If left alone, silverfish can re-enter some blocks, namely cobblestone, regular stone, and stone bricks" but these blocks were not entered in this way. To clarify, using the format usually used for minecraft bug reports...
What I expected to happen was:
Blocks of "smooth" stone, cobblestone or stone bricks spawning naturally may conceal silverfish eggs, whilst blocks placed in creative or survival mode will not unless a silverfish mob "burrows" into it.
What actually happened was:
A significant portion of cobble, "smooth" stone and stone brick blocks placed in creative mode randomly transform into silverfish eggs of their own accord, without making any contact with a silverfish mob.
Steps to reproduce:
1) Begin playing in a creative world, on a non-peaceful difficulty setting (one that allows hostile mobs), or use cheats/commands to change the game mode to creative.
2) Place blocks of cobblestone, stone or stone bricks, the more the better. Do not place "monster egg" blocks, or allow any existing silverfish mobs to approach the ones you have placed.
3) Break the blocks you placed - for clearest results, use a stone pick or similarly appropriate tool.
4) Some of the blocks will randomly have transformed into "monster egg" blocks and thus will spawn silverfish, without having made physical contact with any silverfish mobs.
Why this is a problem:
To the best of my knowledge silverfish eggs do not "randomly spawn" inside blocks placed in survival mode, nor should this be the case, since it would make these "stone" materials too great a risk to ever use as a building block. For that same reason however, this should not happen in creative mode either. Creative mode offers us the choice to deliberately place "monster egg" blocks, so logically it should also offer us the choice to place stone blocks without any risk of monster eggs appearing.
I believe this was no misunderstanding.
Still the system might be experiencing a duplication glitch.
Please quote me when replying.
As described in my original post, these issues are separate. The moderator is stating that any block of the appropriate stone type can be "entered" by a silverfish mob, turning it into a "monster egg". I am not disputing that this is function as intended, but I do believe it fails to address the problem I have encountered.
My contention is that some of these blocks become "monster eggs" without being "entered" by a silverfish mob. In other words, a random percentage of all appropriate block types become "monster eggs", changing their block id without cause or any means of prevention.
That is what I was trying to put across with 'duplication glitch'.
Ah, my apologies.
I was wondering if perhaps the fact that these blocks were placed in creative was somehow causing them to be treated as generated automatically (like they would if exploring a new chunk). Since stone bricks only naturally appear in ruins and strongholds, perhaps this would interact poorly with the silverfish spawn behavior? I don't know enough about the mobs to know if this theory makes any sense though.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
What I expected to happen was:
Blocks of "smooth" stone, cobblestone or stone bricks spawning naturally may conceal silverfish eggs, whilst blocks placed in creative or survival mode will not unless a silverfish mob "burrows" into it.
What actually happened was:
A significant portion of cobble, "smooth" stone and stone brick blocks placed in creative mode randomly transform into silverfish eggs of their own accord, without making any contact with a silverfish mob.
Steps to reproduce:
1) Begin playing in a creative world, on a non-peaceful difficulty setting (one that allows hostile mobs), or use cheats/commands to change the game mode to creative.
2) Place blocks of cobblestone, stone or stone bricks, the more the better. Do not place "monster egg" blocks, or allow any existing silverfish mobs to approach the ones you have placed.
3) Break the blocks you placed - for clearest results, use a stone pick or similarly appropriate tool.
4) Some of the blocks will randomly have transformed into "monster egg" blocks and thus will spawn silverfish, without having made physical contact with any silverfish mobs.
Why this is a problem:
To the best of my knowledge silverfish eggs do not "randomly spawn" inside blocks placed in survival mode, nor should this be the case, since it would make these "stone" materials too great a risk to ever use as a building block. For that same reason however, this should not happen in creative mode either. Creative mode offers us the choice to deliberately place "monster egg" blocks, so logically it should also offer us the choice to place stone blocks without any risk of monster eggs appearing.
As described in my original post, these issues are separate. The moderator is stating that any block of the appropriate stone type can be "entered" by a silverfish mob, turning it into a "monster egg". I am not disputing that this is function as intended, but I do believe it fails to address the problem I have encountered.
My contention is that some of these blocks become "monster eggs" without being "entered" by a silverfish mob. In other words, a random percentage of all appropriate block types become "monster eggs", changing their block id without cause or any means of prevention.
Ah, my apologies.
I was wondering if perhaps the fact that these blocks were placed in creative was somehow causing them to be treated as generated automatically (like they would if exploring a new chunk). Since stone bricks only naturally appear in ruins and strongholds, perhaps this would interact poorly with the silverfish spawn behavior? I don't know enough about the mobs to know if this theory makes any sense though.