To Talven Turog: I do not believe something being an annoyance should be sent to the Minecraft forums, they already do not browse there much. If this bug tracker is not able to handle annoyances, then I would have no option but to move my bug reporting back to the Minecraft wiki, however, I would like to see this bug tracker of Mojang's succeed first.
Mojang wants all issues in one place, annoyances are issues, therefore they should be filed on this bug tracker site as what they are, it's just up to Mojang to decide when they will allow annoyances to be reported as what they really are.
I will add that my initial belief still stands, even though it was flagged as not a bug. I reported it, because I believed that it was a bug, and was reporting it in good faith as such. Thanks to everyone involved for handling it properly and not getting annoyed at such things as incorrectly reported bugs that are annoyances.
I do have a question about the pig behavior, though, the last paragraph of my issue report outlines the details of that above. Is that a "feature" or a bug? If that is an already existing bug on this tracker could someone please insert a link to it so I don't have to report something that already exists. I do not think pigs should crowd through double fence gates and make some pigs ignore the gate and stop pathfinding behavior. If it is a feature it is a very annoying feature and will be reported as an annoyance on the appropriate site once consensus on whether it's a bug or annoyance can be reached.
I have had very good results with using a half slab placed from above in such a way that you throw the chicken egg up at the bottom of the half slab. I haven't tested this using the upside down half slabs but what almost always happens with this method is that the chicken spawns immediately below the half slab and drops down, minimizing any suffocation damage it does incur on spawning.
Not very helpful if you happen to be in one of the few places without readily available food, for example a desert or ocean biome. Swimming takes hours to get anywhere, I would just like to be able to reset the night if I'm not using cheats and am trying to survey a survival map for potential spots after failing to obtain food via a normal game difficulty start on a random seed.
I have always thought that the whole point of survival was to be able to stay in one game mode and not have to rely on changing game modes. Currently this is not realistically possible due mainly to the fact that the Minecraft engine has it's gameplay mechanics geared primarily towards starts where the player can easily obtain both wood and basic starting equipment. This isn't so easy to do in ocean biomes especially given that the biome itself has no animal spawns whatsoever and that obtaining anything other than a slow starting wheat farm takes ages to do and requires that the player not sprint which also isn't easy to do given that sprinting is so easy to do accidentally.
While one could theoretically kill zombie spawns for potato or carrot drops and eat any rotting flesh that drops, this also can be time-consuming to do. There is a similar problem with spider string, because as often as not, they will drop 0 string. If a player really needs string for a fishing rod, which only needs 2 string the chance of obtaining one string from spiders killed by the player should be raised to where they don't have to kill a lot of spiders for poor randomly generated returns on kills.
It also seems weird that spider dungeons will generate a lot more string just because the chance of getting a spider to kill is insanely higher versus the chance enough of them will randomly spawn on an island large enough for spiders to spawn on along with other hostile mobs, and drop string.
I digress, the original issue I filed is a significant gameplay issue and one which needs addressing instead of being left by the wayside. I'm just not sure how much longer I'm willing to put up with having to walk around like a crazy Minecrafter hurting himself every time he takes a tick of starvation damage while staying fully healed on peaceful difficulty.
Can I request that this bug be upgraded to a major bug because of the suffocation issues? If so, I would like to request that this bug be upgraded because of that.
@Ian Carlson: Do you mean when you die and respawn, or in some other more specific circumstances?
If it's when you die and respawn, this may be intended, although the Minecraft Wiki does state you should respawn in a position above sea level. The fact that you're respawning in water may need the creation or alteration of another bug report to handle that because it's not actually directly related to the suffocation issue.
Your default spawn on creating a new world can land you in water, although perhaps a lot more rarely nowadays than it used to. It is, however, still possible to spawn, and therefore respawn, above water on creation of a new world, even if the generated spawn point in the map file is under or at the surface of land nearby.
Respawning only seems to pick an x/z pair of coordinates within 25 tiles of your spawn point, not place you at the first point you actually spawned at on a map.
I suggest you do some experimentation and see if you can separate the spawning/respawning in water issue from the stuck in block issue, because I think they may really be two separate issues. If that really is the case, simply create a new issue regarding the spawning/respawning in water and see how it gets categorized, maybe it's intended behavior, maybe not.
@Colton: As far as I can recall, they have been taking out spawn protection for the last couple of updates now. Regarding the SMP part to which you appear to be referring, the post appears to imply that the original poster was recreating worlds in single player. If Ian is indeed experiencing this problem in SMP or SSP worlds other players can join, it shouldn't really matter, anyway, for if Mojang fixes this bug, it will be fixed for both cases, since the client already runs a local server.
If a player is indeed placing blocks at the spawn point when another player dies and tries to respawn there, there may have to be special case handling code that moves the player outside the area where the other player is placing blocks. At the very least, it should spawn the player just above the blocks, not in them.
I doubt any player seriously wanting to actually play with friends on a Minecraft server would have malicious intent towards any other players, however, the ban system already exists to deal with this particular aspect.
@Nathan2055: I'm not discussing the fact that we're not required to use ocean worlds. The mere fact that they exist and that there is not a viable means to survive on them mean they probably deserve their own issue report anyway.
Besides which, ocean worlds are not the only spawns which could cause this problem. Any world seed that fails to generate both trees and food sufficiently close by to the player could cause this problem. I have encountered a few vanilla world starts where the player is placed far away from trees or starting resources, usually on the edge of a desert biome.
The ocean spawn issue itself has existed ever since animal spawns were changed to be biome specific and all animal spawn was removed from oceans. It should be easier for players to survive in an ocean world start, and there should be ocean content added which helps the player deal with a lack of trees and food.
If Mojang would at least address the core gameplay issues here with the world starts then perhaps I would play vanilla Minecraft more often, right now the issues with getting a random ocean or resource-starved spawn point make it very difficult to play vanilla Minecraft because what I look for in a vanilla start is to find needed resources quickly, I don't want to waste time having to look for my first tree on peaceful mode or resorting to cheaty methods to find where one might be.
I would like for the new Mesa biomes to be somewhat less rare.
I call having to hike thirty thousand tiles or more from spawn a bit much! When you consider this can occur in both x and z directions, even with a horse, one is going to spend many hours searching for these elusive Mesa biomes.
Please, Mojang, make the Mesa biomes somewhat less rare than they currently are!
I see that Mojang attempted to make biomes more realistic, when in fact what they did was to overcomplcate things. Minecraft world generation should not really depend on whether a biome is at the "hot" or "cold" end of the spectrum, it should depend on the way the biomes used to generate. That is, biomes should always be generated by percentage chance of generating and transition biomes that blend two biomes together should be reworked so that the current set of biomes can be easily blended.
One point of note, however: Why can't users set what biomes they want to generate themselves? If that was doable, biome problems could be up to the user to solve themselves. The randomness of Minecraft world generation may have appealing characteristics but perhaps it's time for people to be able to customize biomes to their liking, since it seems obvious that everyone has a vastly different opinion on what biomes they like or dislike.
There are issues with world generation and rendering which can be partially solved by using the Shift F3+a chunk reload shortcut, however, this is only a temporary solution.
Regarding what the above has to do with this bug: Excessive amounts of world terrain generation and rendering can exacerbate this chunk rendering bug. Currently the only workarounds are to either keep reloading chunks when the renderer fails to keep up, or to restart Minecraft and reset it's memory buffer entirely by doing so.
Mojang could make this less problematic by reworking the biome mix so that biomes generate in the way they used to so that rarity is only determined by percentage.
I submit that the biome generation being too rare for certain biomes is in fact a bug because of the side-effects it has on world generation and rendering, and therefore should be fixed.
Players can only do so much, they will always want new terrain, Mojang knows that. If they make it easier on the players to find biomes (whether rare or not) they'll make it easier on their rendering code to maintain and update it. In this way, everyone wins, not just the players.
Geoffrey Hyde
MC-393
Then it is an annoyance, how would I flag this as such? I have not yet learned how to flag an issue as an annoyance on this bug tracker.
To Talven Turog: I do not believe something being an annoyance should be sent to the Minecraft forums, they already do not browse there much. If this bug tracker is not able to handle annoyances, then I would have no option but to move my bug reporting back to the Minecraft wiki, however, I would like to see this bug tracker of Mojang's succeed first.
Mojang wants all issues in one place, annoyances are issues, therefore they should be filed on this bug tracker site as what they are, it's just up to Mojang to decide when they will allow annoyances to be reported as what they really are.
I will add that my initial belief still stands, even though it was flagged as not a bug. I reported it, because I believed that it was a bug, and was reporting it in good faith as such. Thanks to everyone involved for handling it properly and not getting annoyed at such things as incorrectly reported bugs that are annoyances.
I do have a question about the pig behavior, though, the last paragraph of my issue report outlines the details of that above. Is that a "feature" or a bug? If that is an already existing bug on this tracker could someone please insert a link to it so I don't have to report something that already exists. I do not think pigs should crowd through double fence gates and make some pigs ignore the gate and stop pathfinding behavior. If it is a feature it is a very annoying feature and will be reported as an annoyance on the appropriate site once consensus on whether it's a bug or annoyance can be reached.
I have had very good results with using a half slab placed from above in such a way that you throw the chicken egg up at the bottom of the half slab. I haven't tested this using the upside down half slabs but what almost always happens with this method is that the chicken spawns immediately below the half slab and drops down, minimizing any suffocation damage it does incur on spawning.
Not very helpful if you happen to be in one of the few places without readily available food, for example a desert or ocean biome. Swimming takes hours to get anywhere, I would just like to be able to reset the night if I'm not using cheats and am trying to survey a survival map for potential spots after failing to obtain food via a normal game difficulty start on a random seed.
I have always thought that the whole point of survival was to be able to stay in one game mode and not have to rely on changing game modes. Currently this is not realistically possible due mainly to the fact that the Minecraft engine has it's gameplay mechanics geared primarily towards starts where the player can easily obtain both wood and basic starting equipment. This isn't so easy to do in ocean biomes especially given that the biome itself has no animal spawns whatsoever and that obtaining anything other than a slow starting wheat farm takes ages to do and requires that the player not sprint which also isn't easy to do given that sprinting is so easy to do accidentally.
While one could theoretically kill zombie spawns for potato or carrot drops and eat any rotting flesh that drops, this also can be time-consuming to do. There is a similar problem with spider string, because as often as not, they will drop 0 string. If a player really needs string for a fishing rod, which only needs 2 string the chance of obtaining one string from spiders killed by the player should be raised to where they don't have to kill a lot of spiders for poor randomly generated returns on kills.
It also seems weird that spider dungeons will generate a lot more string just because the chance of getting a spider to kill is insanely higher versus the chance enough of them will randomly spawn on an island large enough for spiders to spawn on along with other hostile mobs, and drop string.
I digress, the original issue I filed is a significant gameplay issue and one which needs addressing instead of being left by the wayside. I'm just not sure how much longer I'm willing to put up with having to walk around like a crazy Minecrafter hurting himself every time he takes a tick of starvation damage while staying fully healed on peaceful difficulty.
Can I request that this bug be upgraded to a major bug because of the suffocation issues? If so, I would like to request that this bug be upgraded because of that.
@Ian Carlson: Do you mean when you die and respawn, or in some other more specific circumstances?
If it's when you die and respawn, this may be intended, although the Minecraft Wiki does state you should respawn in a position above sea level. The fact that you're respawning in water may need the creation or alteration of another bug report to handle that because it's not actually directly related to the suffocation issue.
Your default spawn on creating a new world can land you in water, although perhaps a lot more rarely nowadays than it used to. It is, however, still possible to spawn, and therefore respawn, above water on creation of a new world, even if the generated spawn point in the map file is under or at the surface of land nearby.
Respawning only seems to pick an x/z pair of coordinates within 25 tiles of your spawn point, not place you at the first point you actually spawned at on a map.
I suggest you do some experimentation and see if you can separate the spawning/respawning in water issue from the stuck in block issue, because I think they may really be two separate issues. If that really is the case, simply create a new issue regarding the spawning/respawning in water and see how it gets categorized, maybe it's intended behavior, maybe not.
@Colton: As far as I can recall, they have been taking out spawn protection for the last couple of updates now. Regarding the SMP part to which you appear to be referring, the post appears to imply that the original poster was recreating worlds in single player. If Ian is indeed experiencing this problem in SMP or SSP worlds other players can join, it shouldn't really matter, anyway, for if Mojang fixes this bug, it will be fixed for both cases, since the client already runs a local server.
If a player is indeed placing blocks at the spawn point when another player dies and tries to respawn there, there may have to be special case handling code that moves the player outside the area where the other player is placing blocks. At the very least, it should spawn the player just above the blocks, not in them.
I doubt any player seriously wanting to actually play with friends on a Minecraft server would have malicious intent towards any other players, however, the ban system already exists to deal with this particular aspect.
@Nathan2055: I'm not discussing the fact that we're not required to use ocean worlds. The mere fact that they exist and that there is not a viable means to survive on them mean they probably deserve their own issue report anyway.
Besides which, ocean worlds are not the only spawns which could cause this problem. Any world seed that fails to generate both trees and food sufficiently close by to the player could cause this problem. I have encountered a few vanilla world starts where the player is placed far away from trees or starting resources, usually on the edge of a desert biome.
The ocean spawn issue itself has existed ever since animal spawns were changed to be biome specific and all animal spawn was removed from oceans. It should be easier for players to survive in an ocean world start, and there should be ocean content added which helps the player deal with a lack of trees and food.
If Mojang would at least address the core gameplay issues here with the world starts then perhaps I would play vanilla Minecraft more often, right now the issues with getting a random ocean or resource-starved spawn point make it very difficult to play vanilla Minecraft because what I look for in a vanilla start is to find needed resources quickly, I don't want to waste time having to look for my first tree on peaceful mode or resorting to cheaty methods to find where one might be.
I would like for the new Mesa biomes to be somewhat less rare.
I call having to hike thirty thousand tiles or more from spawn a bit much! When you consider this can occur in both x and z directions, even with a horse, one is going to spend many hours searching for these elusive Mesa biomes.
Please, Mojang, make the Mesa biomes somewhat less rare than they currently are!
I see that Mojang attempted to make biomes more realistic, when in fact what they did was to overcomplcate things. Minecraft world generation should not really depend on whether a biome is at the "hot" or "cold" end of the spectrum, it should depend on the way the biomes used to generate. That is, biomes should always be generated by percentage chance of generating and transition biomes that blend two biomes together should be reworked so that the current set of biomes can be easily blended.
One point of note, however: Why can't users set what biomes they want to generate themselves? If that was doable, biome problems could be up to the user to solve themselves. The randomness of Minecraft world generation may have appealing characteristics but perhaps it's time for people to be able to customize biomes to their liking, since it seems obvious that everyone has a vastly different opinion on what biomes they like or dislike.
There are issues with world generation and rendering which can be partially solved by using the Shift F3+a chunk reload shortcut, however, this is only a temporary solution.
Regarding what the above has to do with this bug: Excessive amounts of world terrain generation and rendering can exacerbate this chunk rendering bug. Currently the only workarounds are to either keep reloading chunks when the renderer fails to keep up, or to restart Minecraft and reset it's memory buffer entirely by doing so.
Mojang could make this less problematic by reworking the biome mix so that biomes generate in the way they used to so that rarity is only determined by percentage.
I submit that the biome generation being too rare for certain biomes is in fact a bug because of the side-effects it has on world generation and rendering, and therefore should be fixed.
Players can only do so much, they will always want new terrain, Mojang knows that. If they make it easier on the players to find biomes (whether rare or not) they'll make it easier on their rendering code to maintain and update it. In this way, everyone wins, not just the players.