[MC-9733] Commandblock ignoring testfor @p[score_deaths_min=1 to 3] for Scoreboard - deathCount Created: 13/Feb/13 Updated: 29/Dec/17 Resolved: 20/May/13 |
|
| Status: | Resolved |
| Project: | Minecraft: Java Edition |
| Component/s: | None |
| Affects Version/s: | Snapshot 13w06a |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Christian Letz | Assignee: | Unassigned |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | command_block, scoreboard, testfor | ||
| Environment: |
Windows 8, Java 7 update 11 |
||
| Attachments: |
|
| Confirmation Status: | Unconfirmed |
| Game Mode: | Creative |
| Description |
|
I use this commands in Singleplayer and in (open to LAN) /scoreboard players add @p deaths 3 so i use a commandblock with: testfor @p[[score_deaths_min=3]] the two last commandblock have: i dont know is a feature or a bug,. you can see on a picture i press a button a commanblock see i have min 3 deaths, give energie on comparator this take a redstone torch off a two redstone line can update the last commanblocks. give me a item 276(dia swort) So i have 0!! deaths when i use a button now, a command block see i have not min 3 deaths BUT the command block ignore this and give energie on a comparator oO. when i use playerKillCount, totalKillCount, dummy,. a commandblock dont give energie on comperator. EDIT: Mh LOL i testing again the problem is, when i use and when i use and i can't set negativ argoments "testfor @p[[score_deaths_min=0]]" or lower. EDIT2: So when i leave a singleplayer world and start this world again,. then a problem with a commandblock is away. testfor @p[[score_deaths_min=1]] comandblock don't ignore a min level and i can set negativ argoments, but i must leav and rejoin the world |
| Comments |
| Comment by Tails [ 20/May/13 ] |
|
Unable to reproduce either. |
| Comment by WolfieMario [ 12/May/13 ] |
|
Cannot reproduce, 13w19a. The minimum score detection works perfectly for positive and negative numbers. |
| Comment by Christian Letz [ 01/Apr/13 ] |
|
added the logfile. end of log is, line 172. (13w06a) when I find the time I will check it. in 1.5.1 |
| Comment by Tails [ 18/Mar/13 ] |
|
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. |
| Comment by Christian Letz [ 14/Feb/13 ] |
|
Not Confirmed in 13w06a or 13w07a. I can not repeat this mistake. |