Resolution note
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 "?"
Related issues
is duplicated by
relates to
Attachments
Comments


The output appearing for ambiguities is intended. The base issue causing the output is tracked in the linked ticket.

The logging of ambiguity was added today. That these errors are logged is by design, that they show in vanilla is caused by the linked ticket.

this happens usually when the server host has custom commands setup .. and it trying to configure them it seems to me.. my host gives this problem but the same world on my local lan server does not..