Dynamic commands and improved registration

[PizzaCrust]

This commit adds registration handlers for implementations to handle command registration at any time, than just startup. This commit also adds dynamic commands called ICommand. It also fixes calling the same command name multiple times.

[phase]

What are the use of dynamic commands? I think having immutable ones would be safer.

[PizzaCrust]

Dynamic commands allows for plugins like Skript, to register commands dynamically after they parse the scripting language.

[minecrafter]

I suggest that interfaces not be used as they are not safe. Please use an immutable object instead.

[PizzaCrust]

Hmm. Probably like this:

Fountain.getServer().getCommandManager().newCommand("test-command").invokeHandler(() -> println("meow").register()

[phase]

Or an object. Objects are nice. We're using Java for a reason.

[PizzaCrust]

How would you propose to use an object for this?

[phase]

Not called Command but something like

public abstract class Command {

    public abstract String getName();

    public abstract void invoke(String[] args, CommandSender sender);

}

Which plugins can extend like

public class TestCommand extends Command {

    public String getName() { return "test"; }

    public void invoke(String args[], CommandSender sender) { System.out.println(Arrays.toString(args)); }

}

[PizzaCrust]

What's wrong with using builders?

Fountain.getServer().getCommandManager()
   .newCommand("test")
   .invokeHandler((args, sender) -> {})
   .generate();

[PizzaCrust]

Ok, removing builders.

[PizzaCrust]

Replaced with an abstract class.

[PizzaCrust]

Added the lines.

[phase]

Merged in https://github.com/FountainMC/FountainAPI/commit/73b702e2e72ceb808a32c8351d3032ffa93a0247