The menu title that is shown at the top of the GUI. You can use color and formatting codes here, and PlaceholderAPI placeholders.

The command used to open the GUI menu. It can only be a single word.

To disable the open command, simply delete the line of this option.

Sets requirements a player should have to open the GUI menu. Check the Requirements page for more info.

Runs the command(s) you set when the player opens the menu.

Runs the command(s) you set when the player close the menu by clicking an item that have the close action ([close]).

Allows you to define a different type of Inventory.

Size option only works for CHEST inventory types. Even for that it is optional and will default to 54.

Registers the open command with the server.

Must be manually added to the menu.

TEXT The argument name (Should be unique).

Gives you the ability to set arguments after the open command, and use them inside the menu by adding the argument placeholder (the argument name inside curly braces {TEXT}).
You can have multiple arguments, and they will be set in the same order in the open command.

{first} returns FirstArg
{second} returns SecondArg
{last} returns And the rest

It's highly recommended to add the Args Usage Message option.
Requires Register Command to be true.

Sets the usage message for the menu. If the player didn't set the required arguments. It will be sent to the player if he didn't set the arguments. You can use color and formatting codes here. Requires Arguments to be defined.

This is for any items that use the update: option (Check it here).
The number defines the delay (in seconds) between each refresh of the placeholders in an item's lore/display name.
Note: This refreshes/updates the placeholders only.

This line should be left as is. It is merely telling the plugin you are about to begin defining items.
Check the Item page for more information.

Note:
Each item will have a name, in this example our item is called ItemName. This name should be unique, so there won't be two or more items with the same name.

Sets the material of the item in the menu.[/code]
为菜单内图标设置显示物品。

[quote]For version 1.12.2 or older:
Check Data option to specify the data of the item (the number after the colon :). e.g. Lime Wool would be

For version 1.12.2 or older:
This option will specify the data value (the number after the colon :) of the item or the item's durability (depends on the Material option).

Sets the item's amount in the menu.

Sets the item's amount in the menu using a placeholder.

Allows you to add custom nbt tags to your items like model data so you can display custom models provided by your server resource pack.

The nbt tags options support PlaceholderAPI placeholders now!

Allows you to create your custom banner (Used if the material is a banner).

Allows you to set item flags.

Allows you to set effects (Used if the material is a potion, splash_potion and tipped arrows).

For potion_effects to work on potions and tipped arrows you also need to give it an RGB value.

For RGB option to work on potions and tipped arrows you also need to give it at least one potion_effect.

Sets the item's display name. You can use placeholders and color/format codes

Sets the item's lore (the text shown under the item's name). You can use placeholders and color/format codes and the new line character (\n) in this option.

Sets in which slot the item should be inside the menu.

Slots start at 0.
Multiple items can be in the same slot, but you'll have to use view requirement and priority options to work properly.

Sets the item priority. It's used if you want different items in the same slot (by using the view requirement option).
The item that has the highest priority will be checked first if the player has the required view requirement. It will display the item if they have the requirements and if not, it will check the next item and so on.

The highest priority is 0.
The lowest priority is 2147483647.

Sets the requirements the player should have to see the item. (Check priority option for setting up multiple items in the same slot).
Check the Requirements page for more info about this option's value and how to use it.

If set to true, it will update the placeholders in the item's display name and lore only.
Check the update interval GUI option to set the update speed.

Enchants the item with the specified enchantments. (Check the hide enchantments option to hide the enchantments)

Some items cannot have the enchanting glow effect

If set to true, it will hide the enchantments you set for the item using the enchantments option from the item's tooltip (lore).
Used to add the enchanting glow effect to the item without showing the enchantments text.

If set to true, it will hide the vanilla attributes of an item/armor (e.g. 7 Attack Damage).

If set to true, it will hide the potion's effect text beneath the item name.

If set to true, it will hide the unbreakable tag if the "unbreakable:" option is enabled.

If set to true, it will show the item to be at full durability.

Sets the actions/commands that should be executed once the player clicks the item. they get executed in order from top to bottom.
Check this for all action types and action tags.

Middle clicking was removed by Mojang in 1.18 and newer!

Sets the requirements the player should have to click the item (Check the Requirements page for more info about the EXPRESSION value).
Deny commands (optional) are the actions that are going to be executed if the player doesn't have the required requirements. But if (s)he does, it will execute the actions specified in the click commands option.

You can have deny commands per requirement. Check this page for more information.

Check this for all action types and action tags.

IMPORTANT!
left/right/shift_left/shift_right/middle click requirements won't work unless you also have their respective click commands. This is true even if you have set the success_commands option

Requirements allow you to restrict certain actions or even an entire menu and only allow certain players to see and/or use the menu.

