What STR says is very right.
For MCS, tile entities are basically just entries in a list that are associated with the coordinates of a block that have extra data (i.e. contents, right click handlers, etc.) I'm fairly certain you can't 'send' a cobblestone tile entity - you can either update a client side tile entity via a packet (like a mob spawner's spinning mob type / command block text), or do special things with other packets (open a window for a chest). Internally to MCS, you can absolutely assign cobblestone to be a block entity that acts like a chest or whatever, the client doesn't care.
If you want to make any type of block move, you probably need to make a FallingSand entity, and assign it's blocktype and blockmeta to be what you want. As far as I know, block entities still can't move, they just store extra data.
For the PISTON_MOVING block, it stores a blocktype and meta, position and progress that animates a moving block. However, the client doesn't animate things that can't be moved (like a chest or furnace). I believe these things can't be moved because then the entry in the block entities list would become disassociated with the actual block in the world, and thus would be leaked.
(Correct me if I am mistaken too, I am very unsure of myself :P)
PS: Thank you, Taugeshtu, for using Windows 8 :)
For MCS, tile entities are basically just entries in a list that are associated with the coordinates of a block that have extra data (i.e. contents, right click handlers, etc.) I'm fairly certain you can't 'send' a cobblestone tile entity - you can either update a client side tile entity via a packet (like a mob spawner's spinning mob type / command block text), or do special things with other packets (open a window for a chest). Internally to MCS, you can absolutely assign cobblestone to be a block entity that acts like a chest or whatever, the client doesn't care.
If you want to make any type of block move, you probably need to make a FallingSand entity, and assign it's blocktype and blockmeta to be what you want. As far as I know, block entities still can't move, they just store extra data.
For the PISTON_MOVING block, it stores a blocktype and meta, position and progress that animates a moving block. However, the client doesn't animate things that can't be moved (like a chest or furnace). I believe these things can't be moved because then the entry in the block entities list would become disassociated with the actual block in the world, and thus would be leaked.
(Correct me if I am mistaken too, I am very unsure of myself :P)
PS: Thank you, Taugeshtu, for using Windows 8 :)