Configurations

Here's a list of every configuration file, and explanations for non-obvious settings.

/config/lang.yml

# This file contains all the messages that are used in the plugin. This provides you with the ability to customize the entire plugin to your liking
bounty-set: "&8[&6&lBOUNTY&8] &f%player%'s bounty has been set to $%amount% &fby %target%"
bounty-claim: "&8[&6&lBOUNTY&8] &f%player%'s $%amount% &fbounty has been claimed by &6%target%"
invalid-player: "&C&l(!)&C Invalid player!"
no-bounty: "&C&l(!)&C This player does not have a bounty!"
force-remove-success: "&A&l(!)&A You have successfully forcefully removed %player%'s bounty!"
force-set-success: "&A&l(!)&A You have successfully forcefully set %player%'s bounty to %amount%!"
invalid-amount: "&C&l(!)&C Invalid amount!"
player-only: "&c&l(!)&c Only players can do this!"
console-no-bounty: "&C&l(!)&C The console cannot have a bounty!"
you-no-bounty: "&C&l(!)&C You do not have a bounty!"
bounty-view-you: "&A&l(!)&A You currently have a bounty of $%amount%"
bounty-view-others: "&A&l(!)&A %player% currently has a bounty of $%amount%"
maximum-bounty: "&C&l(!)&C This would exceed the maximum bounty for this player!"

/menus/bountymenu.yml

# This is the generic menu configuration file for every menu in every plugin of Avalon Development.
# The base of every menu is the same. It starts with a "menu" tag, then has a "name" and "size".
menu:
  # The name of the menu
  name: "&8Bounty Menu"
  # The size of the menu (make sure it's divisible by 9! Max is 54!)
  size: 45
  # This indicates which slots bounty heads should go in. You can add / remove however many you want, as long as it
  # fits in the menu. The plugin will automatically pick up on how many players you wish to view the top of
  bounty-slots:
    - 10
    - 11
    - 12
    - 13
    - 14
    - 15
    - 16
    - 21
    - 22
    - 23
  # This is the template for the heads that show up in the bounty menu for every player that's in the top.
  # %player% stands for the player's name
  # %amount% stands for the player's bounty (Formatted)
  bounty-slot-item-template:
    material: "PLAYER_HEAD"
    use-player-head: true
    name: "&e%player%"
    lore:
      - ""
      - "&a%amount%"
  # This is the generic item section, if you wish to add items, like information books, or whatever you want, you ARE able to.
  # Just follow the format that's shown for the Close Barrier, and you'll be able to add whatever you want.
  # Adding "type: "CLOSE"" to the item will result in the menu being closed when the item is pressed!
  # This gives you full control over where the close item should be, or if there should even be one. You can also add multiple!
  items:
    1:
      # The material of the item.
      # Visit (https://hub.spigotmc.org/javadocs/bukkit/org/bukkit/Material.html) to view a full list of all the materials
      material: "BARRIER"
      # The name of the item, supports & colors and hex colors, mixed and mushed together.
      name: "&#FF0000&LClose"
      # The description of the item that shows when you hover over it
      lore:
        - ""
        - "&fClick here to close this menu"
      # The inventory slot which this item should go to in the menu. Starts counting from 0. Max amount is whatever the size is configured to MINUS 1.
      # Any item placed above the max amount will result in errors!
      slot: 40
      # In our menu system, adding a type gives the item functionality. The bounty menu only has 1 functionality option and that's to close the menu.
      # If you wish to add multiple close buttons, just add another one of these items, and add this type: "CLOSE" to it, and it'll automatically
      # add the functionality to close the menu upon clicking.
      type: "CLOSE"

config.yml

# This allows you to choose where the data for bounties should be stored. The options right now are MongoDB, H2 or JSON.
# JSON will be less performant if you have a lot of players!
#
# MongoDB requires a MongoDB server to be setup!
# H2 (MySQL) doesn't require additional setup!
#
# Recommended default: MongoDB
# Default value: JSON
storage-option: "JSON"


# If you choose MongoDB, fill in these details as well, otherwise you can leave it
# Example connection string would be:

# mongodb://admin:[email protected]:27017/
# Make sure you change all the data to match your own. If you don't know what any of this means, you should probably be using JSON instead of MONGODB.
mongodb-connection-string:


# This setting determines what the minimum bounty is. I highly recommend you put this value above 0, just to prevent any issues with negative balances.
#
# Recommended value: 1
minimum-bounty-amount: 1


# This setting determines what the maximum bounty is.
maximum-bounty-amount: 10000000


# This setting determines whether the plugin uses the menu to display the top bounties, or display it in text
# The menus and text are configurable themselves as well. The menu can be changed in the "bountymenu.yml" file and the text format can be changed down below
#
# Recommended value: true
use-bounty-menu: true

# In case you have "use-bounty-menu" set to false, this is what "/bounty top" will show. If "use-bounty-menu" is set to true, you can ignore this!

# This is the header of the /bounty top message.
bounty-top-header: "&6&lBOUNTY TOP"

# This is how many entries should be displayed
bounty-top-amount: 10

# This is the format for every player in the top list.
# %player% translates to the players username
# %amount% translates to the amount of the bounty (formatted)
bounty-top-text-format: "&f- &6%player%: &a$%amount%"


# Permissions:
# "avalonbounty.bounty.forceremove": This permission indicates whether /bounty forceremove is accessible
# "avalonbounty.bounty.forceset": This permission indicates whether /bounty forceset is accessible
# "avalonbounty.bounty.menu": This permission indicates whether /bounty forceset is accessible
# "avalonbounty.bounty.set": This permission indicates whether /bounty set is accessible
# "avalonbounty.bounty.top": This permission indicates whether /bounty top is accessible
# "avalonbounty.bounty.view": This permission indicates whether /bounty view is accessible