GambleBarPro | Perfect Gambling Solution v2.2.0

• Fixed exploit issue with the plugin. Please update to this version ASAP.

• Previously, bar IDs were integers. This wasn't really a problem, but it didn't look clean. Now, bar ids can be a string instead. For example, the default bar was 0 but is now "mainBar".
  
  
• Minor changes to the config and messages files.

• There was a problem where users would get update alerts for the plugin even when there was no update. This problem will no longer happen.
• Background infrastructure changes to prepare for future updates.

With this update, it is now possible to configure a third possible outcome from a drink, a "super lucky win". (Note: If a super lucky win occurs, the normal rewards will not be given, only the super lucky rewards.)

Users should update their configuration if they want to use super lucky wins, but their plugin won't break if they don't. Below, see what a drink configuration looks like with super lucky wins. Notice the added lines, "superLuckyReward, superLuckyRewardCommands, superLuckyOdds".

YAML:

      10:
        name: "&c&lBeer"
        lore:
        - "&#00eff7&lClick to buy for a chance to win!"
        - "&#00bdf7Price: &f$%price%"
        - "&#00a1f7Reward: &f$%reward%"
        - "&#007cf7Odds of winning: &f%odds%%"
        potionColor: BLUE
        price: 500
        reward: 1000
        superLuckyReward: 2000
        odds: 50.00
        superLuckyOdds: 5.00
        rewardCommands:
        - "broadcast &c%player% &fhas won &c$%reward% &ffrom the GambleBar!"
        superLuckyRewardCommands:
        - "broadcast &c%player% &fgot very lucky and won &c$%reward% &ffrom the GambleBar!"

Some users reported server/main thread crashing due to update checking. The method for update checking has improved, added timeouts, and separated update checking from the main thread.

• There was a problem with versions too low to support RGB colors.

• You can now use RGB color codes for this plugin. To use, simply just write a "&", without the quotes, followed by the hex code, and the text.
• Refactored some other code that was just not done well the first time around.

• Slight performance optimization.
• Downgraded to Java 8. This shouldn't break anything for newer version users, but it should fix issues for people on 1.8.x versions.