Do not use this version. Use 2.0.0RC2.
Remember to always backup existing configs before updating! This is VERY important for this release!
File Structure Modified/Updated
- Multi-Crate config support, you can now seperate each crate in seperate files
- Crate/Key config(s) have been moved to the /config/huskycrates/crates/ directory
- Database/Generated Items config(s) have been moved to the /config/huskycrates/storage/ directory
- Migration code in place to move existing files into new locations/naming structure
New Features
- New Command /hc open [nokey] <crate> [player/@a] - allows opening of a crate from a remote location
- Permission : huskycrates.open.base
# Targeting player will instead attempt to open the crate for them
- Permission : huskycrates.open.others
# Targeting @a will instead attempt to open the crate for all players
- Permission : huskycrates.open.others.all
# Adding the optional argument of "nokey" will not perform a key check when opening the crate
- Permission : huskycrates.open.keyless
- New Command /hc generatecrate <name> <inventory/item> - generates a crate configuration based on the item(s) in your inventory or hand.
- Permission : huskycrates.admin
NOTE : This comes with preconfigured values that should be tweaked/modified for the crate to be complete however it should generated a base for you to work from!
- New Command /hc generateinventory - inventory based command that functions exactly the same as the /hc generateitem command
- Permission : huskycrates.admin
# Generates to config/huskycrates/storage/generatedinventories.conf
- New Duplication Log config/huskycrates/storage/dupealert.log
# Writes to file everytime a player triggers a duplication check providing information regarding the situation
- New crate configuration node previewShowsRewardCount
# If false, when the crate is previewed it will not show the reward count.
- New Default Crate-Config
# If your crate directory (config/huskycrates/crates/) is empty, a config will be pushed to the directory for you so you have an example to look into!
- New EXPERIMENTAL Main-Config node/feature virtualKeyDatabase
# Can be used to store virtual keys remotely in a mysql database
- Enabled/Disabled via useRemoteDatabase within
- If enabled, changes logic to update virtual key balance when player joins and immediately push their used keys to database.
NOTE : Requires "huskycrates" schema/database to be created in your sql instance previously ; plugin will create columns
Other Changes
- Items that are not provided with a configured name will now appropriately assume the item's name