[MC-9670] /testfor @p[] won't accept multiple arguments Created: 12/Feb/13 Updated: 06/May/15 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: | Thomas Redwig | Assignee: | Unassigned |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | redstone | ||
| Environment: |
Windows 7 Ultimate x64 |
||
| Confirmation Status: | Unconfirmed |
| Game Mode: | Creative |
| Description |
|
When attaching a comparator to a command block with the code $testfor @p[ score_Kills_min=1, score_dummyName_min=1] the comparator doesn't give an output when both, none or one of the "ifs" is true. It only works for "testifs" with one parameter after the "@p[" |
| Comments |
| Comment by Tails [ 20/May/13 ] |
|
Unable to reproduce either. |
| Comment by WolfieMario [ 12/May/13 ] |
|
Agreeing with Kwin here; I think you're typing it with spaces in the command block, which is incorrect. I cannot reproduce this in 13w19a, so even if it was a bug at some point, it's fixed now. But I doubt this bug ever existed to begin with. |
| Comment by Kwin van der Veen [ 20/Apr/13 ] |
|
This is caused by the "spaces" within the arguments, so "/testfor @p |
| 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. |