Added:
- Support to disable receiving gems in certain worlds (DropRates.yml)
Code:Disabled-Worlds: - 'world_nether'![]()
Added:
- Greatly optimized the plugin
- Added support for gems to be dropped from automated grinders SUPPORTS MOB STACKING (Image 1)
- Feature to remove the lore when purchasing an item from gem shop: *KeepLoreOnPurchase: true* (Image 2)
- Feature to keep the lore but remove the cost line on purchase: *RemoveCostFromLore: true* (Image 2)
Image 1: (DropRates.yml)
![]()
Image 2: (GemShop.yml)
![]()
Code:(Image 1) Automated-drop-rates: #These are the drop rates for when a mob is killed automatically. For example, if a mob dies from fall damage, a gem will be dropped IRON_GOLEM: drop-chance: 50 drop-amount: 1 support-stack-size: true #If set to true if you want the plugin to support stacked mobs (Preferably only used when the whole stack dies at once) death-reason: #For a list of death causes: https://hub.spigotmc.org/javadocs/bukkit/org/bukkit/event/entity/EntityDamageEvent.DamageCause.html - 'FALL' - 'LAVA' SKELETON: drop-chance: 50 drop-amount: 1 support-stack-size: true death-reason: - 'FALL' - 'LAVA' ZOMBIE: drop-chance: 50 drop-amount: 1 support-stack-size: true death-reason: - 'FALL' - 'LAVA' (Image 2) KeepLoreOnPurchase: true RemoveCostFromLore: true #This will remove the cost line from the lore on purchase
Added:
- Added new sounds for multiple events (In the config.yml, replace your current Sound section with the following)
Code:# This is where you can configure the sounds for certain events. Sounds: Redeem: 'ORB_PICKUP' #Leave empty if you don't want a sound to be played, for each specific event GemDropped: 'ORB_PICKUP' OpenShops: 'ORB_PICKUP' OpenUpgrades: 'ORB_PICKUP' Purchase: 'ORB_PICKUP' Upgrade: 'ORB_PICKUP'
Added:
- Added support for required permission to access a shop category
- Added new message to the config.yml (Add the following to your messages)
Code:shop-access-denied: '{prefix} &cYou do not have permission to access this shop. Requires: &e{permission}'
Note:
- To add the shop category permission feature, simply place the following line of code within each of your of your ShopMenu Categories
Simply put the shop category and the plugin will take care of the rest. For example, in the image below, the category is 'spawners'. The permission will automatically become 'elementgems.shops.spawners'Code:RequiredPermission: '(Shop Category)'
![]()
Added:
- Gem Shop? No. Gem Shop(s)
- ElementGems now supports UNLIMITED shop categories!
- Added a more efficient user friendly way of setting up the gem shops!
- Added option to keep or remove the lore of the item when you enable GiveDisplayedItem (GemShop)
- Added a new message to the config.yml file (Under the 'Messages' category, add the following)
Code:shop-not-valid: '{prefix} &cThis shop category does not exist: &e{category}'
Changes: (You will need to edit these within your files for these to take effect)
- Greatly optimized the plugin and reduced the file size
- Gem Shop has been completely revamped and contains a variety of awesome new features! (Requires you to reset your GemShop.yml file if you are updating from a previous version)
- "Auto-add" feature converted to "Auto-redeem" (DropRates.yml)
Added:
- Gems can now be received from fishing (Customizable)
- Added support for custom display names within messages
- Added an optional item to fill the Shop and Upgrade GUI's
(Add this message to your config.yml to use this feature)
![]()
Code:Use-Custom-Player-Display-Names: false
(Add this to your GemShop.yml and GemUpgrades.yml to use these features)
![]()
Code:FillerItem: Enabled: true Type: STAINED_GLASS_PANE Damage: 7 Amount: 1 Display-Name: '&f' Glow: true
Added:
- You are able to pay gems to other players now
- /Gems pay <Player> <Amount>
- New permission: elementgems.pay
- Added some new messages to make each general message, custom
Changes:
- Removed some unnecessary code to clean it up a bit
- Made a few positive changes to the config (Red=Removed, Yellow=Added)
![]()
Note:
- To make these changes take effect, simply add these new messages to your config
Code:withdraw-usage: '{prefix} &cIncorrect usage. &eTry /Gems withdraw <Amount>' add-usage: '{prefix} &cIncorrect usage. &eTry /Gems add <Player> <Amount>' remove-usage: '{prefix} &cIncorrect usage. &eTry /Gems remove <Player> <Amount>' set-usage: '{prefix} &cIncorrect usage. &eTry /Gems set <Player> <Amount>' give-usage: '{prefix} &cIncorrect usage. &eTry /Gems give <Player> <Amount>' pay-usage: '{prefix} &cIncorrect usage. &eTry /Gems pay <Player> <Amount>' not-enough-to-pay: '&cYou do not have enough to send this amount!' pay-to-sender: '{prefix} &7You have &asent &7a payment of &a{amount}x Gems &7to &a{player}''s &7account' pay-to-other: '{prefix} &7You have &areceived &7a payment of &a{amount}x Gems &7from &a{sender}' cannot-pay-to-self: '{prefix} &cYou cannot send gem payments to yourself' config-reload-error: '{prefix} &cAn error has occurred while trying to reload the config files.'
