#CustomChatCommands
CustomChatCommands is a plugin inspired by Bukkit’s RoleplayChat. It allows you to create your own commands which let the user chat in custom formats. A vanilla example of a chat format command is /me.
##Features
- Create your own commands!
- Supports permissions
- Not limited to just the player’s name and a message - you can use any number of command arguments you want
- Messages can be output to the player’s normal chat channel, or server-wide, or confined to a specific radius around the player
- Messages can be written in JSON, TextXML, or color-code format
Config
This is an example configuration node.
me {
aliases=[action]
args=1
format=ampersand
message="&e* <player> <arg1>"
permission="minecraft.command.me"
radius=0
}
aliases
is a list of aliases for the command. Optional.
args
is how many arguments the command has. The last argument used will be the rest of the command arguments combined. Optional, defaults to 0
.
format
is what format the message is in. Can be json
, xml
, or ampersand
. Optional, defaults to json
.
message
is the message that will be sent. Must be in the format described in format
. You can use the <player>
parameter for the player’s name, and the <argx>
parameter where x
is a number for argument x
of the command.
permission
is the permission that is required for the command to run. Optional, but a good bet is minecraft.command.me
for emote-type commands and minecraft.command.broadcast
for broadcast-type commands.
radius
is the radius around the player that the message can be seen in. Special cases: 0
means that the message will be output to the player’s normal chat channel, and -1
means that it will be seen server-wide. There may be a difference between the two, depending on your other plugins. Optional, defaults to 0
.
All this is also explained in the auto-generated config. All auto-generated commands also contain an example
tag, which prevents them from being loaded. This can be deleted if you wish to use the command.
The node named default
is not a command, but rather the default chat format. You can only use message
and format
, and the only supported arguments are <player>
and <arg1>
. Just like above, it will not take effect if example
is true, and it can be deleted if necessary.
Download
Changelog
1.0 First release
1.1 Config is now version 2, added support for XML and ampersand formats
1.2 Config is now version 3, added examples to auto-generated config as well as the example
tag, added to Plugin Releases forum
1.3 Config is now version 4, added /customchatcommands
(/ccc
) command for a shameless self-plug, and /ccc reload
to reload the config and commands, added support for default
for chat messages