Skylinerw

@unknown: that would not work as you would expect. value was used in order to prevent name and objective from being processed again as a caching mechanism. value being specified would have meant that both name and objective are ignored. The result would instead be listing all text in every value no matter what, so all of the selectors are ignored.

(Re-uploaded the videos to include extensions)

@unknown: in many other situations in Minecraft, an unspecified min or max will mean that it doesn't have to be checked at all. For example, signal_strength in the "target_hit" trigger does not require both a min and max to be specified:

{
    "criteria": {
        "custom_test_name": {
            "trigger": "minecraft:target_hit",
            "conditions": {
                "signal_strength": {
                    "min": 10
                }
            }
        }
    }
}

Thus it is a min of 10. A signal strength of 12 is more than 10, so it matches. Another example is the distance parameter for selectors, where the min is implicitly 0 and the max is also implicitly 2147483647.

Meaning in the situation with scores, the implicit values would be the upper and lower bound that scores can have (MIN_INT/MAX_INT). Or just not checked at all as the entity_scores condition is just that: a true/false condition, not a random number selection.

@unknown: there is already a case of splash potions affecting blocks: fire blocks. Fire blocks/coral blocks, are not and do not need to be block entities or regular entities for this to work in the same manner.

Sure, ticket's your now!

Please check your Options -> Chat Settings to ensure your chat is enabled.

Cannot reproduce in 20w07a using the equivalent execute if block. Please let us know if this can still be reproduced.

Cannot reproduce in 20w07a. Please let us know if this can still be reproduced.

@unknown: As violine1101 stated: "Also note that every comment edit sends a new email to every single person who watches this ticket."

You just sent out 936 emails. I recommend writing your comment in a text editor and finalizing it before submitting it to avoid this.

Do you have the chat display set to "hidden" in Options -> Chat Settings?

Armor stands are entities.

Do you have the chat display set to "hidden" in Options -> Chat Settings?

A number of those data packs are using the same namespace "main" and have the same functions within them, which includes an "init.mcfunction" that creates scoreboards. Depending on the order that the data packs are read in, the Coordinates HUD will not be able to create the objectives.

You should contact the developer of the data packs so that they may fix the namespaces such that each pack contains a unique namespace.

@unknown: Please stop removing and re-adding affected versions. Every time you do that, you send out an email to those watching the tickets per action. For example, with MC-2714, you had sent 42 emails (2 per watcher).

Cats are intentionally immune to fall damage.

As well, please do not upload dozens of near-identical images.

This is not a bug. Item display names use the JSON text component and you are copying the JSON into a different string.

Repeating/impulse command blocks can only activate a chain; they are not activated by a chain. Follow the arrow texture on the command blocks to determine the direction the chain travels. A chain command block can only be activated by a repeating or impulse command block or by another chain command block.

Does lowering the followRange to around 100 help? Keep in mind that a value of 1,000 is extremely large, typically being more blocks in each direction than are loaded. This is going to cause the server to slow down tremendously while it calculates pathfinding for what amounts to every single loaded block. What you might be seeing is the server simply not responding in order to move the skeleton. Lowering the followRange will determine if that's the issue.

@@unknown Cannot confirm. Can replicate it in 1.13.1 using the commands provided in the report.

EDIT: Oh, I see the issue. /say will output no matter what, even if the message is empty. Your message in the image is empty, meaning it did not select the villager while in its dying state.

This is still an issue, however it's a little harder to test because now the dimensions seemingly load in a different order: nether -> end -> overworld (requiring the use of /forceload in the nether/end while standing in the overworld), though I'd prefer separate confirmation on that order. I should clarify that sort=nearest is necessary to replicate selectors prior to 1.13, which were sorted by distance.

@@unknown, to give a more clear example of the issue: imagine you sort by nearest with the intention of selecting the single entity directly in front of you. Instead, it selects an entity in a completely different dimension. I suppose it's based on semantics on what you would consider "nearest".