Sueta

Additions | Free version | Menus, items, commands & more | 1

2.9.0

The all in one plugin with custom commands, menus, items, scoreboards, tablists, actions and more!

·Plugin

THIS VERSION IS DISCONTINUED!
We are no longer updating the free version of Additions.
For an updated version, with more features, go to the AdditionsPlus page .

  • Custom Commands
  • Custom Menus
    • Custom menu title
    • Placeholders in menu title [PREMIUM]
    • Left-click actions
    • Right-click actions
    • Custom size
    • Custom open permission (message)
    • Custom open cooldown
    • Open actions [PREMIUM]
    • Close actions [PREMIUM]
    • All items are configurable
    • Supports custom additions items using ci-ITEMNAME
    • Supports HeadDatabase/player heads
    • Enchantments
    • CUSTOM MENU GENERATOR [ONLINE]
  • Scoreboards
    • Per World
    • Togglable per player
    • Anti-Flicker [PREMIUM]
  • Create custom tab lists
    • Per World
  • Custom Player Names In Tab [PREMIUM]
    • Animated
    • Unlimited groups
    • Orders
    • Placeholder support
  • Create custom items
    • Cooldowns for items
    • Left-click actions [PREMIUM]
    • Right-click actions [PREMIUM]
    • Non-left-right-click actions (general clicking)
    • Everything of an item is configurable
    • Supports HeadDatabase/player heads
    • Enchantments
  • Create custom books [PREMIUM]
    • Book title
    • Book item name
    • Book item lore
    • Custom author
    • Custom generation (original, tattered, copy_of_copy, copy_of_original)
    • Inventory Slot (for giving the book)
    • Unlimited Pages
  • Interval actions
    • Random interval
    • Editable interval (in ticks)
    • Unlimited interval actions
  • Event Actions
    • 27 11 custom events [PREMIUM]
    • Perform actions when an event is being fired
    • Custom join message [PREMIUM]
    • Custom leave message [PREMIUM]
  • Color Codes On Signs (&)
  • Color Codes In Anvils (&)
  • Plugin hooks [PREMIUM]
    • PlaceholderAPI support
    • MVdWPlaceholderAPI support
    • Vault support
    • ProtocolLib support
    • HeadDatabase support
  • 49 18 actions [PREMIUM]
  • 1.8x - 1.14x support [PREMIUM]
  • 13 11 Built-in Placeholders [PREMIUM]
  • Almost 100% customizable!
  • Frequently updated No more updates [PREMIUM]
  • 24/7 and fast support via Discord

If your chat gets spammed by messages saying to vote 5-stars for this review and to not forget to vote for the server, please go to the intervalactions.yml file.
You can disable/change the actions there.

We get a lot of people issuing us about getting spammed by this plugin and then leave a 1-star / bad review just based on that.

If you experience any bug, please issue us FIRST before leaving a review!*

* We will still provide full support for the free version, but we will not add any new things, or release any new versions as we will ONLY update Additions+ (paid version) from now on.



It's not a complicated system. You simply put the event name (see event list) in the file, add a : behind it, then press enter, add 2 spaces, type actions: , press enter, and type right under actions: a line (-) and put the action in it. For more actions, just add more lines.

join  :  
  actions   : 
  - 'action1' 
  - 'action2'  
leave  :  
  actions   : 
  - 'action1' 
  - 'action2'  
drop  :  
  actions   : 
  - 'action1' 
  - 'action2'  
fishing  :  
  actions   : 
  - 'action1' 
  - 'action2'  
kill  :  
  actions   : 
  - 'action1' 
  - 'action2'  
dead  :  
  actions   : 
  - 'action1' 
  - 'action2'  
shear  :  
  actions   : 
  - 'action1' 
  - 'action2'  
itembreak  :  
  actions   : 
  - 'action1' 
  - 'action2'  
consume  :  
  actions   : 
  - 'action1' 
  - 'action2'  
entitykill  :  
  actions   : 
  - 'action1' 
  - 'action2'

If you don't want action to be performed for that event, just remove the event type (see underlined words in the event list) or set the actions of that event to []. An example is then:

join  :  
  actions   :   [   ]

Version 2.8.0 also adds the possibility to set the death, join and leave message of players. If you want to remove it, just set it to ''.
The right way to use them are:

join  :  
  joinMessage   :  '&a&l  %player% joined the server'   
  actions   :   [   ]   
leave  :  
  leaveMessage   :  '&c&l  %player% left the server'   
  actions   :   [   ]   
