Yes, that's what I meant by desync - the lighting was written too long ago and the newer blocks don't have their values set yet, because no-one updated those. That's what's causing the black ladders in the server, among other things.
Well i'm currently working on the list, i think it will be finish this evening
btw wouldn't it be easier if we move the "can't push" list out of the BlockPiston.h into in the BlockInfo.cpp?
Probably should, on the contrary, move 'can break' into the piston handler since no one uses it. But maybe not.
The question is, when a new block is added, will you remember to update the piston code to reflect whether the block is breakable / pushable? Or are you more likely to update it if it's in the BlockInfo together with all the other blocks?
Maybe have a point in Guidelines for Contributing making a note of bring both locations up to date?