Keith
- keithicus420
- keithicus420
- America/New_York
- Yes
- No
MC-6641
Low![[Mod] markderickson](../../../data/avatars/users/18946.svg){kind=small}
When changing a player's team, a command block will return true when it shouldn't.
Steps to reproduce:
1. Create teams "testTeam1" and "testTeam2"
2. Place a command block with a comparator
3. Insert the command scoreboard teams join testTeam1 @p[team=testTeam2]
4. Activate the command block.What I expected to happen:
The command block would return true IF AND ONLY IF
1) the team exists
2) the player could be found and
3) was added to it.What happened:
The comparator turned on, even if the player isn't on the correct team (or any team). Note that although the comparator turns on, there is no text in the bottom box explaining that a player has been added to that team, because the command block didn't run the command successfully, so the comparator shouldn't turn on.----------------------
This might be part of a larger set of improperly returning comparator values. I noticed this issue began in the last few snapshots where I had not had the problem in early 1.8 snapshots. Please see
MC-15567for some other examples. I wanted to post this since that bug hasn't been updated in a while and the team joining issue only became a problem for me a few weeks ago.
Not sure what causes this bug, but it seems to occur after a few minutes of play. The blocks a chunk or so away change to this odd blueish texture.
Nonsolid blocks like leaves disappear entirely. Even farther blocks turn dark red.I've tried changing Minecraft video settings and nothing seems to make a difference. It may have something to do with my video card/video card drivers? Relogging does not work; I have to completely close Minecraft.
I can't describe how to replicate the problem because I wasn't doing anything in particular when I noticed it.
Not sure what causes this bug, but it seems to occur after a few minutes of play. The blocks a chunk or so away change to this odd blueish texture. Even farther blocks turn dark red. Leaves disappear entirely, grass seems to stay.
I've tried changing Minecraft video settings and nothing seems to make a difference. It may have something to do with my video card/video card drivers? Relogging does not work; I have to completely close Minecraft.
I can't describe how to replicate the problem because I wasn't doing anything in particular when I noticed it.
Working fine for me... check your mouse.
I believe this works for any thing that occupies two blocks (doors, beds). If Mojang fixes this, I'd like to see minecarts not drop themselves as items either.
This is not a bug; this occurs quite often in MC when you create a world, the game is updated, and you move into new chunks after the update. I'm almost positive the game goes about drawing the map differently after the new update, and that's why you see this. So play on, everything here is intended.
I didn't realize that strength of the signal was a problem. Thanks for linking this with the other, Tails.
Note: still present in 13w02b.
I used MCEdit filters to change the properties of the mob spawner, but I had no mods installed at the time I took the screenshot. Just tested in 13w07a, still exists.
Also confirmed in 1.5.
Confirmed for 13w17a.
Confirmed for 1.6.2. I've noticed the hunger bar also disappears for some reason...
Confirmed for 13w42b.
This issue may need to be reopened. It says it's fixed but I'm experiencing something similar in 14w10c. I'm trying to use /fill to switch around tile entities.
Steps to recreate my issue:
1. A command block with "fill ~ ~2 ~ ~ ~2 ~ dirt 0 replace air" returns "1 blocks filled", as it should.
2. Change "dirt" to "chest" will fail, returning "Data tag parsing failed: Unable to locate name/value separator for string: air".
3. Note that "fill ~ ~2 ~ ~ ~2 ~ chest 0" is successful, again returning "1 blocks filled".
If anyone would like to test, confirm, and reopen, please do. If I'm doing something wrong, please let me know.
Confirmed for 14w27b. It seems to matter what you were holding in survival mode. For example, I was holding a book in survival when I starting punching the block, quit punching, then switched to adventure, and the breaking animation still showed, but only while I was punching with the book in my hand.
Did you agree to the EULA in eula.txt file in the world folder?
Noticed this in 14w29b.
Confirmed for 14w29b.
It appears rx and rxm parameters aren't working either. Did the fix resolve that too?
Aw. I was a couple of hours late. Sorry for the duplicate.
This is not a bug. If you want to suggest a change, use the forums or make a suggestion on the minecraft suggestions subreddit.
Secondly, thrown items don't stack to 16.
Works as intended.
Blah, I just tested this in 14w30c and it's still broken.
In creative, I right-clicked on a spawner with a ghast egg. The ghast is still displayed outside of the spawner.
Would you mind updating the affected versions for
MC-15567since this is still an issue?Confirmed in 1.9.1-pre1.
Derp. Thought I was up to date, then I opened my Nvidia dashboard and realized I wasn't. I'm pretty sure this will fix the issue. Thanks, brotha.
I thought about that, but I couldn't come up with any conceivable reason that would be the case. And even if it was, why wouldn't they be able to run commands that non-ops can normally run, like /trigger, /me, or /say?
No, non-opped players definitely can run all commands through the signs (not just ones they could use in the command line) outside of spawn chunks. For example, I once built a store that used these signs to purchase, (the store had to be outside of spawn chunks) and the sign itself used a /setblock command, which ran a line of other command blocks.
Edit: this comment was directed to Tan Chin Cheern. I agree with Skylinerw. I also just tested this in 1.9.4 by deoping myself, leaving spawn, running a command through a sign. I haven't heard anything about this, so I doubt it's been fixed in any recent update.
@Henry Walker I am the server owner/admin. This is a problem with the game itself, not my sever.
Confirmed for 1.9.4.
Confirmed for 1.10.