Heyho,
weird problem regarding the testfor and other commands which uses scoreboard selectors:
i can't test for an entity with an scoreboard selector anymore:
/testfor @e[name=<entityname>,score_objective=<number>]
doesnt work.
/testfor @e[name=<entityname>]
works.
Besides the /testfor it also doesn't work for /kill, /execute, etc
It doesn't show any error message in the chat.
Linked issues
is duplicated by 1
Comments 5
Updatetime:
I got it working now. The thing was i built a command block contraption before (in 21b) which worked fine.
it used 24 Witherskulls who got a score between 0 and 3 via a randomizer. Then depending on the number (1-3, 0 is "undefined") these witherskulls summoned another witherskull above it (y=95, c=1). Now the witherskull sets the new summoned skull a scoreboard value of another objective and kills itself, so that only the new summoned skulls on y=95 remained and have a score of another objective between 1 and 3.
since the 25b snapshots this didnt work anymore.
I think it was because c=1 or/and y=95. I assumed that when i search in y=95,c=1 it will choose the first entity which was found on y=95 (the new correct skulls).
It didn't chose the new summoned ones, but the skulls which got killed right after it. Because of that /say, /execute, etc failed...
Now i changed it to c=-1,r=1,y=95 and it selects the correct skulls again.
So i don't know if its really a bug anymore or I doesn't made it right from the Beginning.
Fact is that it worked before and now i had to change my contraption. So i guess there is something wrong (or was wrong and got fixed) with the y= -selector .
Now how should it work?
When i let execute an entity (WitherSkull) to search for another entity on another height-level and c=1 (no radius). Should it find itself or the other entity?
Is this still a concern in the current Minecraft version? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases. If this has been done, we can reopen the issue.
Keep in mind that the "Resolved"-Status on this ticket just means "Answered", and that we are waiting for further information on whether this issue still exists or not. We will reopen it as soon as the requested information has been delivered.
Seems like MC-80893
also doesnt work for /say