A sponge plugin for custom commands that can be created via a configuration file or a command, so that it is easy to use!

You have two ways to add a new command: You can edit the configuration file of the plugin or add a command ingame with the help of the addCommand.

To add a command ingame you need to use the addCommand (/addcmd <message...>). The first parameter is the name / identifier for the command, that you later need to edit or delete the command. The second parameter is a command that your users use to use the command, the last parameter is the message that is shown if the command is executed. To add a description, extended Description or a permission you need to edit the command with the editCmd.

Example: /addcmd tsCommand ts ts: ts.domain.tld

For adding a command with the help of the config (the ingame methode also writes into the config) you can easy copy the following example code into the config and replace the texts with yours. The example adds the same command as the command of the ingame example after using each of the ingame edit examples.

commands {
    tsCommand {
        commands=[
            ts
            ts3
        ]
        description="[{color:blue,text:\"shows the ts ip\"}]"
        extendedDescription="shows you the currned ip of the teamspeak server"
        message="[{color:blue,text:\"TS3:\"},{color:green,text:\" ts3.domain.tld\"}]"
        permission="cmd.ts3"
    }

    spectatorCommand {
        commands=[
            spectator
        ]
        description="changes to spectator"
        extendedDescription="changes your gamemode to the spectator mode"
        message="changed PLAYER.DISPLAY_NAME gamemode from PLAYER.GAMEMODE"
        permission="gm.spectator"
        serverCommands="/gamemode @p 3"
        otherPlayerPermission="gm.spectator.outher"
    }
}

To edit a command ingame you need to use the command /editcmd [key] [commandName] [value].

You can easy edit the node of the configuration file.

You only need to use the command /deletecmd to delete a command.

IMPORTANT: the command can not be restored and will be deleted immediately and permanent!

You can easy delete the node from the configuration file

You can use DataKeys in messages to send changing informations to the player, eg. the name of the player or the current amount of players on the server. To do this you only need to write the corresponding key into the message. If a player key is used in the message the command automatic gets a player parameter, so it can also be used as the console, if you don't want allow players to use this parameter you need to set a permission for this in the otherPlayerPermission setting of the command.

                      |                                                  |

SERVER.DATE | the currend date | 28.08.2015 SERVER.HAS_WHITELIST | if the whitelist is enabled | false SERVER.MINECRAFT_VERSION | the minecraft version the server is using | 1.8 SERVER.MOTD | MotD of the server | a minecraft server SERVER.ONLINE_MODE | if the online mode is active | false SERVER.PLAYER_ONLINE | current amount of online players | 42 SERVER.SLOTS | slots of the server | 100 SERVER.SPONGE_API_VERSION | the version of the spongeApi the server is using | 2.1-SNAPSHOT SERVER.TIME | the currend time | 18:43 SERVER.TYPE | does the server run on a server or a client | SERVER SERVER.VERSION | the version string with all informations | 1.8-1499-2.1DEV-584+unknown-b584.git-unknown

You can create a new line by adding \n to the position of the line break. In the JSON-format it must be in the text block.

Of course you can! Everything you need to do is copying the translation.properties file from the resource folder of github to the configuration folder of the plugin and change the texts to whatever you want them to be. If you translate them it would be nice if you would create a pull request with the translated file or send it via mail to lergin@gmx.de so everyone can use it.

Feel free to create a pull request if you want to add a feature. You can also translate the plugin into another language if you want to!

On the left hand site you can find the issue tracker of github, feel free to add one there. But make sure your using the latest version and that the bug isn't reported already ;)

Maybe. Just create an issue on the issue tracker and we will see :)