Issue has been resolved as of 0.15.3 or 0.15.4 (i don't know wich)
Bug present in 1.10.2
Oh, I forgot to add to the pictures that the four outer pistons are not sticky, and the two inner ones are. like this
O = observer S = Slime
P = piston # = sticky piston
OP OPO
SO#SSS
SSS#OS
OPO PO
I can confirm for windows 10 edition.
Bug present in 1.9.1 pre-3
Can confirm for 1.9.1 pre-1
Also happens when given an item while manipulating your inventory, as I detailed in MC-99295 before finding this bug.
I can confirm for 1.9.
This seems to affect all directional blocks
I tested furnace, piston, sticky piston, and torch.
(p.s. the torch with damage 0 rendered the item torch opposed to a placed torch. as if it were placed in an item frame)
also, this affects item frames,
place an item frame, run
/entitydata @e[r=3,type=ItemFrame] {Item:{id:"minecraft:dispenser",Count:1b,Damage:1s}}
I can confirm for 15w49b with the command
/summon ArmorStand ~ ~2 ~ {ArmorItems:[{},{},{},{id:"minecraft:dispenser",Damage:1}]}
(other blocks with damage values render correctly, ex stone 1 renders granit)
When you place the first gravel, the falling block entity it tries to produce gets killed before it can delete the first gravel. making the block disappear client side, and stay server side
if you place any block where the gravel was, it turns into gravel.
posibly relates to MC-54026
(because you are creating a ghost air block inside of a gravel block)
the Minecraft Wiki article on it says you can only change all of one type of block with replace.
A possible workaround could be to use /stat to make a command blocks:
/fill ~10 ~-10 ~10 ~-10 ~ ~-10 air 0 replace stone
affected blocks stat save to a scoreboard value then summon that many stone items.
Crash report? I can not reproduce in 15w49b
I can confirm for 15w49b.
I'm not sure if this was already understood; but I think the regen part of this bug is caused by Minecraft using how long the effect has left rather than how long you have had the effect to determine when to give the player a 1/2 heart.
/effect @a minecraft:regeneration 5 will give you a 1/2 heart when you run it, while /effect @a minecraft:regeneration 6 will wait until you have 5 seconds of the effect left to do so.
I have just ran into the same bug. I'm attaching a crash report.
This certainly is unexpected behavior... I would suggest only scheduling the first command block to run, then when it does, have it tell the next command block to execute without scheduling it, and have that block tell the next, and so on through the chain. To prevent infinite loops, have each command block, when told to run, check if it has been run this tick, if yes, have it not run the command, nor tell the next block to run.
p.s. Is this the correct place to suggest this? Or should I have put this on redit, with the rest of the suggestions?
I can confirm it for 15w32c
I think this is intended, to make it so on peaceful you always regenerate. (low food = no natural regen)
Still an issue in 16w33a.
Also probably won't be fixed for the same reason it wasn't in
MC-42375(because of Searge's comment onMC-31365)