MC-68368Command blocks sometime don't check if a tag is true
Sometimes command blocks on a fast clock will not check if a condition is true every time. To replicate this, make a scoreboard objective called "example" and set its value to 1. Then put the command "tell @p[score_example=1] test" into a command block attached to a 20 hz clock. You will be spammed with messages. Then set your score in "example" to 0. The spam will not stop.
Environment
Operating system: OSX 10.9.3
Java Version "1.6.0_65"
Created Issue:
Detect argument bug
Sometimes the detect argument will think you are on the specified block when you are actually not. It is difficult to duplicate, however it seems to happen to me most when: It is on a very fast clock, and/or you have been on the correct block for a long time, and you suddenly move off of it. If you play around with it for a while, you should get it to happen to you.
Environment
Operating system: OSX 10.9.3
Java Version "1.6.0_65"
Sometimes the detect argument will think you are on the specified block when you are actually not. It is difficult to duplicate, however it seems to happen to me most when: It is on a very fast clock, and/or you have been on the correct block for a long time, and you suddenly move off of it. It also seems to happen more when in multiplayer or LAN. If you play around with it for a while, you should get it to happen to you.
Sometimes the detect argument will think you are on the specified block when you are actually not. It is difficult to duplicate, however it seems to happen to me most when: It is on a very fast clock, and/or you have been on the correct block for a long time, and you suddenly move off of it. It also seems to happen more when in multiplayer or LAN. If you play around with it for a while, you should get it to happen to you.
Sometimes command blocks on a fast clock will not check if a condition is true every time.
Sometimes command blocks on a fast clock will not check if a condition is true every time.
Sometimes command blocks on a fast clock will not check if a condition is true every time. To replicate this, make a scoreboard objective called "example" and set its value to 1. Then put the command "tell @p [score_example=1] test" into a command block attached to a 20 hz clock. You will be spammed with messages. Then set your score in "example" to 0. The spam will not stop.
Detect argument bugCommand blocks sometime don't check if a tag is true
The command executes with the center of the block you are closest to. So if your player is in between 2 blocks, it will try to detect the one that is closest to the decimal place.
I tested with large fields of blocks so I could be sure that that's not the problem.
You'll have to post your world file or a screenshot with commands then.
As I said, it is difficult to duplicate, just posting the world won't help. I'm currently trying to find a way to consistently duplicate it.
A word of advice: You should try and figure out a way to reproduce a bug before posting it on Jira. Without any confirmation, bugs get closed and it really is frustrating if you're the only one experiencing the issue.
Oh ok, i'll do that in the future. Thanks.
Ok, I found a way to replicate this, although the bug is different then I originally thought. It seems to be that commands on a fast clock will not test for all conditions to be true every time. To replicate it, make a scoreboard objective called "example" and set its value to 1. Then put the command "tell @p[score_example=1] test" into a command block attached to a 20 hz clock. You will be spammed with messages. Then set your score in "example" to 0. The spam will not stop. If you reset your score however, it will stop. The same thing can happen with conditions that are not scoreboard conditions (like detect), but those are harder to replicate.
I've responded, could this bug be reopened please?
Still working as intended.
tell @p[score_example=1] does not mean the score has to be exactly 1. It means the score can be up to 1.
To prove this, type this
You can see the spamming stops.
If you want to specify an exact number, you have to include a score_min, like this:
Whoops, I though score defaulted to min, not max. Never mind.
Ticket resolved as incomplete, because no answer in a reasonable amount of time (1+ year), if it still happens, please update the ticket.