CrazyEnvoys

Changes 🔨

• Updated the internal command implementation, the changes are minimal... and are listed below!
  • envoy.admin is no longer a valid permission for commands
• Replaced all instances of legacy color codes with MiniMessage
  • The only places not touched are the hologram plugin's and their color implementations.
• Added /crazyenvoys migrate -mt [LegacyColorAll/MojangMappedAll] which you must run.
  • This migrates all color codes to MiniMessage.
• Improved runtime placeholder migration.
• Improved initial prize creation.
• Updated default configurations.
  • All materials are now lowercase, existing configurations should work.
  • All enchantments are now mojang mapped, existing configurations should work.
    • SHARPNESS → sharpness, and so on.
• Improved folia support maybe?

Bugs Fixed 🐛

• Fixed an issue with CMI Holograms by forking CMI and updating the API ourselves.

As always, Report 🐛 to https://github.com/Crazy-Crew/CrazyEnvoys/issues

What's changed?

• Fixed an issue with default tier files getting extracted despite deleting them.
• No longer allow 0 seconds being added to time related strings #162
• Fixed an issue with random spawn behavior by using the correct config option

envoys:
  generation:
    # Whether to always spawn the max amount of crates possible set below, If the option is false. Spawn locations set using /envoy edit will instead spawn.
    # Note: You should only use this if random-locations is false.
    max-drops-toggle: false
    # The max amount of crates that will spawn.
    max-drops-amount: 20
    # The min amount of crates that will spawn.
    min-drops-amount: 7
    # This option will spawn a random number of envoys between min-drops-amount and max-drops-amount.
    # Note: You must set max-drops-toggle to false otherwise this will not function.
    random-drops: true # -> This is the option it used before.
    # Random location settings
    random-locations:
      toggle: true # -> This is the option it uses now.
      max-radius: 300
      min-radius: 20

What's changed?

• Fixed an issue with DecentHolograms error due to using characters not allowed. #154
• Fixed an issue by removing ignoreCancelled(true) which allows blocks like redstone torches to work while right-clicking air #156
• Fixed a visual issue with the #sendBlockChange by delaying it by 2 ticks which is used to show the bedrock when placing or being in edit mode. #155
• Added a new feature that allows the player who started the signal flare to be announced that they started it in chat. #158
  • This adds a new message to your message file, and a new config.yml option.
• Fixed an issue with data not saving to data.yml

All new config.yml options have values that represent how they were out of the box previously

#157

• Added a new argument to the /crazyenvoys ignore command which is -s or -no
• Added the ability to turn off/on broadcasting via a new config.yml option.

New Contributors

• @InstantlyMoist

• Updated to 1.21.8.
• Fixed multiple issues on Folia.
• Updated FileManager usage.
• Added FancyHolograms as soft depend.
• Improved performance interacting/creating flares by not using ItemMeta.
• Fixed typos in pl-PL.yml #150
• Added the french translation #153

• Add support for lists with left/ended in messages.yml. (it should automatically migrate)

ended:
  - 'line 1'
  - 'line 2'

• Converted time-till-event into a list in messages.yml. (it should automatically migrate)

Changes:

• Bumped to 1.21.1
• Bumped CMI API

Added:

• A new config option to open a menu with items in it, instead of adding it to the inventory.

Fixed:

• Issue with file manager not properly loading/reloading files.

Fixed:

• Apply MaxStackSize to the player's inventory when using Player#addItem, so now instead of 99 items popping up in the inventory if giving 99 keys or any items, it'll split 64/35
  • Spigot for some odd reason made Player#addItem use the max stack size for the inventories. #hardforkwhen

Changes:

• Moved i/o operations off the main thread.
• Cleaned up build script.

Added:

• Ability to make the flare glow, the config option in config.yml defaults to false.

Fixed:

• The option to limit flares to specific regions was not being used, the wrong config option was being used internally.

Fixed:

• Player Heads were not stacking previously, they should now.

Fixed:

• Null pointer exception with HeadDatabaseAPI

Added:

• Added support for HeadDatabaseAPI (the previous way of doing custom heads i.e. eyJ0ZXh0dXJlcyI6eyJTS0lOIjp7InVybCI6Imh0dHA6Ly90ZXh0dXJlcy5taW5lY3JhZnQubmV0L3RleHR1cmUvZTVkMzE1NTkyNjFiM2U3OTAyNDc1MWZlMDdiNzExYzhmZWVmNTFkNTZjMDM2MzUyMjY5NTU4MDViYzQyODk0ZSJ9fX0= will be removed in the next major version of Minecraft.

Prizes: #The prizes that can be won.
  '1':
    DisplayName: '&6Custom Head' #The display name used in %reward%
    Chance: 75
    Drop-Items: false
    Messages:
      - '&7You have just won {reward}.'
    Items:
      # Only use this if you have HeadDatabase by Arcaniax on the server.
      - 'Item:PLAYER_HEAD, Skull:61151, Name:&cA fancy head, Lore:&eA fancy lore,&7with lines, Amount:3'

Changes:

• Removed NBT API completely (which was never used internally just shaded for some stupid reason)
• Flares are no longer identified by if the ItemStack object ids match which was hefty and unreliable, they now check for a tag added by PersistentDataContainer
  • There is no way to migrate old Flares given because they have no unique identifier we can know of.

Added:

• 1.21 support

Changes:

• https://textures.minecraft.net/texture/ is no longer needed in the Player field in prizes.
• Removed reliance on NBT-API in the ItemBuilder.

Fixed:

• Custom Skulls using Player Names / Textures were not working.

Changes:

• Check if WorldEdit is enabled before WorldGuard.
• Updated the falling block animation.
• Optimized tiers being picked when the envoy starts.

Added:

• 1.20.6 support.
• Folia support.

Removed:

• HolographicDisplays support.
• 1.20.4 support.
• Removed the toggle for bStats from the config.yml, you can toggle it in the bStats folder.

Removed:

• Example sub-folder which caused initial runtime error on first install

Changed:

• Updated to use recently added damage source api. The previous way to prevent firework damage stopped working.

Fixed:

• Error with the ItemBuilder.