False Shown Leaf Decay

Intended. Random ticking will change this back to true.

i'v already tryed but it stay's the same.

I'm not sure what you mean by that. Random tick speed doesn't affect whether a leave can decay, only how fast.

Confirmed in 1.8.2-pre6. The check_decay field is simply incorrect. Grow a tree, and destroy the wood. Some of the leaves with have check_decay true, and some will have false, but they will all decay.

ok thanks

This is not intended. Please reopen.

Could someone please explain why this is marked as WAI? It's clearly a bug.

@unknown explained the check_decay field to me a while back, though I can't remember if there was a specific issue under discussion. The leaf decay algorithm is kind of computationally expensive, and they've done a lot of things to try to reduce its impact on performance. The server doesn't generally send updates about the check_decay field to clients in order to reduce traffic. The client doesn't need to know about it, because it doesn't affect the appearance of the block, and it's the server that does the decay calculations. The server only sends it when it has to send other information about that block, such as when you load the whole chunk, and possibly when it experiences a block update.

Oh. Well I still feel that this is a bug, because the debug screen is showing incorrect information. If they don't want to send those updates to the client, they should remove that field from the debug screen.

The debug screen is primarily for Mojang's own use. If they find the presence of the check_decay field useful, even though it isn't always up to date, then it serves its purpose. Anyway, I believe the debug screen is populated automatically, and it's probably not worth it to make a special case to specifically exclude a field.

Server has some internals that 'leak' through blockstates, they are not send to reduce traffic.