Add support for wildcards about commandbouncer HOT 9 OPEN

Aye aye Cap'n!

from commandbouncer.

@PSGS BUMP 🔔

from commandbouncer.

What do you mean by "Add support for wildcards"?

from commandbouncer.

Add support for people to do: cmd1: a_command *
And the * would be all the arguments.

could also be used like this: cmd1: * arg1 arg2 arg3

from commandbouncer.

I see. Thanks :)

from commandbouncer.

In CommandListener.java, e.getMessage().equalsIgnoreCase("/" + plugin.getConfig().getString("cmd" + a)) should check the whole command message, including arguments, as the event being handled is PlayerCommandPreprocessEvent. Bukkit.getServer().dispatchCommand(Bukkit.getPlayer(e.getPlayer().getName()), replaceinput2); should also dispatch the whole command from a string, as if it was a raw command entered by a player.

Is getConfig().getStringList("player" + a).get(i).toString(); the reason why extra arguments can't be entered? I don't see where I need to add support for wildcards.

from commandbouncer.

How do you think they'll be able to act on every possible argument to a command like /ban for example?
/ban psgs /ban Notch /ban carlgo11 /ban Koala
They would need to add a cmd for every possible command. At least that's how they'd have to do atm. There for we need wildcards :P

from commandbouncer.

We need to convert wildcards from the cmd string in the config. Not the in game command.

from commandbouncer.

Oh, wow. I made a huge mistake...

from commandbouncer.