dead  :  
  deathMessage   :  '&c  %player% is soon to be hosting his own funeral as a ghost. Please be there, he''d like that. &lR.I.P'   
  actions   :   [   ]

Creating custom commands isn't hard with this easy system. It practically works the same as the events, but you do it in the commands.yml file, and instead of the event name, you type the command.
All actions can be used on either the events or the commands.

help   :   # would be '/help' ingame   
  actions   : 
  - '  [  msg  ]  &7  ---  - &bHelp Menu &7  ---  -' 
  - '  [  msg  ]  &b/helpop &7Get help from an operator' 
  - '  [  msg  ]  &r' 
  - '  [  msg  ]  &fpage 1/2'  
help 1   :   # would be '/help 1' ingame   
  actions   : 
  - '  [  msg  ]  &7  ---  - &bHelp Menu &7  ---  -' 
  - '  [  msg  ]  &b/helpop &7Get help from an operator' 
  - '  [  msg  ]  &b/help 2 &7Next page of the help menu 
  - '  [  msg  ]  &r' 
  - '  [  msg  ]  &fpage 1/2'  
help 2   :   # would be '/help 3' ingame   
  actions   : 
  - '  [  msg  ]  &7  ---  - &bHelp Menu &7  ---  -' 
  - '  [  msg  ]  &b/server &7Select a server' 
  - '  [  msg  ]  &b/help 1 &7Previous page of the help menu' 
  - '  [  msg  ]  &r' 
  - '  [  msg  ]  &fpage 2/2'

The commands can also have permissions. If you don't specify the permission, everyone will be able to perform the command. If you do specify the permission, the player needs it to perform it.
If the player doesn't have the permission, the noPermission message will be sent to the player. This can be specified per command. If you don't specify the noPermission message, the default message will be sent: "&cYou don't have permission to do this".
The correct usage of permissions and the noPermission message is:

rankup 3  :  
  permission   :  yourperm.rankup.2  
  noPermission   :  '&cYou must be at least rank 2 to rankup to rank 3. You can buy ranks in our store.'  
  actions   : 
  - '  [  title  ]  &a&lRANKED UP\n&7You are now level 3!' 
  - '  [  msg  ]  &aCongratulations! You are now rank 3.' 
  - '  [  console  ]  pex user  %player% add yourperm.rankup.2'

Version 2.6.0 also offers the usage of cooldowns in commands. You can add a cooldown time to the command. You can also add a cooldownMessage to the command. This message will be sent to the player when the command is on cooldown for that player. Use %time% in the cooldownMessage for the remaining time.
The correct usage of these features is:

mycommand  :  
  cooldown   :  1200  # 1200/20 = 60 seconds ( 1 minute )   
  cooldownMessage   :  '&cYou can only use this command once per minute. You have to wait for another  %time%'   
  actions   : 
  - '  [  msg  ]  &aThis is a command with a cooldown'
Result

When you don't have permission:

When you do have permission:

And also the command in the console is being performed. The permission has been successfully added to my permission list.

Creating custom menus isn't hard to do. The plugin will automatically generate a 'menus' folder when enabling it. In that folder, you create your custom menus. Each menu is separated and has its own YAML file. The name of the menu is the file name without .yml.

You simply create a YML file with as name the menu name. You only use this name to open the menu in the /additions command or [menu] actions.
Example: example.yml . You open this menu with /additions openmenu example .

