Bukkit

GroupDrops YAML configuration

config.yml

This will explain all the options in the config.yml file.

debug:

• events: Debug info during events (Default: false)
• config: Debug info from config (Default: false)

version: Current config/database version. Used for auto-updating mechanic, so don't edit this.

drops.yml

This explains the per block break item drop editor yaml file.

Each top level section identifier indicates for what block break to listen to and potentially modify.
Each key under that is the permission sub-node to give to players / groups to apply the drop rules.
Permission nodes are as follows: GroupDrops.group._
And simply fill in the blank with the given key for the section.

For each permission section, there are two options:

• clear : whether or not to include the orignial drop, if any. If true, the original drop will NOT be included. (Default: false)
• drops: This is is a list of items that should be dropped, along with a percentage chance of that item being dropped.

Here's a quick example and explaination:

'2':
  test:
    clear: false
    drops:
      '19': 100
      '14': 75
      '1': 150
  other:
    clear: true
    drops:
      '20': 40
35&15:
  test:
    clear: false
    drops:
      '278': 100
      35&2: 25
      35&3: 120
  other:
    clear: true
    drops:
      '20': 40

The first section has a top level key of "2". Thus, it will listen for whenever a grass block (block id 2) is broken and attempt to apply its drop rules depending on if the player has the permission nodes of the immediate subsections.

The next two sections, "test" and "other" are the permission sub-node sections. So, those with the GroupDrop.groups.test permission node will have the "test" drop rules apply to them. Same with the "other" section. And if a player has both or more, then all applicable drop rules will apply.

For the "test" section, the clear option is set to "false", so the original grass item drop will be included (aka, a dirt block will be dropped). However, with the "other" section, the clear option is set to "true", so the dirt block will not be included.

Lastly, the list of drops. The "test" section will drop the following:

• Sponge (19), with a 100% chance
• Gold ore (14), with a 75% chance
• Stone (1), that will always drop at least 1 and a 50% chance of dropping a second.

So, if you go over 100%, you are guaranteed that number / 100 and the remainder as a chance for the next. For example, if you put 830 as the percentage, you are guaranteed that 8 will drop, and a 30 percent for an extra to drop.

Lastly, if you want to use data values for an item, separate the item id from the data value with an ampersand: "&"
So, in the second item that we're listening for, black wool, we specify the section with "35&15", as 35 is for wool and 15 is the data value for black wool.
And as seen in the example, the same applies to drops that you want data values for.

The clear option does not have to be there. If missing, it will default to false.
If a player breaks a block that is not on the list, it will drop / act normally.
If a player breaks a block on the list, but has none of the sub-nodes in their permission set, it will drop / act normally as well.