Uploaded image for project: 'Minecraft (Bedrock codebase)'
  1. Minecraft (Bedrock codebase)
  2. MCPE-169057

Execute if score comparisons fail to run with multiple selectors

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Works As Intended
    • None
    • 1.19.80.22 Preview, 1.19.80.21 Preview, 1.19.71, 1.19.72
    • None
    • Unconfirmed
    • Multiple

      When using the new execute syntax, the if score condition does not allow for either score in a comparison (> or <) to have multiple entities selected. This is not coherant with Java Edition, but limits players creativity and therefore quality of their maps/creations.

       

      Steps to reproduce:

      1. Open a world with commands enabled
      2. Run command /scoreboard objectives add somescoreboard dummy
      3. Run command /summon pig
      4. Run command /summon pig
      5. Run command +/summon cow
        +
      6. Run command +/scoreboard players add @e[type=!player] somescoreboard 1
        +
      7. Run command /scoreboard players add @e[type=pig] somescoreboard 50
      8. Run either command:
        • /execute as @s if score @e[type=pig] somescoreboard > @e[type=cow] somescoreboard run say The pigs beats the cow!
        • execute as @s if score @e[type=cow] somescoreboard < @e[type=pig] somescoreboard run say The pigs beats the cow!

      Observation:

      A syntax error is given:

      +Only one entity is allowed, but the provided selector allows more than one
      +

       

      Expected result:

      The message "The pigs beats the cow!" should display in chat since all of the selectors in @e[type=pig] have a value greater than the single cow's value.

      Why is this important?
      This specific execute condition is extremely useful in determining which entity/player has the highest value, for example, a score in a minigame map. Without this condition working as proposed, players find it hard to determine which entity/player has the highest score.

            Jordanparki7 jordanparki7
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: