Command API: Function based

The same result achieved in the Class-based wiki-page can be obtained using the function-based approach. Specifically, this is useful if you have one node command and many children that belong to it.

Here's an example:

public class QuakeArenaCommands {
    // ================================================================================
    // create <arena>
    // ================================================================================
    @AsCommand(
            description = "Creates a new arena.",
            aliases = {"c"},
            sender = SenderType.PLAYER
    )
    public void create(Player player, String arena) { // Automatically handles the <arena> parameter.
        // (...) Does some stuff to actually create the arena...
        player.sendMessage(GREEN + "Arena created.");
    }

    // ================================================================================
    // arena delete <arena>
    // ================================================================================
    @AsCommand(
            description = "Deletes an arena."
            alaises = {"d", "rm", "remove"},
            //sender = SenderType.ALL (by default)
    )
    public void delete(CommandSender sender, String arena) {
        // (...) Does some stuff to delete the arena...
        player.sendMessage(GREEN + "Arena removed: " + arena.getId());
    }

There's no way to create a functional node command, we have keep the QuakeCommand we've created before:

public class QuakeCommand extends NodeCommand {
    public QuakeCommand() {
        super("quake");

        setDescription("The main Quake command.");
        //setSenderType(SenderType.ALL);
        addAliases("q");

        // Appends to the node the list of commands returned by FunctionalCommand#load.
        append(FunctionalCommand.load(new QuakeArenaCommands())); // <---
    }
}

After registering QuakeCommand as we did before, we'll obtain the following commands:

/quake create <arena>
/quake delete <arena>

Function-based is better than Class-based

Using this approach is more powerful than creating classes, here some advantages:

• You don't have to take care of args parsing, the API does it for you. Handling also eventual syntax errors.
• Auto-generates the usage that is displayed by the help command.
• Less verbosity, you don't have to create one class for every command you have.
• Embedded management of tab-complete for parameters.

Parameter types to use

By itself, Uppercore supports the following types of parameters:

• Primitives: boolean, char, byte, float, double, short, int, long, String, String[].
• Some Bukkit's utils: Color, Enchantment, Material, Sound, Vector

It is also possible to include your own parameter parsers.