Non-staff donors unable to use /summon or /teleport

Issue #182 resolved
xArches created an issue

When a normal player (obsidian and up) attempt to /summon or /teleport a player upon the acceptance of the request it say "unknown command". It doesn't say "player has been teleported to player", just that the command is unknown AFTER the other player has accepted the request.

Comments (7)

  1. Riot

    Sorry what? So although you say "unable to use", you actually mean /summon and /teleport do actually work, and send a request as expected? And then after they have worked, and the request has been created, the process of accepting it fails and sends an error to the sender?

    If so, i wish you guys would finally learn to report bugs based on what actually happens, like I've been asking you for months, and not state with total assurance that someone is "unable to use" a command while in the same breath reporting it succeeded...

    So what actually happens when you type /teleport? And what actually happens when you type /tpaccept? And which really has the bug?

  2. Riot

    Ok cool. So what you actually mean by "it does not work" with regards to /summon and /teleport is "/summon and /teleport work absolutely normally, and return correct responses. On the other hand, /acceptteleport and /acceptsumon return correct responses also but fail to transport you."

    So who can and who can't use /accepptteleport successfully?

  3. xArches reporter

    From what I've experienced, when the /teleport or /summon is sent by a staff member, anyone can accept it. Normal players, other staff and so on. However when the /teleport or /summon is sent by a player to a staff member or another player it gives the "unknown command" error.

  4. Riot

    Rather than generalising, can you give me specific names of pairs of sender and recipient that do work, and sender and recipient that don't work? Then I can track down the issue. But it's looking like canary / vanilla tp command is at fault.

  5. Log in to comment