Varieties of /teleport create ambiguities for tab-completion and syntax highlighting
The different syntaxes of /teleport introduce ambiguities for tab completion and syntax highlighting.
- Is the first argument destination or targets? "/tp @p <tab>" doesn't give tab completions for the <destination> argument. "/tp @a" doesn't complain that the <destination> argument may only return one entity.
- Is the first argument a player name or part of a set of coordinates? Attempting to teleport the player 1234321 to 0 0 0: type "/teleport 1234321" and start typing in the coordinates, after the y-coordinate, "1234321 0 0" will be highlighted as one argument even though it isn't.
- Is the second argument a player name or part of a set of coordinates? When I want to teleport myself to 0 0 0, I type "/teleport @p". After the x coordinate, it highlights the 0 in "/teleport @p 0" as a valid argument.
This could be fixed by introducing keywords or even subcommands like it was done to avoid ambiguities in /execute, or like it was done in /data.
Linked Issues
is duplicated by5
MC-123963Weird and repetitive help text when using ^ in coordsDuplicateMC-130811/tp command not showing valid inputs and facing does not workDuplicateMC-135624"/help teleport" doesn't show "facing"DuplicateMC-151076The second argument of the teleport command gives no suggestionsDuplicateMC-153576Can't enter Y or Z coordinates in command blocksDuplicate
Normal![[Mod] redstonehelper](../../../data/avatars/users/10122.svg){kind=small}
LowCreated Issue:
Varieties of /teleport create ambiguities for tab-completion and syntax highlighting
The different syntaxes of /teleport introduce ambiguities for tab completion and syntax highlighting.
1. Is the first argument destination or targets? "/tp @p <tab>" doesn't give tab completions for the <destination> argument. "/tp @a" doesn't complain that the <destination> argument may only return one entity.
2. Is the first argument a player name or part of a set of coordinates? Attempting to teleport the player 1234321 to 0 0 0: type "/teleport 1234321" and start typing in the coordinates, after the y-coordinate, "1234321 0 0" will be highlighted as one argument even though it isn't.
3. Is the second argument a player name or part of a set of coordinates? When I want to teleport myself to 0 0 0, I type "/teleport @p". After the x coordinate, it highlights the 0 in "/teleport @p 0" as a valid argument.This could be fixed by introducing keywords or even subcommands like it was done to avoid ambiguities in /execute.
clones
The different syntaxes of /teleport introduce ambiguities for tab completion and syntax highlighting.
1. Is the first argument destination or targets? "/tp @p <tab>" doesn't give tab completions for the <destination> argument. "/tp @a" doesn't complain that the <destination> argument may only return one entity.
2. Is the first argument a player name or part of a set of coordinates? Attempting to teleport the player 1234321 to 0 0 0: type "/teleport 1234321" and start typing in the coordinates, after the y-coordinate, "1234321 0 0" will be highlighted as one argument even though it isn't.
3. Is the second argument a player name or part of a set of coordinates? When I want to teleport myself to 0 0 0, I type "/teleport @p". After the x coordinate, it highlights the 0 in "/teleport @p 0" as a valid argument.This could be fixed by introducing keywords or even subcommands like it was done to avoid ambiguities in /execute, or like it was done in /data.
The different syntaxes of /teleport introduce ambiguities for tab completion and syntax highlighting.
1. Is the first argument destination or targets? "/tp @p <tab>" doesn't give tab completions for the <destination> argument. "/tp @a" doesn't complain that the <destination> argument may only return one entity.
2. Is the first argument a player name or part of a set of coordinates? Attempting to teleport the player 1234321 to 0 0 0: type "/teleport 1234321" and start typing in the coordinates, after the y-coordinate, "1234321 0 0" will be highlighted as one argument even though it isn't.
3. Is the second argument a player name or part of a set of coordinates? When I want to teleport myself to 0 0 0, I type "/teleport @p". After the x coordinate, it highlights the 0 in "/teleport @p 0" as a valid argument.This could be fixed by introducing keywords or even subcommands like it was done to avoid ambiguities in /execute, or like it was done in /data.
The different syntaxes of /teleport introduce ambiguities for tab completion and syntax highlighting.
- Is the first argument destination or targets? "/tp @p <tab>" doesn't give tab completions for the <destination> argument. "/tp @a" doesn't complain that the <destination> argument may only return one entity.
- Is the first argument a player name or part of a set of coordinates? Attempting to teleport the player 1234321 to 0 0 0: type "/teleport 1234321" and start typing in the coordinates, after the y-coordinate, "1234321 0 0" will be highlighted as one argument even though it isn't.
- Is the second argument a player name or part of a set of coordinates? When I want to teleport myself to 0 0 0, I type "/teleport @p". After the x coordinate, it highlights the 0 in "/teleport @p 0" as a valid argument.
This could be fixed by introducing keywords or even subcommands like it was done to avoid ambiguities in /execute, or like it was done in /data.
relates to
relates to
relates to
![[Mojang] Nathan Adams](../../../data/assets/gravatar/dinnerbone.png){kind=small}
[Mojang] Nathan Adams![[Mod] tryashtar](../../../data/avatars/users/41963.png){kind=small}
is duplicated by
is duplicated by
is duplicated by
![[Mod] Pokechu22](../../../data/avatars/users/92931.png){kind=small}
[Mojang] Nathan Adamsis duplicated by
![[Mod] violine1101](../../../data/avatars/users/92858.png){kind=small}
is duplicated by
![[Mod] SPGoding](../../../data/avatars/users/44622.png){kind=small}
![[Mod] Greymagic27](../../../data/avatars/users/92875.png){kind=small}
![[Helper] Johnibur](../../../data/avatars/users/28381.png){kind=small}
![[Mod] Jarl-Penguin](../../../data/avatars/users/92849.png){kind=small}
![[Mojang] Adrian Östergård](../../../data/assets/gravatar/nighter.jpeg){kind=small}
![[Mod] LateLag](../../../data/avatars/users/92884.png){kind=small}
relates to
![[Mod] Chandler](../../../data/assets/gravatar/triwonder81.png){kind=small}
![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
![[Mod] ampolive](../../../data/avatars/users/18949.svg){kind=small}
![[Mod] markderickson](../../../data/avatars/users/18946.svg){kind=small}
![[Mod] EVGENSYPERPRO](../../../data/avatars/users/92853.png){kind=small}
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
relates to
relates to
relates to
![[Mojang] slicedlime](../../../data/assets/gravatar/slicedlime.jpeg){kind=small}
These warnings are logged on purpose to indicate that registered commands are ambiguous.
These specific warnings are caused by MC-124137.
You can ignore them.
[07:18:27] [main/WARN]: Ambiguity between arguments [teleport, destination] and [teleport, targets] with inputs: [Player, 0123, @e, dd12be42-52a9-4a91-a8a1-11c01849e498] [07:18:27] [main/WARN]: Ambiguity between arguments [teleport, location] and [teleport, destination] with inputs: [0.1 -0.5 .9, 0 0 0] [07:18:27] [main/WARN]: Ambiguity between arguments [teleport, location] and [teleport, targets] with inputs: [0.1 -0.5 .9, 0 0 0] [07:18:27] [main/WARN]: Ambiguity between arguments [teleport, targets] and [teleport, destination] with inputs: [Player, 0123, dd12be42-52a9-4a91-a8a1-11c01849e498] [07:18:27] [main/WARN]: Ambiguity between arguments [teleport, targets, location] and [teleport, targets, destination] with inputs: [0.1 -0.5 .9, 0 0 0] [07:18:27] [main/INFO]: Loaded 0 recipes [07:18:27] [main/INFO]: Loaded 0 advancements [07:18:27] [Server thread/INFO]: Starting minecraft server version 18w05a [07:18:27] [Server thread/INFO]: Loading properties [07:18:27] [Server thread/INFO]: Default game type: SURVIVAL [07:18:27] [Server thread/INFO]: Generating keypair [07:18:27] [Server thread/INFO]: Starting Minecraft server on *:25565 [07:18:27] [Server thread/INFO]: Using epoll channel type [07:18:27] [Server thread/INFO]: Preparing level "survival" [07:18:27] [Server thread/INFO]: Reloading ResourceManager: Default [07:18:28] [Server thread/INFO]: Loaded 466 recipes [07:18:28] [Server thread/INFO]: Loaded 509 advancements [07:18:28] [Server thread/INFO]: Preparing start region for level 0 [07:18:29] [Server thread/INFO]: Preparing spawn area: 97% [07:18:29] [Server thread/INFO]: Done (1.501s)! For help, type "help" or "?"
The suggestions issue is MC-124137, the facing issue is because you left out "entity"
Repetitive error messages still appear when typing anything invalid, however this is essentially caused by MC-124137
This is caused by the ambiguity in the teleport command, any other command works fine.
As such, this is a duplicate of MC-124137.
Er- never mind, it appears this affects all commands.
I think this is ultimately MC-124137
The only thing that's wrong is the error message, which is impossible to make more specific because the command is ambiguous. If you include limit=1 the command works fine.
Duplicate of MC-124137
Can confirm.
Also happens with commands other than /tp (such as /execute if entity ... as well, so it's not caused by the /tp ambiguity (MC-124137).
You need to add limit=1. The reason the command doesn't provide a more helpful error (like e.g. /spectate) is because of MC-124137
Duplicate of MC-124137
This is not a duplicate of MC-124137.
I reached out to the server provider. Turns out the PSU was going bad and the CPU compound between the CPU and heatsink had dried out and needed replacing/refreshing. The server is running ok now, no crashes or instability on vanilla 1.17 survival.
Please close this report.
I believe that this should be resolved as a duplicate of MC-124137. Not only is it the cause of this issue, but it would be impossible to fix that issue without fixing this one, meaning that they're the same bug. In addition, it doesn't really make sense to have a bug report for behaviour within something that's a bug anyway (e.g. A bug with TNT duplication wouldn't be reported since TNT duplication itself is a bug).
This bug is new, MC-124137 is not, so it's not a duplicate
Affects 18w20c
I'm not sure if this relates to this problem, but I've noticed in the logs that the game seems to issue these warnings every time:
[09:25:39] [Client thread/ERROR]: Realms module missing
[09:25:43] [Client thread/WARN]: Ambiguity between arguments [teleport, destination] and [teleport, targets] with inputs: [Player, 0123, @e, dd12be42-52a9-4a91-a8a1-11c01849e498]
[09:25:43] [Client thread/WARN]: Ambiguity between arguments [teleport, location] and [teleport, destination] with inputs: [0.1 -0.5 .9, 0 0 0]
[09:25:43] [Client thread/WARN]: Ambiguity between arguments [teleport, location] and [teleport, targets] with inputs: [0.1 -0.5 .9, 0 0 0]
[09:25:43] [Client thread/WARN]: Ambiguity between arguments [teleport, targets] and [teleport, destination] with inputs: [Player, 0123, dd12be42-52a9-4a91-a8a1-11c01849e498]
[09:25:43] [Client thread/WARN]: Ambiguity between arguments [teleport, targets, location] and [teleport, targets, destination] with inputs: [0.1 -0.5 .9, 0 0 0]
[09:25:43] [Client thread/INFO]: Loaded 0 recipes
This example is from the 1.13-pre2 version but I've noticed it in previous snapshots as well.
1.13-pre5, on server startup:
[23:56:57] [main/WARN]: Ambiguity between arguments [teleport, destination] and [teleport, targets] with inputs: [Player, 0123, @e, dd12be42-52a9-4a91-a8a1-11c01849e498]
[23:56:57] [main/WARN]: Ambiguity between arguments [teleport, location] and [teleport, destination] with inputs: [0.1 -0.5 .9, 0 0 0]
[23:56:57] [main/WARN]: Ambiguity between arguments [teleport, location] and [teleport, targets] with inputs: [0.1 -0.5 .9, 0 0 0]
[23:56:57] [main/WARN]: Ambiguity between arguments [teleport, targets] and [teleport, destination] with inputs: [Player, 0123, dd12be42-52a9-4a91-a8a1-11c01849e498]
[23:56:57] [main/WARN]: Ambiguity between arguments [teleport, targets, location] and [teleport, targets, destination] with inputs: [0.1 -0.5 .9, 0 0 0]
Still present in 1.13 full release. Is there anything for the server operator to do to resolve it?
Still present in 18w31a. Very confusing to see these at startup.
Confirmed in 32a.
Confirmed for 1.13.1. Just disabled the vanilla datapack, restarted MC, enabled the vanilla datapack and after every /reload (even after another restart) it spams those ambiguity messages in the log. (Maybe it did that earlier on, I just noticed that)
Very confusing error message. I thought it was nether portal related first, (i did have some desynced portals).
After some googling it seems like it's nothing to worry about and that it's a mojang bug.
Still in all 1.14 snapshots.
confirmed in 1.14.2
I still have this strange messages in the server console, but I dont use any teleport commands.
This messages happen on server start even when no player is logged in.
And I dont use any functions of datapacks. So why I get these warnings on server start ?
Those warnings are the game identifying that /teleport is an ambiguous command, because of the ability to do things like /tp x y z and /tp player x y z. It runs checks on all command definitions on server start to determine this. There is nothing you can do, and nothing to worry about.
Still in 19w37a.
@tryashtar I know that this messages are for teleport commands.
But the point is, in my world I have no teleport commands.
I dont use Commandblocks, and I dont have any datapacks what are using teleport commands, so why still get this message??
It is very confusing to get a bunch of warnings on each serverstart without the chance to fix this.
Because the commands still exist and are loaded into the game as a valid command.
@FVbico I know that the commands still exists, I follow the changelogs on each update.
The real question is, what can I do to avoid these warnings when I start my server ?
Nothing, except for wait for mojang to do something about it.
Yes. Sometimes a bug is coped with to slowly.
Confirmed for 1.16 Pre-release 2
In 1.16.1 and 20w29a.
Also /tp @s ~ ~ ~ <facing|rotation> can't be completed with tab(Intentional to "rotation")
Can confirm in 21w03a.
Still exists in 1.16.5 and 1.17.0.
Mojang, please can we get a Priority bump to clean up the console/error log? "Nothing to worry about" noise makes it harder to see real errors, so it's not really harmless. And it's been more than 3 years...
Also in 1.17.1... This gets really annoying on the server logs for sure, I keep on thinking the server is crashing on boot. As well as this, the weird entity tag starting dd12be always makes me think that there is some entity corruption or something... This really needs fixing for sure
The simplest fix I can think of: make the target entity a mandatory argument (so no /tp <pos> and no /tp <destination>) then /tp <entity> 0 will have 0 as destination, and /tp <entity> 0 0 will complain about a missing coordinate.
I recon people use the shortcut frequently, and will complain about it being lost; but people also use the /gamemode shortcuts/numbers and they were removed too (and they didn't even cause issues like the autocompletion). It'll just take those people a bit of getting used to, and there's no issues anymore.
Affects 1.18
Affects 1.18.1
Can confirm in 1.18.2.