Minecraft
  1. Minecraft
  2. MC-101249

Target selectors ignore invalid arguments

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Resolution: Fixed
    • Affects Version/s: Minecraft 1.9.2, Minecraft 1.9.3 Pre-Release 1, Minecraft 16w35a, Minecraft 16w39c
    • Fix Version/s: Minecraft 16w41a
    • Security Level: Minecraft - Public (Viewable by everyone)
    • Labels:
    • Environment:

      Win 10

    • Confirmation Status:
      Confirmed

      Description

      "@e[customName=Xephos]" works EXACTLY the same as "@e". This causes extreme problems, like when using the "kill" or "tp" command. This caused me to teleport all entities on my friend's realm to one spot. It will take a while to fix this.

      What I expected: The command fails due to an invalid argument.
      What happened: The command completely ignored the argument, and teleported every entity.

        Activity

        Show
        [Mod] redstonehelper added a comment - WAI: https://bugs.mojang.com/browse/MC-106842?focusedCommentId=329385&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-329385
        Hide
        [Mod] Torabi added a comment -

        See [Mojang] Grum (Erik Broes)'s comment on MC-106842:

        It now keeps parsing and just ignored any invalids.

        Show
        [Mod] Torabi added a comment - See [Mojang] Grum (Erik Broes) 's comment on MC-106842 : It now keeps parsing and just ignored any invalids.
        Hide
        Harrison Martinson added a comment - - edited

        It is way too risky to use the @e selector with commands like kill and tp. I never use it. People with dyslexia might consider the @e selector unusable and therefore pointless, because one mistake ruins all entities. It would be easy to change the parser, and a lot safer.

        If a command doesn't work as you want it to, and you don't realize that, would you want the command to fail and give an error message so that it doesn't mess up anything, and let you know you messed up, or would you rather mess up the world?

        I'm sorry if this is wasting your time, but this is really important, at least to me.

        Are you guys (including Grum) willing to reconsider if this is WAI or not? Or should I give up, even if I bring up an entirely new point?

        Show
        Harrison Martinson added a comment - - edited It is way too risky to use the @e selector with commands like kill and tp. I never use it. People with dyslexia might consider the @e selector unusable and therefore pointless, because one mistake ruins all entities. It would be easy to change the parser, and a lot safer. If a command doesn't work as you want it to, and you don't realize that, would you want the command to fail and give an error message so that it doesn't mess up anything, and let you know you messed up, or would you rather mess up the world? I'm sorry if this is wasting your time, but this is really important, at least to me. Are you guys (including Grum) willing to reconsider if this is WAI or not? Or should I give up, even if I bring up an entirely new point?
        Hide
        [Helper] Fabian Röling added a comment -

        Remind them again in a year or when the first 1.12 snapshot comes out or something like that.

        Show
        [Helper] Fabian Röling added a comment - Remind them again in a year or when the first 1.12 snapshot comes out or something like that.
        Hide
        [Mojang] Grum (Erik Broes) added a comment -

        This will now make the command fail telling you which argument caused it.

        Show
        [Mojang] Grum (Erik Broes) added a comment - This will now make the command fail telling you which argument caused it.

          People

          • Assignee:
            [Mojang] Grum (Erik Broes)
            Reporter:
            Harrison Martinson
          • Votes:
            5 Vote for this issue
            Watchers:
            10 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:
              CHK: