Commands reference

Every command is configurable, you can change it into whatever you want by editing last options of config.yml.

By default, every command is based on a permission that is given only to operators by default.
So you must setup permissions before start to using them.

Command /party

/party is the main command of Parties, if you want to use that command without any sub-command you must have parties.user.help permission set.

Structure of the command: /party <sub command> [arguments]

Global commands

Sub-command	Permission	Description	Default on	Usable by console
`accept`	`parties.user.accept`	Accept a party invitation	Yes	No
`chat [on/off]`	`parties.user.chat`	Toggle on/off the party chat so you can directly write into global chat to send a message into party chat	Yes	No
`color <color>`	`parties.user.color`	Change the color of the party	No	No
`create <name>`	`parties.user.create`	Create a party with the given name	Yes	No
`create <name> [fixed]`	`parties.user.admin.create.fixed`	Create a fixed party with the given name	Yes	Yes
`delete <party>`	`parties.admin.delete`	Delete the party	Yes	Yes
`delete <party> [silent]`	`parties.admin.delete.silent`	Delete the party silently	Yes	Yes
`deny`	`parties.user.deny`	Deny a party invitation	Yes	No
`desc <new desc/remove>`	`parties.user.desc`	Set/remove description of the party	No	No
`follow [on/off]`	`parties.user.follow`	Toggle on/off the follow leader feature	No	No
`help [page]`	`parties.user.help`	Show help pages	Yes	No
`ignore [party]`	`parties.user.ignore`	Add/remove/show ignore parties	Yes	No
`info`	`parties.user.info`	Show information of your party	Yes	No
`info [party]`	`parties.user.info.others`	Show information of another party information	Yes	Yes
`invite <player>`	`parties.user.invite`	Invite a player into your party	Yes	No
`join <party> [password]`	`parties.user.join`	Join into a party with the given password	No	No
`join <party>`	`parties.admin.join.bypass`	Join into a party without type the password	No	No
`kick <player>`	`parties.user.kick`	Kick the player from your party	Yes	No
`kick <player>`	`parties.admin.kick.others`	Kick the player from his party	Yes	Yes
`leave`	`parties.user.leave`	Leave the party	Yes	No
`list [page]`	`parties.user.list`	List of online parties	No	Yes
`motd <new motd/remove>`	`parties.user.motd`	Set/remove the party motd	No	No
`mute [on/off]`	`parties.user.mute`	Toggle on/off party notifications	No	No
`password <new password>`	`parties.user.password`	Set/change the password of your party	No	No
`rank <player> <new rank>`	`parties.user.rank`	Change the player rank, must be into your party	Yes	No
`rank <player> <new rank>`	`parties.admin.rank.others`	Change the player rank	Yes	Yes
`reload`	`parties.admin.reload`	Reload Parties configuration files	Yes	Yes
`rename <new name>`	`parties.user.rename`	Rename your party	Yes	No
`rename [party] <new name>`	`parties.admin.rename.others`	Rename the party	Yes	Yes
`spy [on/off]`	`parties.admin.spy`	Toggle on/off spy so you can see all party messages	Yes	No
`version`	`parties.admin.version`	Show Parties information	Yes	Yes

Bukkit/Spigot only commands

Sub-command	Permission	Description	Default on	Usable by console
`claim <permission>`	parties.user.claim	Grant the permission to the GriefPrevention claim that you are standing on	No	No
`home`	parties.user.home	Teleport to your party home	No	No
`home [party]`	parties.admin.home.others	Teleport to the party home	No	No
`protection [on/off]`	parties.user.protection	Toggle friendly fire protection	No	No
`sethome [remove]`	parties.user.sethome	Set/remove party home	No	No
`teleport`	parties.user.teleport	Teleport your party members to you	No	No

Command /p

/p is the command used to send a message to the party, if you want to use that command you must have the parties.user.sendmessage permission set.

Structure of the command: /p <message>