config:{
  config-version: "4.0"
  #//Variables - {player} : the person who voted
  #//            {rewards} : The list of random rewards the player received

  #//Leaving this empty will disable messages from being shown publicly: Supports color and formatting codes
  broadcast-message: "&7{player} &evoted! Received 200 PokéCoins{rewards}&e!"

  #//-1 will have the system select a number of rewards between rewards-min and rewards-max;
  random-rewards-number: 1
  rewards-min:1
  rewards-max:1
  #// Under random You can set The tables you would like to use with weights in front for there to be a random chance of choosing from a table.
  #//In the case that there is only one table it will be chosen.
  vote-reward:{
    random:[
      "1", "TableCommon"
    ]
    set:["eco add {player} 200"]
  }
  //# Tables are groups of rewards which work as a weighted system. Below are two small examples, but they are very simple and not too elaborate.
  //# Much like the rewards above, the Tables are re-usable. As a matter of fact the Tables are needed by all "Random" rewards areas.
  //# They are pretty basic to use, Give it an id (no two id's should be the same) and then make a list with alternating weights and reward ids
  //# The weights are pretty simple to use, the higher number a reward has the likelier it is to be chosen. in the TableCommon below 'money1' has
  //#  25/125 chances to be chosen. You can use this to make common, rare , and super rare (etc...) tables which can be used together when you
  //# want more control over what is being given out.

  Tables {

    TableCommon: [
      "49", "bronzekey",
      "5", "silverkey",
      "45", "none",
      "1", "miragepoint"
    ]

    TableYearly: [
      "1", "miragecrystal"
    ]
    TableMonthly: [
      "1", "miragecrystal"
    ]
    TableWeekly:[
      "1", "miragecrystal"
    ]

  }


  //#Each Reward Requires an id "which is the descriptor / identifier such as tomahawk: in the tomahawk reward
  //# After each Reward requires a name key, and a reward key
  //# The value for name is just a text String (This can be used to Call it out in the broadcast built in)
  //#The value for the rewards string is a list of strings. Each String should be a full command and can include the standard variables
  //# Each new command string needs a comma before it. If your command requires quotations make sure to add escape characters
  //#-----i.e ----"hello how "are" you"---- is not valid the string should be escaped as follows
  //#         ----"hello how \"are\" you---- The backslash allows the " to be escaped to be ignored by the parser
  //#
  //# Every single Reward should have it's id be unique, i.e there should not be more than one tomahawk ect... The name of the items can
  //# be duplicated though, so a tomahawk1, and a tomahawk2, can have "Steel Tomahawk" as the name"

  Rewards {

    bronzekey: {
      name: " & &61 Bronze Key"
      rewards: [
        "crate key bronze {player}"
      ]
    }

    silverkey: {
      name: " & &71 Silver Key"
      rewards: [
        "crate key silver {player}"
      ]
    }

    none: {
      name: ""
      rewards: [
        ""
      ]

    }

    miragepoint: {
      name: "& &61 Mirage Point"
      rewards:[
        "enjin addpoints {player} 1"
      ]
    }

    miragecrystal: {
      name: "&61 &l&6Mirage &l&bCrystal"
      rewards:[
        "pb give {player} 1"
      ]
    }


  }

  #//This Message will Show above the Links.
  vote-sites-message: "&aVoting earns you a total of &e1000 PokeCoins &aa day, plus some lucky rewards such as &6crate keys&a! Click the link below to be directed to our voting page."

  #// Your website voting links, displayed by /vote, these support color formatting. Creates clickable links.
  #//seriousvotes.commands.vote
  vote-sites:[
    "&bhttp://www.miragecraft.xyz/vote"
  ]


  #// The Milestones Module Requires a Mysql System Setup
  database:{
    hostname: "censored-butit'scorrect"
    port: "3306"
    name: "censored-butit'scorrect"
    prefix: "SV_"
    username: "censored-butit'scorrect"
    password: "censored-butit'scorrect"
  }

  #// Currently we have monthly weekly and yearly, put what you need in the set rewards. these commands will be run
  #// When a player votes X amount of days in a row, 365,30, 7
  dailies: {
    enabled: true

    weekly: {
      message: "&7{player} &evoted 7 days in a row! Received &61 &l&6Mirage &l&bCrystal&e!"
      random:[
        "1", "TableWeekly"
      ]
      set:[]
    }
    monthly: {
      message: "&7{player} &evoted 30 days in a row! Received &61 &l&6Mirage &l&bCrystal&e!"
      random:[
        "1", "TableMonthly"
      ]
      set:[]
    }
    yearly: {
      message: "&7{player} &evoted 365 days in a row! That's 1 year! &9Are you really that dedicated!? Received a hug!"
      random:[
        "1", "TableYearly"
      ]
      set:[]
    }
  }


  milestones: {
    enabled: false
    #//place the number of votes you'd like to enable milestones for inside the brackets separated by commas.
    records-enabled:["100","1","37"]
    #// The setup for these is just the same as the normal voting. The tables must be defined in the table section in order for them to be used.
    records:{
      100:{
        message: "&4{player} has voted for a 100th time in a row!"
        random:[
          "27", "claimblocks"
        ]
        set: []
      }
      1:{
        random:[]
        set: ["one command","two command", "three command", "floor"]
      }

    }

  }
}