[MC-50601] Scoreboard reset not equal to 0

Using a @a[score_test=0] argument doesn't affect players that have been reset with the "/scoreboard players reset <players>" command.

*What I expected to happen was*
The reset players would be considered as having a score of 0 and be affected by commands that use the @a[score_test=0] argument.

*What actually happened was*
they are not affected by the commands

*Steps to Reproduce* (example used in attached file)
1. create a scoreboard objective (/scoreboard objectives add test dummy)
2. set two commands on a clock
    Bottom: tell @a[score_test=0] testing
    Top: scoreboard players set @a[score_test=0] test 1
3. when using the (scoreboard players set @a test 0) the commands do what they should. saying "testing" and setting your test score to 1.
4. when reseting the score (scoreboard players reset @a) the commands does not affect you.

Linked issues

is duplicated by 11

MC-51848 Testfor player of score 0 is not equal anymore to a player with reseted score Resolved

MC-51983 Player score does not default to 0 in objectives. Resolved

MC-52654 Scoreboard cannot test 0 after reset Resolved

MC-53014 Scoreboard objectives don't work properly with command parameters Resolved

MC-54305 Minecraft 14w18a snapshot Scoreboard problems Resolved

6 more links

relates to 2

MC-51330 Selectors not working with scores of offline players Resolved

MC-55587 Scoreboard players don't reset properly when objective gets removed. Resolved

Attachments

Screen Shot 2014-03-08 at 6.18.06 PM.png

Screen Shot 2014-03-08 at 6.19.04 PM.png

Screen Shot 2014-03-08 at 6.19.15 PM.png

Comments 26

Stephen Kowalski 3/9/2014, 12:31:26 AM

Environment: Mac OSX 10.9.2 Java 7 update 51
I believe this is the same as the bug I'm experiencing. Here's another way to explain it:

In previous versions (confirmed in 1.7.5), executing the command "/scoreboard players set @a[score_ones=0] ones 1" would set all online players with score 0 or less AND all players who were not on the ones scoreboard.

in 14w10c, the same command only sets the score for players who are already on that scoreboard.

Stephen Kowalski 3/9/2014, 12:34:05 AM

Image 1: Showing two players online, one has no value for the ones objective, the other has 0.
Image 2: Showing the command to be executed "/scoreboard players set @a[score_ones=0] ones 1"
Image 3: Showing the results. The player with 0 in ones was set to 1. The player with no value for ones was not set.

Steve Bob 3/12/2014, 3:21:41 PM

Confirmed (on Windows 8)

minihilly 3/18/2014, 7:00:19 PM

Related to MC-51330 ?

kumasasa 3/18/2014, 8:42:22 PM

This behaviour may be intended, @unknown wrote in MC-50145:

Use "/scoreboard players reset * score" instead of "/scoreboard players set * score 0" to remove scores from the players.

16 more comments

Steve Bob 3/18/2014, 9:37:10 PM

Kumasasa, there's still the essue of spawned entities not having any score on objectives, instead of having it 0 as default as it should have.

Daan Verstraten 4/7/2014, 5:09:05 PM

Hey, I have been experiecing this problem also in 14w11b

Commandblock just don't seem to be doing anything at all
I used the map Remnant from fyreuk into the new snapshot and every commandblock is doing nothing.

M F 4/30/2014, 2:07:43 PM

This Bug should really be fixed or explained. It really makes me not being able to do a lot of stuff in command blocks.

Daan Verstraten 5/4/2014, 4:43:28 PM

I have noticed what is happing

it doesnt not notice @a[score_a=0] after the score got reset for the person but if you set the score to 0,

its start to notice the actuall score again.

Rebecca König 5/4/2014, 10:22:37 PM

If this actually is intended behavior it would be great to have some way to select players that don't have an objective set. Otherwise I see no way to initialize an objective automatically without resetting it for everyone.

Rebecca König 5/5/2014, 10:33:57 AM

Looking at it again it appears to be the same for objectives based on stats. For example, the following fails.

/scoreboard objectives add test stat.swimOneCm
/testfor @a[score_test=0]

I believe this to be contrary to how one would expect stats to work.

And it's still that way in 14w18b.

Rebecca König 5/12/2014, 8:48:41 AM

