I was messing around with Command Blocks for some kind of reward system I want to make (Players will get 'Coins' (virtual scoreboard currency) when they kill a Mob). It all works fine, but when I try to overload the system by killing many mobs at the same time my totalKillCount score gets reset properly and the rewarding part of my systems shuts off BUT in chat it still says the testfor commandblock is finding me. This is probably a really really bad explanation, sorry for that. You might want to look at the pictures to see what I mean.
Picture 1:
This is the /testfor commandblock (run by a Hopper clock) that checks for a player with the name Pepijn96 and a minimum score for MobKills of 5 (Mobkills is the name I gave the totalKillCount objective). Notice that it says at the bottom part of the GUI that the Command Block isn't finding any Players who match the Arguments!
Picture 2:
Here you can see that the Command Block is spamming in chat that it is finding me.
Picture 3:
Here you can clearly see that even the comparator is off, another sign that the /testfor didn't find anyone. (oh and btw, the second comparator is still having the "on" texture? while it's not on... another bug???)
Picture 4:
Still spamming...
This only happens when I'm killing many mobs at once. Just to make sure you understand me correctly: The system is actually working, the only issue is that it's spamming in the chat that the testfor is still finding me even when it's clearly not doing that anymore (GUI says it, comparator=off).
Thanks for reading
Pepijn96 (Pepijn Sietsema)
Attachments
Comments 8
Found the problem, redstone was activating another testfor commandblock, my bad (and Tobias, you might want to test things before you comment)
You don't, the mods do, and Tobias is not totally off, he's just been running with commandBlockOutput false for so long he's probably forgotten about it.
Ah ok. But tobias should probably have known that /say only does white text with the name of the command block in front of it, he should at least have said /tellraw 😛. But btw, what about that second comparator having the "on" texture, when it's not receiving or sending out a signal (picture 3)?
That's MC-12211.
I can't see any bug because the spam looks like it is caused by a "/say" command. "/testfor" does not log anything to the chat as far as I remember.