mojira.dev
MC-45431

Redstone Comparator clock bug (Renamed)

When using

testfor @p[score_deaths]

or

testfor @p[score_deaths_min]

in a command block, it doesn't output a redstone signal when adjacent to a comparator (assuming the condition is true)

– Fixed – --New Bug –

When using a comparator clock, and the redstone input is within about 3 blocks of the comparator, the command block (or any peripheral) will not receive redstone activation.

Related issues

Attachments

Comments

migrated
[media]
migrated

Unable to reproduce in Minecraft 1.7.4.

  • You need to add the objective by typing /scoreboard objectives add deaths stat.deaths

  • @p only detects the closest player. If the condition isn't true for this player, there will be no output.

If that doesn't help, please force a crash by pressing F3 + C for 10 seconds while in-game and attach the crash report (minecraft/crash-reports/crash-<DATE>-client.txt) here.

Ezekiel

Please put the exact command you used. The commands you showed are not valid.

2008Choco

I have added the scoreboard into the game with those stats, however the command is still not recognizing that I have 3 deaths. The exact command I used is

testfor @p[score_deaths_min=3]

. I am aware that you need to have 3 deaths and that it tests for the nearest player and I have accomplished all of those listed criteria but it still does not output a signal.

2008Choco

Maybe this snapshot will help you get a general idea of what I'm trying to explain.

2008Choco

Notice the "Deaths = 6" scoreboard on the side of my screen?

Ezekiel

Try setting your deaths to exactly 3, does it work?

2008Choco

I did try it. That was the first thing I did to see if the command worked. It didn't... That's when I realized it was bugged.

Ezekiel

ok, try this

/scoreboard objectives add deaths2 deathCount
/scoreboard objectives setdisplay sidebar deaths2
/kill
/kill
/kill
/say @a[score_deaths2_min=3]

Does it say your name?

2008Choco

I am officially a genius... Ok so I found the issue and it was in fact NOT the command block at all. So see what I had done was used a comparator clock and since the command block was too close to the redstone, it wasn't actually receiving a redstone pulse. I suppose that this can be considered a bug aswell though... I'll put another snapshot of what I mean.

2008Choco

The redstone clock is too close to the command block and isn't receiving a redstone pulse

2008Choco

(Unassigned)

Unconfirmed

Minecraft 1.7.4

Retrieved