Confirmed for 14w19a.

Here's a suggestion to address this without changing the current functionality. Players that don't have the score set could be selected by omitting the value similar to how players without a team are selected. The 1.7 functionality could then be emulated with the following command.

/scoreboard players set @a[score_test=] test 0

minihilly 5/12/2014, 10:32:54 AM

This report needs updating; the bug is still present in the newest of these snapshots, too (14w17a, 14w18b, and 14w19a).

marcono1234 5/21/2014, 8:12:40 PM

Duplicates:
MC-53014
MC-54305
please close them 🙂

*Confirmed for 14w20b

M F 6/17/2014, 8:44:31 PM

Mojang? Can we get at least a sign that this is gonna stay like this or are you just gonna keep quiet?

michael 6/18/2014, 1:16:54 PM

the reset subcommand removes a score from a player completely. this is not the same as setting it to 0 using the scoreboard player set command.

Rebecca König 6/18/2014, 2:12:10 PM

But can you add a way to detect players that don't have the score then or is there a simple solution that I have missed? Currently I have to add another score to emulate the 1.7 behavior.

marcono1234 7/11/2014, 9:32:59 PM

Yes that is my question too how can we detect it than?

WolfieMario 8/26/2014, 3:51:02 AM

Using "/scoreboard players add <target> <objective> 0" will place the targets on the scoreboard with a default score of 0, while having no effect on targets who already have a nonzero score. Either use it on all players/entities when they initially spawn or enter a relevant area, or use it on them just before you intend to check their scores.

EDIT: For clarification, this is not a way to detect untracked entities, but rather, a way to render them trackable. That's a useful workaround for any score where 0 is your desired default value, as it was in previous versions.

If you actually want to detect untracked entities without giving them a score, create a separate "tracked" objective. Use "/scoreboard players add <target> tracked 1", where <target> includes the arguments "score_name_min=-2147483648,score_name=2147483647" (where "name" is the objective). Also use "/scoreboard players add <target> tracked 0", this time without the score arguments. Untracked players/entities in the objective "name" will have a tracked score of 0, while tracked players/entities will have a tracked score of at least 1.

marcono1234 10/12/2014, 4:01:54 PM

Great I know also a lot of work arounds, probably even more efficient ones than yours...
Examples:

Test for @e without a team AND NOW I WANT AN EXPLANATION!!! WHY DOES THIS WORK WITH TEAMS, BUT NOT WITH SCORES!?
/entitydata executed on @e's with for example a custom name to change their name

kumasasa 10/12/2014, 4:09:08 PM

No.

@unknown on 18/Jun/14:

the reset subcommand removes a score from a player completely. this is not the same as setting it to 0 using the scoreboard player set command.

Resolution		Works As Intended [ 6 ]
Assignee		@unknown
Status	Open [ 1 ]	Resolved [ 5 ]

marcono1234 10/12/2014, 4:51:25 PM

Can you also explain me why this should be WAI?

Alright maybe this works as intended, but then these bugs need to be fixed:

MC-61657 which is caused by this
MC-61662 which IS a bug, because you cannot test for this, even if it is NULL!

kumasasa 10/12/2014, 5:00:02 PM

???
Because

the reset subcommand removes a score from a player completely. this is not the same as setting it to 0 using the scoreboard player set command.

or with other words: Because @unknown coded this to work that way.

marcono1234 10/12/2014, 5:19:57 PM

Then it would be null... I guess

Each class variable, instance variable, or array component is initialized with a default value when it is created:
For all reference types, the default value is null.

http://stackoverflow.com/questions/2707322/what-is-null-in-java

marcono1234 10/13/2014, 8:27:34 AM

Would be very nice if I get an answer 🙂

BoxFigs 12/15/2014, 7:47:30 PM

It would be nice if we could test for a null score, like we can with teams:

@a[score_objective=]

In the meantime (or if it never happens), I have a workaround.

/scoreboard players set @a nullObjective 1
/scoreboard players reset @a[score_objective_min=0] nullObjective

Now, all players who have a null score for "objective" will have a score of 1 for "nullObjective".

The two commands must be run in the order listed, and both must be run before any command blocks looking for a player with a score of 1 for "nullObjective".