anchoring would not make sense when the position is not relative to an entity, thus having no eye or feel levels.
The same thing could be said for "execute positioned" isn't it?
"positioned ^ ^ ^1" would not make sense when there is no looking-direction of an entity. but that is solved by storing the rotation in the location context via "execute at" instead of executor context and provide a default value when no entity is supplied.
I'm under the impression that anything that changes execution location should follow "execute at" subcommand. So, anchoring would still make sense when making it relative to "execute at".
This is still an issue in 1.15 and this also affected /data storage as well.
Thanks! but I don't have Geforce experience install so it shouldn't be that.
Will try to install it and disable the overlay to see if that do anything.
MC-123029 issue is only partially overlapped this issue.
This issue focuses especially on how fence and wall don't connect to itself when disabling vanilla datapack but it's can still connect to other blocks.
Adding "damage: 1.0" to the model also seem to mess up the model entirely
Also happen in warm ocean (ocean with sand floor) even if there are no ravines nearby.
This also seem to happen when firework boosting out from swimming animation.
No, this fix since 17w46 i think but no mod have mark it as fixed.
@Auldrick No, i only have one monitor and the issues is somehow gone after I wipe out my computer.
Can confirm this I have this issue for a year and seem like only few people actually have this issue.
Still not working in 17w50a
The missing tag in the 3rd and 4th command is probably just my mistake when copying it over but ignoring that, your explanation is not correct.
The Slot NBT is not stored inside the
{tag: {...
}} field so it cannot be removed even if the field was set by the/data
command and in those commands, nothing is being created, it simply modifies the NBT value that already exists in the container that it can find with the given predicate.Though it has been far too long for me to remember what this bug report was about so if no one else has reported the same issue, it should be fine to close it.