- Added support for `minecraft:custom_model_data` and `minecraft:dyed_color` components. - Improved logging errors from NBT serializers - Fixed an issue where choose item GUI always used sign GUI for search regardless of the config ### How to (components) This is an example of using the `minecraft:custom_model_data` component in your item: ```yaml id: minecraft:chest count: 1 components: minecraft:custom_name: <!italic><aqua>Your Orders minecraft:lore: - <!italic><white>Click to view your orders minecraft:custom_model_data: floats: [4.0, 5.6, 99.1] strings: ["foo:bar"] colors: ["#03fcd7", "059fe7"] ``` The structures of the components are the same as vanilla. However, **there are exceptions** for the color part. `custom_model_data` has a list of colors and `dyed_color` has one color. In vanilla, you can input a hex number, an integer or a list with 3 values (red, green, blue). In Orderium, you cannot input an integer for the color, you can only input a hex string (without `0x` prefix), a hex string prefixed with `#`, a list of 3 values (like vanilla), and an object (a map) with 3 keys: red, green, and blue with values ranging from 0 to 255 (inclusive both ends).

- Allow using order placeholders in `receive-delivery` message - Storage system refactor with MySQL support - bStats is removed

### Fix Patches to some duping exploits/vulnerabilities

### Fix Incompatibility on 26.3 ### Feature Search dialog, as an alternative for sign GUI. Sign GUI is deprecated and will soon be removed.

## UPDATES This version fixes a lot (I mean A LOT) of issues in the plugin. <br> Updating is recommended to provide a more stable experience. ### Fixes - Similarity check only accepts valued data component types - Possible exploit with interacting choose item GUI - Race condition when logging money transactions - Duplicating keys when storing money transactions - Thread-safety issues with search GUI and delivery confirm dialog - Possible undefined behavior because of access of `Bukkit.getOnlinePlayers()` asynchronously - Thread-safety issues when modifying order values - Possible race condition when deducting money (more like Vault Implementer's job but eh) - Orders never get deleted in storage - Items that represent orders in main and your orders GUI don't have expires time updated unless their values are changed - Possible issue with byte array comparison for orders and order items - Possible exception when orders failed to load - Updates to orders are not atomic and don't have proper locking - Connection changes are not rolled back on exception in storage ### News - Item of an order now shows its tooltip on hover when sent as a text message ### License License is now GPL-3.0 for both the GitHub repository and Modrinth project, as required by ConfigurationMaster's license. ### Disclosure As to adapt to Modrinth's new project disclosures system, Orderium now has disclosures. <br> You can view this on the main page of the Modrinth project. ### Discord My Discord account has been permanently suspended. For more information, see the Discord server link of this Modrinth project.

# Optimizations This version mainly improves the performance impact of the plugin to servers. ## The issue 1. A bottleneck in Orderium was that strings are constantly getting deserialized to MiniMessage text components. At first, this does not sound very resource-intensive, just deserializing a string. However, it starts to create a performance impact when this happens more often. Every page, every item, every lore lines, custom name, all of them are deserialized when you execute `/order` command. 2. The plugin makes `Bukkit.getOfflinePlayer(UUID)` calls for **all** active orders whenever a player uses search. This method tends to be resource-intensive. ## The solution For the first problem, I used 2 methods to solve it: 1. Lazy loading: whenever a player executes `/order`, it generates all the pages, even if the player only accesses the first or second page. This version no longer generates all the pages, it only does when the player moves to the next page, minimizing the amount of inventories need to be created as well as `ItemStack`s. 2. Caching: The orders used to create a new `ItemStack` then deserialize the lore lines with placeholders. Now, it only creates the `ItemStack` every time the placeholder values change or the config reloads. For the second problem, I also simply cache `OfflinePlayer` and only call `Bukkit.getOfflinePlayer(UUID)` once when the server starts for each order. <hr> You can see that a lot of changes have been made. Therefore, bugs might appear in this version, because optimizing is always scary. If you found any, feel free to report an issue on the Github repository :)

### Fixes - cancel order gui config is missing - API events are not called when delivering for an order - Orders can be canceled even if it's already completed ### News - Webhook support - Order limits for different permissions - Show cost when creating order and reward when cancelling order

# READ ME! This update has many changes, please read the changelog carefully before updating. ## Config Overhaul The plugin should automatically migrate to the new formats for you. Each GUI now has its own config file instead of putting everything in `config.yml`. <br> The config files of the GUIs are under `gui/` directory. `gui.main` > `main.yml` <br> `gui.your-orders` > `your-orders.yml` <br> `gui.choose-item` > `choose-items.yml` <br> `gui.search-sign` > `search.yml` <br> `gui.delivery` > `deliver.yml` <br> `gui.enchant-item` > `enchant.yml` <br> `gui.new-order` > `new-order-dialog.yml` <br> `gui.confirm-delivery` > `confirm-delivery.yml` <br> `gui.manage-order` > `manage-order.yml` In container GUIs, you can now specify the amount of rows. <br> For main, your orders, choose items, enchant item GUIs, you can now specify a list of slots where the orders/items/enchantment books should be put in respectively. <br> Buttons now have 2 keys, `item` and `slot`; name, lore, item model of the button is now moved to the `item` key, under `components`, providing a more vanilla format. <br>`name-prefix` in enchant GUI's config is changed to `name.active` and `name.inactive` `sort-prefix` and `sort-types` are now merged to `sorts-display`, allowing you to set the text for each sort type when it is active and inactive. ## FastStats The plugin now uses [FastStats](https://faststats.dev/) to collect anonymous data. Besides default metrics it collects, Orderium also tracks errors at different places, and these data: - API Usage: a boolean determines if your server is using API from Orderium - Experimental features: a string array contains names of experimental features being used - Order amount: an integer shows the amount of orders have been created - Items collected: an integer shows the amount of items collected from all orders

- Removed empty items.db file - Fix bStats not working correctly with config option - Fix packetevents listeners spamming errors if the plugin is disabled - Fix not recognizing economy plugin if it enables after Orderium - Fix commands not unregistered if the plugin is disabled - Add permission `orderium.use` for executing command `orders`

- Fixed an issue with false warning of downgrading plugin. If you didn't downgrade the plugin, you can safely ignore the message.