When inverting requirements, make sure you put the type in quotation marks. This is because "!" is a special symbol in YAML so it will break the syntax.
ex: type: "!has permission"

Checks if the player has the specified permission.

To invert the requirement (Check if the player doesn't have the permission) you can simply add the exclamation mark before the type name (like this type: "!has permission").

Checks if the player has the specified amount of money (Vault is required).

To invert the requirement (Check if the player doesn't have the amount of money) you can simply add the exclamation mark before the type name (like this type: "!has money").

To use a placeholder as a value for the amount, replace the amount: field with placeholder:.

Checks if the player has the specified item in the inventory.

To invert the requirement (Check if the player doesn't have the item) you can simply add the exclamation mark before the type name (like this type: "!has item").

Meta uses Persistent Data Containers which means this feature will only work on servers that are 1.14 or newer!

Checks if the player has the specified meta.

If the meta_type is a number format (DOUBLE, LONG, INTEGER) it will check if the player's meta value is greater than or equal to the value
To invert the requirement (Check if the input doesn't match the output) you can simply add the exclamation mark before the type name (like this type: "!has meta").

Checks if the player has the exp level or points.

If the level option does not exist, it will check for exp points by default
To invert the requirement (Check if the input doesn't match the output) you can simply add the exclamation mark before the type name (like this type: "!has exp").

Checks if the player is within distance of location.

To invert the requirement (Check if the input doesn't match the output) you can simply add the exclamation mark before the type name (like this type: "!is near").

Evaluates a JavaScript expression that must return true or false.

Checks if input: matches output: (Case sensitive).

To invert the requirement (Check if the input doesn't match the output) you can simply add the exclamation mark before the type name (like this type: "!string equals").

Checks if input: matches output: (Case insensitive).

To invert the requirement (Check if the input doesn't match the output) you can simply add the exclamation mark before the type name (like this type: "!string equals ignorecase").

Checks if input: contains output: (Case sensitive).

To invert the requirement (Check if the input doesn't contain the output) you can simply add the exclamation mark before the type name (like this type: "!string contains").

Checks if input: contains the regular expression in regex:.
Visit this site to create regular expressions easily.

To invert the requirement (Check if the input doesn't contain the regular expression) you can simply add the exclamation mark before the type name (like this type: "!regex matches").

A simple example to show you how you can make a Kits menu that displays 3 different items for each kit, when the kit is available to claim, when it's on cooldown and when it's unavailable (Locked).

To make this work fine you have to download Essentials and download the Essentials expansion using:
/papi ecloud download Essentials
/papi reload

A simple example to show you how you can make a Mines menu that displays 3 items for each mine, when the mine is unlocked, when it's the current mine and when it's locked.

To make this work fine you have to download EzRanksPro and download Player and EzRanksPro expansions using:
/papi ecloud download Player
/papi ecloud download EzRanksPro
/papi reload

A simple example to show you how you can make a Ranks menu that displays 2 items for each rank, when the rank is not purchased and when the rank or a higher rank is purchased.

To make this work fine you have to download LuckPerms and download Player and LuckPerms expansions using:
/papi ecloud download Player
/papi ecloud download LuckPerms
/papi reload

A simple example to show you how you can make a Server Selector menu that displays 2 different items for each server, when the server is online and when it's offline.

To make this work fine you have to download Pinger and (optional) Server expansions using:
/papi ecloud download Pinger
/papi ecloud download Server
/papi reload

In this example, we have 2 different servers on one BungeeCord: vanilla and games. We are on the server games in this example.

If we want the player to connect to the vanilla server, we need to setup the right functions in the left_click_commands: **section
In our example, we will first close the menu with [close], send a message to the player with [message] and finally connect him to the server with [connect].

To show, how many players are on the server vanilla, we will use the placeholder %pinger_players_<ip>:<port>%
Please keep in mind, that Pinger placeholders have their own update interval, to change it, go to the PlaceholderAPI config file and change the check_interval: (default is 30 seconds).
But what if the server is currently offline?
In this case, we can use a second item with a lower priority, that will be displayed, if the view_requirement: of the first item isn't true.
So now we can show a different item, if the server is offline. But keep in mind that the items don't update automatically, if the view requirement has changed (from Offline to Online). We can update the menu, by letting the player execute [refresh] if he clicks on the item.

The second item is easier. Because we are already connected, so we just need to send a message. And we can show the amount of players on the server with the %server_online% placeholder.

A simple example to show you how you can make a Store/Shop menu that you can buy/sell items from using various economic systems.

To make this work fine you have to download the Player and CheckItem expansions and the expansion of the economic system that you'll use using:
/papi ecloud download Player
/papi ecloud download CheckItem
/papi ecloud download Vault
/papi ecloud download TokenEnchant
/papi ecloud download PlayerPoints
/papi reload
****Vault****
****Token Enchant****
****Player Points****
​****Player XP****

A simple example to show you how meta works.

EzRanksPro allows users to rank-up the easy way, with a very flexible and extremely customizable rank-up system built for server owners by server owners. The config requires minimal effort an is a quick and simple setup.

To give a player or group access to a rankup, they need access to the permission node associated with it! Without it EZRanksPro does not know what rankup they have access to. If you create a rankup for rank A to B, you will need to give the A rank the permission node: ezranks.rank.A. This will tell EZRanksPro that players in A should have the rankup associated with A. Players can have access to multiple ezranks.rank. permission nodes, the highest order rankup will always be applied for the player.
For a player to be considered the last rank, they need to have the permission node: ezranks.lastrank This tells EZRanksPro that the player is at the last rank and has no more rankups available.
Inside of your rankups.yml you will see a section with each rankup named rankup_actions. In this section you may list many actions that the plugin will perform when a player ranks up. The format for actions are:
-'<action> <arguments>'
You must include required arguments :
<required>, (optional)
You may delay any rankup action by ending the action String with  example:
-'[consolecommand] eco give %player% 100 '

[consolecommand]  - perform a console command
[playercommand]  - make the player perform a command
[message]  - send the player a message
[broadcast]  - send the server a message
[jsonmessage]  - send the player a json message
[jsonbroadcast]  - send the server a json message
[actionbarmessage]  - send the player an actionbar message
[actionbarbroadcast]  - send the server an actionbar message
[addgroup]  (world) - add the player to a permissions group
[removegroup]  (world) - remove the player from a permissions group
[addpermission]  (world) - add a permission node to the player
[removepermission]  (world) - remove a permission node from a player
[setprefix]  - set the players prefix
[setsuffix]  - set the players suffix
[effect]  - play an effect at the players location
[sound]    - play a sound at the players location

Placeholders can be used in your rankup actions and messages. Placeholders list:
%player% - players name
%displayname% - players displayname
%world% - players current world
%rank% - players current rank
%rankup% - players next rank (if they have one)
%cost% - cost to rankup
%cost_formatted% - formatted cost to rankup
%balance% - players balance
%balance_formatted% - players formatted balance
%difference% - amount still needed
%difference_formatted% - formatted amount still needed
%progress% - rounded % of rankup cost obtained
%progressexact% - exact % of rankup cost obtained
%rankprefix% - players current rank prefix defined in this file
%rankupprefix% - players next rank prefix defined in this file
%lastrank% - last rank available
%lastrankprefix% - last rank available prefix
%rankup_cost_% - show the cost for a specific rank
%rankup_cost_formatted_% - show the formatted cost for a specific rank
%rankup_is_completed_% - show if a player has completed the specified rank

Keep it going! EZPrestige gives you the ability to add prestige levels to your server's rank up system, where players can start over as a prestige player when they reach a certain rank.
EzPrestige gives players the ability to prestige using /prestige. Features plenty of configurable requirements for prestiging, as well as placeholders to display the prestige info such as prefix, next prestige and much more.

Ability to create unlimited prestige levels!
Highly customizable.
Built-in GUI to display all prestige levels.
An option to confirm before upgrading to the next prestige level.
Supports any chat plugin to display the prestige level!
Supports any rank up system/plugin.
Ability for players to prestige
Highly customizable.
Placeholders to display prestige info
Compatible with rankup plugins (EzRanksPro, etc)
Permission based

EZPrestige requires any rank up system/plugin to work properly and fulfill its purpose.

To display the prestige tag within your deluxechat chat format, use the placeholder provided by the ezprestige expansion
download the expansion using /papi ecloud download ezprestige (make sure to reload PlaceholderAPI afterwards)
set the prestige placeholder %ezprestige_prestige% within your format
Other placeholders (https://api.extendedclip.com/expansions/ezprestige/)
Put the EZPrestige jar file you downloaded in your plugins folder.
Download a rank up plugin (such as EZRanksPro) or set up your own.
Restart the server.
Modify the config.yml file that was generated to fit your server's layout (File path: /plugins/EZPrestige/).
Create your prestige levels in prestiges.yml file. Don't forget to give the players the prestige permission (ezprestige.prestige.<Prestige Number>) in the prestige_commands section!
Reload EZPrestige /prestige reload.
Check the Commands & Permissions page, to give players access to the commands you want them to use.
And you're done!

If you are using Essentials Chat you will need to do the following
Open the Essentials config and find the EssentialsChat section
Place the prestige placeholder for essentials chat {prestige} inside the format

InventoryFull is a very small plugin that alerts players when they don't have inventory space!
Simply enable any of the following ways to alert players in the config file and use /invfull reload. After the alert type is enabled, when players get a full inventiry they will be alerted!

5 Ways to send the full inventory alert.
Highly customizable.
Play a sound when the alert is sent.

Types of alerts:
ChatMessage - send an inventory full message through chat!
Actionbar (Requires ActionAnnouncer) - send an inventory full message through the actionbar!
Title and subtitle (Requires TitleManager) - send an inventory full message through the Title and subtitle!
Holograms (Requires HolographicDisplays) - send an inventory full message with a hologram!
Sound - play a sound to a player when they have a full inventory!

There is an API that will allow you to listen to a special event that is fired when a player has a full inventory and breaks a block that won't fit!
Here is an example:

MessageAnnouncer allow server owners to create custom message using JSON which can be sent at a set interval.

Ability to use JSON
Ability to use regular text using the [text] tag
Ability to send the messages in a random order
Ability to set a custom interval
Ability to play a sound when a message is sent
You can create unlimited announcements
Highly customizable.
PlaceholderAPI support

MineCrates allows server owners to define areas where crates will spawn. Blocks that are mined in the area contribute to the reward counters, once reached the last block the player broke will switch into a reward crate. Areas, rewards and tiers can all be edited within the config.

Ability to define "crate areas"
You can define unlimited "areas" and even "reward tiers"
MineCrates supports: WorldGuard, WorldEdit, PrisonMines & MineResetLite
Highly customizable.
Rewards can be items or commands
Highly customizable.
PlaceholderAPI support
Permission based

NoFlyZone is a plugin that prevents players from flying in specific WorldGuard regions if they do not have permission.

All you need to do is add the region name to the NoFlyZone config list either by command or by editing the config manually and using /nfz reload. Anyone without the permission noflyzone.bypass will be stopped from flying as soon as they enter the region.
You NEED WorldGuard 6.x + WorldEdit for this plugin to work!

This plugin is open source. You can get the source code from here:
https://github.com/extendedclip/NoFlyZone

Ever have that urge to punch a cow, but everytime you do its just so unsatisfying? Well I've got the plugin for you, this plugin allows cows to float up in into the sky after being punched by a player... and then come crashing down to the ground ultimately coming their end.

This is a fun little plugin that allows fireworks to come shooting out of any configured block clicked by a player. It also includes a configurable cooldown per block to stop pesky spammers.

FishSlapper allows any player with the correct permission to use raw fish as an tool to slap people around the server in a chaotic fashion. It's quite a simple concept, those with the permission allowing them have the permission to slap can slap anyone with the permission that allows them to be slapped. Once contact has been made between the fish and the player they are then sent flying away! (Pufferfish will allow for maximum slapping)

Due to new fish added to the game,  v1.11.0+ You need to use a Pufferfish for the effect to work!

Just a simple plugin to send a raw message (No Prefix) from in game or console with PlaceholderApi placeholders to either a single player or broadcast it to the whole server.

<centered> - If set to true RawMsg will attempt to center the message when sending it to the player.
You can use <n> in the message to add a new line. To add a blank line just use two!

For 1.16+ Users:
#<??????> for custom hex colours
Replace ?'s with hex value eg #<ffffff>

Let your players spit like Llamas using the /spit command, this will fire spit from the player in the direction they are looking in.

Set a timed message to show up in your server list MOTD, broadcast events in your message, Thank voters in your message, Congratulate rankups in your message and much more.

Using ChatReaction you can launch commands on correct guesses, use this to show off who won the reaction win and tell others to join in on the fun.

Using EzRanksPro on a rankup you can run the TempMotd command in the console and show off who ranked up and what they ranked up to!

More examples include:
- Thank players for donating to the server.
- Thank players for voting for the server.
- Broadcast Drop Parties or other events.
- Congratulate on level ups.
And many more.

Guilds were created to offer an RPG-type system to servers. It was inspired by players like you who enjoy creating a fun, exciting, and adventurous environment for your server. Guilds allow players to join interactive groups of other players, make their own communities on your server, and have a general fun time!

Per-Guild Hierarchy (Roles)
Tiers (Includes perks of your choosing)
Claims (via WorldGuard)
Banks
Vaults (As many as your choose!)
Buffs
Per-Guild Chat
Wars (via Arenas that you make)
Multilingual
Tons of GUIs!
JSON + MySQL + SQLite support!

In Guilds, we always try to support as many languages as we can in order to support more people! The plugin currently supports 20 languages, but not all of them are always up-to-date on the translations. If you speak a language fluently other than English and are interested in translating, please join our discord and let us know so that we can give you information on how to do that!

When the plugin starts up for the first time, the following files will be generated:
​​buff.yml
config.yml
roles.yml
tiers.yml
The configuration for the plugin is split up into multiple files due to how flexible the plugin is and how much custom data you can add to it.