BlockParticles - Changelog

BlockParticles 1.13.1

on Oct 23, 2024

Changes:

Updated default config.yml to use HeadDatabaseAPI head ids. /hdb search <head> when the plugin is installed.
- We no longer support the old way of getting ids. (they might still work, so migrate when you can)

  heads:
    plants:
      #Tomato
      - '1130'
      #Mango
      - '32596'
      #Cherry
      - '31879'
      #Melon
      - '20577'
      #Mushroom
      - '21906'
      #Orange
      - '59223'
      #Golden Apple
      - '79863'

Properly cancel all active particles on reload, and clean up our garbage.

Fixed:

Not getting tab completion with the permission bparticles.admin, because the check for the permission was if you had the permission.
Fixed an issue with custom heads from HeadDatabaseAPI.
- We load everything after the HeadDatabaseAPI's database loads if the plugin is enabled.
Fixed the menu that pops up when you do /bp set <name>
- It was not updating items properly when you hit Fountains to view fountain types etc.

BlockParticles 1.13

on Oct 23, 2024

Download

Additions:

Added folia support (untested).
Added bparticles.admin to the plugin.yml
- This will fix a few niche issues, it's mainly for tab completion!

Changes:

Improved readability and slight performance increase by using single variables for commonly called methods.
Save/load files such as config.yml or data.yml off the main thread.
- This ensures that the main thread can run without issue, which is responsible for everything in some way.
No longer store the player object in a hashmap, reduces memory footprint since we use the uuid (I don't know if memory footprint is the right word, Correct me if I am wrong.)
Updated how the inventory that displays particles or fountain types is handled.
- No longer check the inventory title to see if it's our inventory.
- No longer check display name on items to find out which set of items to show a player.
- This effectively keeps the menu secure from unwanted eyeballs.
Updated to 1.21.1.
Updated vital api.
Updated the itembuilder.
- With updating the ItemBuilder, and Vital API. You can expect more configuration to how the plugin works.
Cleaned up unused methods.
Send a message if the location you are trying to delete does not exist.
End all for loops early, if we find what we need and utilize booleans to send messages depending on the outcome (true/false).

Future Changes:

A current list of things I thought of that need to be done. If you have any suggestions, hop over to our issues tab!

Ability to configure all messages.
- The messages will be using MiniMessage, since we never had a configuration. I do not see a point in using legacy color codes.
Ability to have control over what the particles look like.
- The color, The amount of particles as an example!
Better default storage, easier management for admins.