Minecraft Wiki talk:Issues/1.0.0

Snow in Taigas
Although Tundras (ice plains) finally have snow again, Taigas (pine forests) still do not. It really is bad that you never see snow at high altitudes.Chezzik 19:58, 21 November 2011 (UTC)

Death
While in a boat on hardcore mode, a tamed wolf falling onto you will kill you. 0305 11-22-11 (CST)

Read the instructions sign
This should be red,orange or yellow to add contrast. --93.106.76.125 10:21, 22 November 2011 (UTC)

Piston cannot extend discussion
[X] If a piston is powered but cannot extend because of the amount or types of blocks in front of it, the piston will still not extend after the blocks have been removed, even if its power source remains. (this should become a large bug, not a minor, as it could mess with auto building bridges and other devices that use a max pistons push amount. This could break a lot of things!)
 * Absolutely not. This property is crucial for building legitimate BUD devices, and all sorts of existing creations depend on it.  Do not remove this feature!  (Instead, remove the Piston Quasiconnectivity Bug, which messes many more things up, and is a terrible abstraction.)  —Immute [talk]
 * That is true, but this is still a bug. Many devices that use BUDs can be built other ways that do not rely on the glitch. A possile fix to this bug may be to tell pistons to update if a block within thirteen blocks of its front side changes state.
 * That would require Minecraft to search 78 blocks every time another block changes, possibly involving loading extra chunks. It's also one of the easiest-to-understand piston glitches and allows some interesting behaviour - specifically BUDs - as opposed to the quasiconnectivity bug which is hard to understand. Immibis
 * It would only need to check eighteen blocks around the piston: one block on each of the five sides made of cobblestone and thirteen blocks on the side of the wooden arm. (Pistons can push up to twelve blocks so it would be important to keep track of the thriteenth block that might be preventing movement.) Also, anyone who has been using BUD devices should have known not to heavily rely on a bug that exists in a game that is in development. You should have been expecting bugs like this to be fixed eventually.
 * You don't understand how block updates works in minecraft. Immibis is right. T would need to update 78 blocks (13 in every direction) to make sure, that pistons, that can be there, update status. And this can accidently break some old-style BUDs (like a water which changes flow if block nearby is updated). — MiiNiPaaT
 * Actually it just could, first check what direction which piston is pointing, then check blocks there, resulting to check 14 blocks. --93.106.76.125 11:04, 22 November 2011 (UTC)
 * it is the other way around: if an Block updates this Block has to check 78 Blocks if they are Pistons and if they could extend towards this Block. if it would depend on the Piston you would have to check 14 Blocks - but per tick and per visible/loaded piston, which would be much more load on the CPU than checking the 78 Blocks per block update which is already multiple times more than currently

217.189.220.19 20:56, 23 November 2011 (UTC)

Entities

 * Wolves glitch out again like they used to and will be never be able to stand up, they also will attack there owners when glitched.


 * When a player is killed or disconnects on a server they will remain there, but they cannot be interacted with/ collided with.


 * Wolves will keep standing back up automatically in SMP (they are still sitting but there model stands up)