MC-59778/scoreboard players test does not go lower than -1
When I used this command:
/scoreboard players test fakeplayer testscore -1 -100
It outputs a:
The number you have entered (-100) is too small, it must be at least -1
I expected it to work for negative numbers because of the the new .json signs, if you have a remove player sign and because the player is fake, you cannot target them in any other way to set their score to 0 (because for example on a join game sign there is a remove player sign, if you hit it too much it will go into negative numbers and there is no way to have a negative player!) other than by using test that does not work for numbers lower than -1.
What I was expecting when I used
/scoreboard players test fakeplayer testscore -1 -100
was something like
Score -3 is in range -1 to -100
If you could please fix this bug it would be awesome to all mapmakers who want to use this in books and signs like myself!
Thanks
~TheDestruc7i0n
Created Issue:
/scoreboard players test does not go lower than -1
When I used this command:
/scoreboard players test fakeplayer testscore -1 -100
It outputs a:
The number you have entered (-100) is too small, it must be at least -1
I expected it to work for negative numbers because of the the new .json signs, if you have a remove player sign and because the player is fake, you cannot target them in any other way to set their score to 0 other than by using test that does not work for numbers lower than -1.
What I was expecting when I used
/scoreboard players test fakeplayer testscore -1 -100
was something like
Score -3 is NOT in range -1 to -100
If you could please fix this bug it would be awesome to all mapmakers who want to use this in books and signs like myself!
Thanks
~TheDestruc7i0n
Attachments2
When I used this command:
/scoreboard players test fakeplayer testscore -1 -100
It outputs a:
The number you have entered (-100) is too small, it must be at least -1
I expected it to work for negative numbers because of the the new .json signs, if you have a remove player sign and because the player is fake, you cannot target them in any other way to set their score to 0 (because for example on a join game sign there is a remove player sign, if you hit it too much it will go into negative numbers and there is no way to have a negative player!) other than by using test that does not work for numbers lower than -1.
What I was expecting when I used
/scoreboard players test fakeplayer testscore -1 -100
was something like
Score -3 is NOT in range -1 to -100
If you could please fix this bug it would be awesome to all mapmakers who want to use this in books and signs like myself!
Thanks
~TheDestruc7i0n
When I used this command:
/scoreboard players test fakeplayer testscore -1 -100
It outputs a:
The number you have entered (-100) is too small, it must be at least -1
I expected it to work for negative numbers because of the the new .json signs, if you have a remove player sign and because the player is fake, you cannot target them in any other way to set their score to 0 (because for example on a join game sign there is a remove player sign, if you hit it too much it will go into negative numbers and there is no way to have a negative player!) other than by using test that does not work for numbers lower than -1.
What I was expecting when I used
/scoreboard players test fakeplayer testscore -1 -100
was something like
Score -3 is
NOTin range -1 to -100If you could please fix this bug it would be awesome to all mapmakers who want to use this in books and signs like myself!
Thanks
~TheDestruc7i0n
Well it seems the first number can go very low, closing.
You can use /scoreboard players test player obj -100 -1
This bug report is just a math fail. The command is: scoreboard players test <player> <objective> <min> [max]
-1 is greater than -100 so you have them backwards.
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.
Ticket resolved as incomplete, because no answer in a reasonable amount of time (1+ year), if it still happens, please update the ticket.