WorldEdit

WorldEdit

Mods
43M Downloads

Command usage not being sent properly

u9g opened this issue ยท 3 comments

commented

WorldEdit Version

Bukkit-Official(7.2.8+6008-1246d61)

Platform Version

git-Paper-152 (MC: 1.18.1) (Implementing API version 1.18.1-R0.1-SNAPSHOT) (Git: 78999b5)

Confirmations

  • I am using the most recent Minecraft release.
  • I am using a version of WorldEdit compatible with my Minecraft version.
  • I am using the latest or recommended version of my platform software.
  • I am NOT using a hybrid server, e.g. a server that combines Bukkit and Forge. Examples include Arclight, Mohist, and Cardboard.
  • I am NOT using a fork of WorldEdit, such as FastAsyncWorldEdit (FAWE) or AsyncWorldEdit (AWE)

Bug Description

Running Bukkit.getCommandMap().getKnownCommands().get("brush").getUsage() (on paper) results in duplicated usage output (with any worldedit command). It always looks like this: /brush /brush <forest|butcher|paint|none|clipboard|gravity|heightmap|extinguish|sphere|raise|smooth|cylinder|set|apply|deform|lower|snow|biome>, showing the command, then the command with args.

Expected Behavior

I'd expect only the command with args to be shown as is done with every other native command like from spigot/paper/etc.

Reproduction Steps

Run

        String usage = Bukkit.getCommandMap().getKnownCommands().get("brush").getUsage();
        cs.sendMessage("Usage: " + usage);

on Paper, and watch the output be: Usage: /brush /brush <forest|butcher|paint|none|clipboard|gravity|heightmap|extinguish|sphere|raise|smooth|cylinder|set|apply|deform|lower|snow|biome>

Anything Else?

No response

commented

er, to be clear on that title, this is about whatever is stored in the bukkit api and not anything about what's sent to the client yes? does that string actually get used anywhere?

commented

er, to be clear on that title, this is about whatever is stored in the bukkit api and not anything about what's sent to the client yes? does that string actually get used anywhere?

I was going to use it for my plugin hence the problem, but yeah, this is a problem with what's being stored in the bukkit api, hence the title change.

commented

0ad3ab1