put this command on command block :blockdata ~ ~ ~ {SuccessCount:1}
it's work on 14w06b is perfect for compact redstone system but on 14w07a is deosn t work because you punch button 10 time your game crash.
Linked issues
is duplicated by 1
relates to 1
Attachments
Comments 8
See Also MC-49761 Specifically a commandblock setting the SuccessCount on itself leads to an infinite pit of despair.
blockdata ~ ~ ~
{SuccessCount:1}
[22:05:25] Block data updated to: {Command:"blockdata ~ ~ ~ {SuccessCount:1}",id:"Control",TrackOutput:1b,LastOutput:"{"extra":[{"translate":"commands.blockdata.success","with":["{Command:\"blockdata ~ ~ ~ {SuccessCount:1}\",id:\"Control\",TrackOutput:1b,CustomName:\"@\",SuccessCount:1,z:-74,y:1,x:663,}"]}],"text":"[22:05:09] "}",CustomName:"@",SuccessCount:1,z:-74,y:1,x:663,}
I can confirm in 14w08a.
@pecker: There is a work-around by applying a blank "LastOutput" tag, or by disabling output tracking:
/blockdata ~ ~ ~ {SuccessCount:1,LastOutput:" "}
/blockdata ~ ~ ~ {SuccessCount:1,TrackOutput:0b}
Apparently this has regressed in 1.8.1-pre5 (MC-74521).
I was testing a similar bug in 1.8.2-pre7 and found this one was active again.
Used 4 command blocks with the commands:
/blockdata 1 65 1 {SuccessCount:0}
/blockdata 1 65 -1 {SuccessCount:0}
/blockdata -1 65 -1 {SuccessCount:0}
/blockdata 1 65 -1 {SuccessCount:0}
3 connected by repeaters with a torch off the 3rd feeding the 4th with redstone dust.
Edit: When reading that crash report noticed I hadn't updated java in awhile. Updated to 1.8.0_31 and crashed it again.
Confirmed.
This is the tile entity data of the command block after running out of memory: