Varieties of /teleport create ambiguities for tab-completion and syntax highlighting

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 ?

[21:39:02 WARN]: Ambiguity between arguments [teleport, destination] and [teleport, targets] with inputs: [Player, 0123, @e, dd12be42-52a9-4a91-a8a1-11c01849e498]
[21:39:02 WARN]: Ambiguity between arguments [teleport, location] and [teleport, destination] with inputs: [0.1 -0.5 .9, 0 0 0]
[21:39:02 WARN]: Ambiguity between arguments [teleport, location] and [teleport, targets] with inputs: [0.1 -0.5 .9, 0 0 0]
[21:39:02 WARN]: Ambiguity between arguments [teleport, targets] and [teleport, destination] with inputs: [Player, 0123, dd12be42-52a9-4a91-a8a1-11c01849e498]
[21:39:02 WARN]: Ambiguity between arguments [teleport, targets, location] and [teleport, targets, destination] with inputs: [0.1 -0.5 .9, 0 0 0]

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.