Coby Z
- CactusPuppy
- cactuspuppy
- America/Los_Angeles
- Yes
- No
MC-127508
Summary: Using entity selectors to filter by tag does not behave correctly when tags are removed and when testing for multiple tags.
Description: While testing for only one tag works as intended, when attempting to test for multiple tags (or test for the lack of a tag in addition to the presence of a tag), the game will incorrectly persist in believing the conditions of the selector are met despite the fact that the condition is no longer true.
How To Reproduce:
1) Start a new creative singleplayer world in 1.12.2
2) Run /give @p minecraft:command_block
3) Place down a command block and set the command block to run
title @a[tag=A,tag=!B] title "Hello" constantly (set Mode to Repeating / Unconditional / Always Active) Note that this command block should now attempting to show a title to every player who has the tag A and does not have the tag B.
4) Run /title @a times 0 20 0 in the chat to make the title appear onscreen instantly when the command block finds the selector to be true, and to make it quickly apparent that the selector has stopped being true.
5) Place down four more command blocks with the following commands in them (keep track of which one is which)
- Number One: scoreboard players tag @p add A
- Number Two: scoreboard players tag @p remove A
- Number Three: scoreboard players tag @p add B
- Number Four: scoreboard players tag @p remove B
6) Activate Command Block One. The title will now appear on screen (as expected)
7) Activate Command Block Three. The title will disappear from the screen (as expected)
8) Activate Command Block Two. The title will continue to not display (as expected)
9) Activate Command Block Four. The title will suddenly jump back onto the screen, despite the fact that the condition is NOT true. The player has neither Tag A nor Tag B, which is not what the command block should be checking for: has Tag A and does not have Tag B.The issue persists in the world even after reloading the world and/or restarting the game. The only option is to modify the repeating command block's entity selector, thus resetting the check the command block is performing. Unfortunately, I am unsure what code is causing this behavior.
Confirmed for 16w02a.
Confirmed for 16w04a, also the display name is not checked by the game code. What matters is that the string pointed to by container.minecart is not displaying, Marcono1234.
Confirmed for 1.9-pre2
It would appear that any achievement hinging on building an item is currently broken.
How to Reproduce:
1) Generate a new world in version 16w32a
2) Open Inventory to give yourself the Taking Inventory achievement
3) Punch a tree. Note that this does NOT give you the Getting Wood achievement
4) Run the command "/achievement give achievement.mineWood" to manually obtain the achievement
5) Create a crafting bench. Note again that this does NOT give you the Benchmarking achievement.
And so on. I haven't done much testing, but that's the status of things as is.
This may simply be a case of block lag. Without further information it is impossible to tell whether this is a bug that should be fixed or a machine limitations.
As a suggestion to improved your bug report, what did you expect to happen/what do you think was intended to happen?
What happens when you place the armor stand, and what were you expecting to happen?
More information if possible please. Was there a light level of seven or lower where the Enderman spawned? Can we absolutely rule out the possibility that it teleported from an underground cave while the world was loading?
Not sure if this helps, but with a server I was hosting on my computer, I forgot to properly halt the server before shutting down, and I came back to the chunks being swapped around, as you describe. Perhaps the issue is insufficient resources being dedicated to saving the chunks in the proper location? This is just a hypothesis, as I have very little knowledge of the inner workings of Java.
Huh. That's more than a little irritating, though I am glad to hear that the behavior will be what I expected in 1.13. Guess I'll have to find a workaround for now. Thanks for the insight FVbico!
Apologies for not providing more information or being more active about reading replies. At any rate, the bug appears to have been fixed in 1.13 Prerelease 1, so I am okay with the bug being marked as resolved. With regards to @Kumasasa's request to examine the logfile, nothing was logged, but I have attached the logfile here regardless.
MC-123968does not describe my issue, as I am unable to click back into the game to resume normal operation.2018-06-01-4.logEDIT:
MC-123968may actually be the issue I had, as I just checked and my overlay key was somehow reset to the tilde key, which I didn't think to check since I had a different keybind before. I have set the Overlay Lock keybind to something else and the issue has vanished. Thank you @tryashtar for realizing what the issue might be!To be clear, it was the Discord Overlay causing the issue. I have tested having the Overlay keybind set to Shift + ` (which makes ~ in-game but also triggers the overlay, causing the issue) and an alternative keybind (Ctrl + Numpad Period, which doesn't trigger the issue) in 1.13 pre-1.