MC-156419Command syntax: /teleport .. facing tab suggestion is invalid and incorrect
As we know, in command line arguments braces mean <required argument> and [optional argument], and additionally | in [1|2|3] and <1|2|3> means a selection of mutually exclusive arguments, which true for most of Minecraft's commands. Now, look at the situation bellow:
As seen on the screenshot, the teleport command syntax suggestion makes no sense. It means, literally:
Optional argument: either Facing or required Rotation
Basically, there a pair of optional arguments, one of which is mandatory to be chosen, which wrong both because the second option doesn't even exist and the suggestion of a "mandatory option" makes no logical sense.
Judging by the actual command syntax, the correct suggestion should be
[facing <entity|x y z>] and typing entity should lead to a suggestion of entities or selectors like with the target argument (which, by the way, doesn't happen here unlike all other entity arguments in the game)
When the facing argument is entered, the command syntax continues to defy logic:
It then gives an optional mandatory argument, which is actually not optional. The same appears to show up for most of the game's commands - optional arguments appear to either not have any braces, or wrapped in both [optional] and <required>
Created Issue:
Command syntax: /teleport .. facing tab suggestion is invalid and incorrect
As we know, in command line arguments braces mean <required argument> and [optional argument], and additionally | in [1|2|3] and <1|2|3> means a selection of mutually exclusive arguments, which true for most of Minecraft's commands. Now, look at the situation bellow:
As seen on the screenshot, the teleport command syntax suggestion makes no sense. It means, literally:
Optional argument: either Facing or required Rotation
Basically, there a pair of optional arguments, one of which is mandatory to be chosen, which wrong both because the second option doesn't even exist and the suggestion of a "mandatory option" makes no logical sense.Judging by the actual command syntax, the correct suggestion should be{{ }}
[facing <entity|x y z>] and typing entity should lead to a suggestion of entities or selectors like with the target argument (which, by the way, doesn't happen here unlike all other entity arguments in the game)When the facing argument is entered, the command syntax continues to defy logic:
It then gives an optional mandatory argument, which appears to be true for most of the game's commands. Optional arguments appear to either not have any braces, or wrapped in both [optional] and <required>
Attachments2
image-2019-07-10-16-38-34-480.png
As we know, in command line arguments braces mean <required argument> and [optional argument], and additionally | in [1|2|3] and <1|2|3> means a selection of mutually exclusive arguments, which true for most of Minecraft's commands. Now, look at the situation bellow:
As seen on the screenshot, the teleport command syntax suggestion makes no sense. It means, literally:
Optional argument: either Facing or required Rotation
Basically, there a pair of optional arguments, one of which is mandatory to be chosen, which wrong both because the second option doesn't even exist and the suggestion of a "mandatory option" makes no logical sense.Judging by the actual command syntax, the correct suggestion should be{{ }}
[facing <entity|x y z>] and typing entity should lead to a suggestion of entities or selectors like with the target argument (which, by the way, doesn't happen here unlike all other entity arguments in the game)When the facing argument is entered, the command syntax continues to defy logic:
It then gives an optional mandatory argument, which appears to be true for most of the game's commands. Optional arguments appear to either not have any braces, or wrapped in both [optional] and <required>As we know, in command line arguments braces mean <required argument> and [optional argument], and additionally | in [1|2|3] and <1|2|3> means a selection of mutually exclusive arguments, which true for most of Minecraft's commands. Now, look at the situation bellow:
As seen on the screenshot, the teleport command syntax suggestion makes no sense. It means, literally:
Optional argument: either Facing or required Rotation
Basically, there a pair of optional arguments, one of which is mandatory to be chosen, which wrong both because the second option doesn't even exist and the suggestion of a "mandatory option" makes no logical sense.Judging by the actual command syntax, the correct suggestion should be{{ }}
[facing <entity|x y z>] and typing entity should lead to a suggestion of entities or selectors like with the target argument (which, by the way, doesn't happen here unlike all other entity arguments in the game)When the facing argument is entered, the command syntax continues to defy logic:
It then gives an optional mandatory argument, which appears to be true for most of the game's commands. Optional arguments appear to either not have any braces, or wrapped in both [optional] and <required>
As we know, in command line arguments braces mean <required argument> and [optional argument], and additionally | in [1|2|3] and <1|2|3> means a selection of mutually exclusive arguments, which true for most of Minecraft's commands. Now, look at the situation bellow:
As seen on the screenshot, the teleport command syntax suggestion makes no sense. It means, literally:
Optional argument: either Facing or required Rotation
Basically, there a pair of optional arguments, one of which is mandatory to be chosen, which wrong both because the second option doesn't even exist and the suggestion of a "mandatory option" makes no logical sense.Judging by the actual command syntax, the correct suggestion should be
{{ }}
[facing <entity|x y z>] and typing entity should lead to a suggestion of entities or selectors like with the target argument (which, by the way, doesn't happen here unlike all other entity arguments in the game)When the facing argument is entered, the command syntax continues to defy logic:
It then gives an optional mandatory argument, which appears to be true for most of the game's commands. Optional arguments appear to either not have any braces, or wrapped in both [optional] and <required>
As we know, in command line arguments braces mean <required argument> and [optional argument], and additionally | in [1|2|3] and <1|2|3> means a selection of mutually exclusive arguments, which true for most of Minecraft's commands. Now, look at the situation bellow:
As seen on the screenshot, the teleport command syntax suggestion makes no sense. It means, literally:
Optional argument: either Facing or required Rotation
Basically, there a pair of optional arguments, one of which is mandatory to be chosen, which wrong both because the second option doesn't even exist and the suggestion of a "mandatory option" makes no logical sense.Judging by the actual command syntax, the correct suggestion should be
[facing <entity|x y z>] and typing entity should lead to a suggestion of entities or selectors like with the target argument (which, by the way, doesn't happen here unlike all other entity arguments in the game)When the facing argument is entered, the command syntax continues to defy logic:
It then gives an optional mandatory argument, which appears tobe truefor most of the game's commands. Optional arguments appear to either not have any braces, or wrapped in both [optional] and <required>As we know, in command line arguments braces mean <required argument> and [optional argument], and additionally | in [1|2|3] and <1|2|3> means a selection of mutually exclusive arguments, which true for most of Minecraft's commands. Now, look at the situation bellow:
As seen on the screenshot, the teleport command syntax suggestion makes no sense. It means, literally:
Optional argument: either Facing or required Rotation
Basically, there a pair of optional arguments, one of which is mandatory to be chosen, which wrong both because the second option doesn't even exist and the suggestion of a "mandatory option" makes no logical sense.Judging by the actual command syntax, the correct suggestion should be
[facing <entity|x y z>] and typing entity should lead to a suggestion of entities or selectors like with the target argument (which, by the way, doesn't happen here unlike all other entity arguments in the game)When the facing argument is entered, the command syntax continues to defy logic:
It then gives an optional mandatory argument, which is actually not optional. The same appears to show up for most of the game's commands - optional arguments appear to either not have any braces, or wrapped in both [optional] and <required>
![[Mod] tryashtar](../../../data/avatars/users/41963.png){kind=small}
You're misunderstanding the meanings of the brackets. Angled brackets mean "argument" as opposed to a literal, square brackets mean optional.
So you can either type the literal word "facing" or whatever is valid for rotation. Either way, it's optional, hence the nested brackets.