You can use the new sub commands system by just add a new section 'Sub_Commands' to your original normal command and remove all keys expect for aliases. like this:
Code (YAML):
MyCommandGroup:
Aliases
:
[mcg
]
Sub_Commands:
Cool_Message:
Aliases
:
[
]
Usage
:
""
# The time between each command execution.
# Example: 10 Seconds.
# Example2: 2 Minutes
# Example3: 5 hours.
# Example 4: 6 Days.
Cooldown
:
"0 seconds"
#Set to null to make this commands allowed for everyone.
Permission
: null
# Put '/' before the command to make this command perform by the player, otherwise it will be performed from the console.
# Placeholders: 1.{player}.
# 2.{arg:<#>:[Type]} : valid types: player (reads the arg # as a player name),
# number (reads the arg # as a number), boolean (reads the arg # as a boolean),
# world (reads it as a world name), enum (see number 3).
# (TO Do) 3. {arg:#:enum:["enum1", "enum2", "enum3"]}: reads the arg as an enum, if the enum list doesn't contains the arg# it throws an error message.
# Note: arguments numbers starts from 0 and not 1. so for example if 'MyCommand MyPlayer' is performed, the 'MyPlayer' argument number is 0.
# Note 2: put '*' to make this argument required. or don't put it and specify the replacement after the type or arg number. (see command 3).
Commands
:
-
"give {player} diamond"
#These will be sent when this command used as a reply.
Reply_Messages
:
-
"&6&lCool Message &5&lfor cool people!!"
Code
:
[
]
This will allows your to use command '/mcg cool_message'.
Please note that once the 'Sub_Commands' section is added to a command section, the plugin will read it as a command group that has subcommands.