/tphere and /summon not working for user with only numbers in name

Issue #404 resolved
Sail Bird created an issue
  1. /tphere 419 and /summon 419
  2. I expected the user 419 to be teleported to my location
  3. The summon was sent and accepted, but the user was not teleported. There was no teleport for the /tphere either. This message was displayed to Anna: 2017-04-29 06:44:33 [INFO] You must specify which player you wish to perform this action on.

Comments (4)

  1. Anna Bakker

    Seems to be a vanilla/canary bug where it is thinking that the 419 at the start of /tp 419 Anna_28 is a coordinate, and that a player should be before it. This only happens when 419 is at the start of the teleport input, so when a player is trying to teleport 419 to them or 419 is teleporting to someone else.

    2017-05-04 22:41:45 [INFO] You must specify which player you wish to perform this action on.

    The --force option on /tphere I added awhile ago teleports the player fine though, as it executes a teleport from the player to coordinates instead of trying to teleport one player to another.

    For now I'll add a check for all number usernames to just use the --force option, but this is more of a bug with vanilla/canary teleport thinking that 419's username are coordinates.

  2. 419

    i suggested perhaps adding a fallback feature that attempts to resolve the players UUID and tp them based on that in a situation such as this.

  3. Log in to comment