minihilly
Assigned
Reported
Comments
I'd like to mention, since I don't think anyone mentioned this already, that the entites can be targeted again just fine if you restart a server if in multiplayer, or relog from your singleplayer world if in singleplayer - this seems to make all entities affected by the bug working again with 100% reliability.
Obviously, though, having to relog out of a map or restart a server to temporarily resolve the problem (as it can happen again even shortly after a server restart/singleplayer relog) isn't an option in many cases, what's worse is there's no automated means of avoiding/fixing or even detecting that this bug has occurred
I wasn't trying to say the problem would be barrier blocks, I was trying to point out their height, and we could replicate the issue by placing blocks at the top y-layer (y 255 i.e. y 256).
Probably an off-by-one error by the devs...
This looks a lot like an error we were getting on an existing world a friend was hosting.
In our case, the culprit was barrier blocks that were placed a y 256, removing them stopped the issue as far as we can tell.
I don't know if this is the exact same problem, though, but the error looks the same
This seems to be related to Mip-Mapping, if you have Mip-Mapping turned off, it'll cause some flickering.
This report needs updating; the bug is still present in the newest of these snapshots, too (14w17a, 14w18b, and 14w19a).
This report needs updating; the bug is still present in the newest of these snapshots, too (14w17a, 14w18b, and 14w19a).
This seems to happen either if the objective is new (added since 14w11a), or if the player is new - but I'm having a hard time recreating the issue, it seems to sometimes occur at random points; a player may have valid scores one login, but invalid scores the next[?]
It's notable that if you do a simple [EDITED]:
/scoreboard objectives add myObjective dummy
[should default all players to 0]
/say @a[score_myObjective_min=0]
[returns no players; expected all online players to be listed]
/say @a[score_myObjective=0]
[also returns no players; expected all online players to be listed]
You will find that the player(s) this may have affected will not show up for either /say, meaning they either have no score, or an invalid score in the scoreboard.
If I can find clearer steps to reproduce, I'll edit this post.
EDIT: Seems just creating brand-new objectives does the trick, but I don't know how this bug applies to previously-created objectives (even though it seems to have some effect).
ALSO:
This bug may be related to: https://bugs.mojang.com/browse/MC-50601
I still have this problem in 1.13 pre 3