2.5.10​

- Added milestone commands
/acrates milestone <crate> set/take/add <player> <amount>
This command modifies the amount of opens

- Fixed milestone handling

- Added support for 1.20.4

- added milestones
- fixed issues with milestones
- added a way to modify the crate hitbox (Barriers)
- added randomized crate idle animations
- added more preview settings (milestone related)

- updated wikipage

Changelog - 2.5.6​

- Added KeyUseEvent
- Added placeholder parsing to reward model section
- Switched open bind from left click to right (multicrate)

Click to expand...

2.5.5​

- Added an option to show a model as a reward while the spawned reward is rumbling (while being in an animation)
- Fixed Key Bank issues
- Added an option to bind click actions to items in menus
- Fixed MEG v3.X.X loading bug
- Added a way to set a yaw of reward model

- Fixed MEG4 models rotation bug
- Fixed MultiCrate breaking

Click to expand...

1. 
   
2. - Added multicrates
   - Added command animation task
   
   NEW MULTICRATES!
   
   You can now create a Crate that contains multiple crates.
   All subcrates are gonna use the same model.
   
   It is known that Placedcrate animation won't work with this type of crate!
   
   There was a new folder made for the multicrates
   
   Example configuration:
   display-name: "&fCaja de Halloween"
   crates: # A list of crates that Multicrate contains
   - "testcrate"
   preview:
   enabled: true
   items:
   test:
   material: STONE
   display-name: "{#000000>}Special Stone lol{#FFFFFF<}"
   slot: 0
   crate-testcrate: # Binded crate item (Left-click open, Right Click preview)
   material: DIAMOND
   display-name: "{#000000>}TestCrate{#FFFFFF<}"
   slot: 2
   LARKYY, Yesterday at 5:05 PMReportLike
   
   

3. Changelog - 2.5.1​

   - Added an if statement to check if there is any available reward (If not, it wont take the key)
   - Added reward conditions
   - Fixed MEG4 animations
   
   NEW REWARD CONDITIONS
   The permission setting won't work anymore! It requires a change in your configuration!
   
   Example:
   Code (YAML):
   conditions:
   1:
   type: permission
   permission: "your.permission"
   negate: true # Shoud be the condition negated?
   

- Added an if statement to check if there is any available reward (If not, it wont take the key)
- Added reward conditions
- Fixed MEG4 animations

NEW REWARD CONDITIONS
The permission setting won't work anymore! It requires a change in your configuration!

Example:
Code (YAML):
conditions:
1:
type: permission
permission: "your.permission"
negate: true # Shoud be the condition negated?