In version 2.8.0, the whole menu system has been recoded to add more customizability for the items and its display. If you are using 2.7.0 or lower (which I don't recommend), read the old tutorial below.

You can set everything of an item in the new version. You can add enchantments, add item flags to hide the enchants, and all other things. Note that all messages support color codes and Placeholders.
Below are the non-item options you can set for the menu:

title :
Description: The title of the menu
Type: String
Required: true
command :
Description: The command to open the menu
Type: String
Required: true
size :
Description: Size of the menu. Must be either, 9,18, 27, 36, 45 or 54.
Type: Integer
Required: true
permission :
Description: The permissions needed to open the menu
Type: String
noPermission :
Description: The message that will be sent when a player doesn't have the specified permission to open the menu
Type: String
cooldown :
Description: The cooldown amount in ticks before the player can open the menu again. (1 second = 20 ticks)
Type: Long
cooldownMessage :
Description: The message that will be sent when a player is on cooldown for that menu. Use %time% for the remaining time
Type: String
openActions :
Description: Actions that will be performed when the player opens the menu
Type: String List
closeActions
Description: Actions that will be performed once the player closes the menu
Type: String List
If you set all of that, your file will look something like this:

Example Menu
title   :  '&b&lExample Menu  (   %player%)'   
size   :  9  
commands   :  examplemenu 
 # optional   
permission   :  myperm.examplemenu  
noPermission   :  '&cWell.. This is too exclusive for your eyes :  )  '  
cooldown   :  200  # 200 ticks = 10 seconds (200/20=10)   
cooldownMessage   :  '&cYou can only open this menu once per 10 seconds. You have to wait for another  %time%'   
openActions   : 
 - '  [  msg  ]  &aYou opened the menu :  )  '  
closeActions   : 
 - '  [  msg  ]  &cYou closed the menu :  (  '

Now you're ready to add the contents to the menu. You add all items under the content section. Then add the slot number (starting at 1, not 0) under it between brackets: '1'. Like this:

content: 
  '1': 
  '2':

Then you set the item information. Below is a list of all options you can add to the item to customize it, literally everything is possible.
material :
Description: The material type of the item. If you have the HeadDatabase plugin, you can set this item to a custom head using "hdb-<headID>". Replace <headID> with the ID of the head. You can also set a player head using "head-<player>". Replace <player> with the player's name (this also supports the placeholder %player%)
Type: Material Type
Required: True
data :
Description: The data of the item (for 1.8-1.12 only)
Type: Byte (Integer)
displayName :
Description: The display name (title) of the item
Type: String
Required: True
amount :
Description: The amount of the item
Type: Integer
durability :
Description: The durability of the item
Type: Short (Integer)
lore :
Description: The lore of the item
Type: String List
itemFlags :
Description: The item flags of the item. Click here for a list of item flags
Type: ItemFlag List
enchantments :
Description: The enchantments that should be applied to the item. To set the enchantment level use the format ENCHANTMENT:LEVEL (DURABILITY:3). Click here for a list of 1.12.2 enchantments.
Type: Enchantment List
unbreakable :
Description: Whether the item should be unbreakable or not
Type: Boolean
left_click_commands :
Description: A list of actions that will be performed when you left-click the item
Type: String List
right_click_commands :
Description: A list of actions that will be performed when you right-click the item
Type: String List
If you did all that, the file will look something like:

Example Menu
title   :  '&b&lExample Menu  (   %player%)'   
size   :  9  
commands   :  examplemenu 
 # optional   
permission   :  myperm.examplemenu  
noPermission   :  '&cWell.. This is too exclusive for your eyes :  )  '  
cooldown   :  200  # 200 ticks = 10 seconds (200/20=10)   
cooldownMessage   :  '&cYou can only open this menu once per 10 seconds. You have to wait for another  %time%'   
openActions   : 
 - '  [  msg  ]  &aYou opened the menu :  )  '  
closeActions   : 
 - '  [  msg  ]  &cYou closed the menu :  (  ' 
 # menu items   
content  :  
  '1'   :   # slot 1   
    material   :  STONE  
    data   :  0  
    amount   :  2  
    displayName   :  '&7Some random &lStone'  
    lore   : 
    - '' 
    - '&7This stone could be yours, &b  %player%'  
    - '&7This another lore item :  )  '  
    enchantments   : 
    - DURABILITY:3 
    - FIRE_ASPECT:10 
    - MENDING  
    itemFlags   : 
    - HIDE_ATTRIBUTES 
    - HIDE_DESTROYS 
    - HIDE_ENCHANTS 
    - HIDE_PLACED_ON 
    - HIDE_POTION_EFFECTS 
    - HIDE_UNBREAKABLE  
    unbreakable   :  true  
    left_click_actions   : 
    - '  [  msg  ]  &7You left-clicked a random stone'  
    right_click_actions   : 
    - '  [  msg  ]  &7You right-clicked a random stone'  
  '2'  :  
    material   :  head-  %player%   
    amount   :  1  
    displayName   :  '&b&lYour head'  
    lore   : 
    - '' 
    - '&7This is your own head' 
    - '&7Don''t worry. It is not chopped off'  
    itemFlags   : 
    - HIDE_ATTRIBUTES 
    - HIDE_DESTROYS 
    - HIDE_ENCHANTS 
    - HIDE_PLACED_ON 
    - HIDE_POTION_EFFECTS 
    - HIDE_UNBREAKABLE

Oof. You now know how to create a menu :)

Similar projects

Plugin →