mojira.dev
MC-50405

Checking for @a[score_x=0] fails after objective init

If a scoreboard objective (dummy) was added before 14w10a the initial score was zero.
Commands with identifiers like @a[score_test=0] don't work anymore before explicitly setting the score to 0.
In 14w08a this was working fine.

Way to reproduce:
1. /scoreboard objectives add test dummy
2. /tp @a[score_test=0] ~ ~10 ~ -> Nothing happens
3. /scoreboard players set <name> test 0
repeat step 2. -> Player gets teleported

In previous versions the player gets teleported before doing step 3.

Linked issues

Comments 4

Confirmed. Please add more labels, e.g.: "Zero", "Selector",.. so it will be seen more likely.

There is a difference between a score of 0 and no score at all for a player or entity.

So how are we able to define if a player already has a score? It was different before and it was a lot easier.

Make it how it were please :'(

Jannik R.

michael

Unconfirmed

command, initial, score, scoreboard, selector, zero

Minecraft 14w10b, Minecraft 14w10c, Minecraft 14w11a

Retrieved