HyperCurrencies

In this update, placeholders (for PlaceholderAPI) have been upgraded, adding new placeholders: · %hypercurrencies_balance_{currency}% - Balance of player. · %hypercurrencies_balance_{currency}_{player}% - Balance of other player. · %hypercurrencies_baltop_{player}_{currency}% - Balancetop placement of player. · %hypercurrencies_baltop_{uuid}_{currency}% - Balancetop placement of player (using UUID). · %hypercurrencies_baltop_{placement}_{currency}% - Name of player on balancetop placement.

What's new? · Added both danish and chinese language support · Fixed /baltop displaying null if there was no more players left to display · A help message when executing /pay · The ability to toggle paying for currencies, so you can chose whether or not you want to be able to get paid through /pay · Fixed bugs happening when paying a currency with the built-in vault provider · Fixed automatic table generation with the built-in SQL provider when setting balance · The built-in SQL provider now supports baltop · Added bStats tracking Improved discord You can now ask questions and showcase what you've made in the discord, so make sure to join! Javadoc available! If you're interested in developing with the HyperCurrencies API, check out the new javadoc! Ideas? I'm open for any ideas! If you have ideas, wanna add a language file or have found a bug/glitch, please open an issue at this page.

· /baltop now support pages 1-10 (top 1-100 players). · Added language support/message configuration (located in HyperCurrencies/lang/LANG_FILE.yml).

This update is a must have, so make sure to update! New in 1.3: · /bal · /baltop · /pay · Pay toggling and pay minimum · PlaceholderAPI integration

SQL Optimization and minor patches for better performance.

This is the stable release of 1.2, featuring full MySQL support. How to use MySQL for storing currency data First, set the currency's provider to hc-sql. Then fill in the details like this: Code (YAML): mysql-currency: provider : 'hc-sql' sql: url : 'MySQL_Database_URL' username : 'DB_Username' password : 'DB_Password'

New in this snapshot: · SQL Support for currencies. (supports min, max & starting balance) · Adding or removing balance close to a min or max balance cap is now possible. Note: This is a snapshot; not recommended for big servers or for storing important data. Click to expand...

· Fixed wrong names when changing others balance. · Better handling negative numbers.

· Supports all versions from 1.8 and above. · /hc info now shows if the plugin is up to date.

I found out that I'd forgot to change the main class in the plugin.yml file, resulting in a bunch of bugs occurring. I thought everything worked as it should, but apparently it didn't. Well, that made me spend 2 days on fixing bugs, which is probably good enough, because I can now with safely say that HyperCurrencies is 100% stable. Java notice: Currency#currencyExists is no longer depricated, due to a fix. Take a look at the full changelog here

In this patch, three things have been done. · Setting currency properties by command is now working. · CurrencyProvider#getProviderID is now abstract, which means that protected String providerID has now been removed. · The API-version has been changed to 1.8, instead of 1.19.

The first release contains bug fixes, API updates & a bunch of other cool stuff! You can now visit a fully covered java wiki, explaining how to use currencies in your plugin and adding providers to HyperCurrencies. Here's a total list of updates: - Manage currency properties in java and with a currency sub-command. - Update Checker. - Currencies uses java double (large decimal numbers) instead of java long (large non-decimal numbers) for managing player balance. - A sub-command for getting information about a currency.