# 1.14.1 Hey there! It's been a quick moment since we last updated you all. Here's a whole heap of new features and changes. One important change that has happened since our last update is DeluxeMenus is now an open sourced project on GitHub, so feel free to help us on future updates or just follow along with changes as they happen. https://github.com/HelpChat/DeluxeMenus/ ## Fixes And Changes: - Fixed smithing tables being limited to 3 out of 4 slots in 1.20+. - Fixed `material: placeholder-` not properly updating when reloading the menu (using `/dm reload`). - Fixed tipped arrows not supporting the `potion_effect` option. - `model_data` supports negative values (for versions that still use the old option). - Fixed armor materials showing stone instead of air when armor was not placed in the respective slot. - Fixed target set in `/dm open -p:` not being used to parse placeholders inside actions. - Removed `hide_effects` option as this item flag was removed. - Fixed `update_interval` changing to 10 if value is set to 1. - Changed `/dm list` command. It is now paginated. To get the old list, simply use `/dm list all`. - Fixed `[sound]` action on 1.21.3 and newer versions. - Fixed lore containing the new line symbol `\n` not properly being updated when `update_interval` and `update` options were enabled. - Fixed `[commandevent]` action. The internal behavior was changed from a CommandPreProcessEvent to do the same as the `[player]` action. ## The New Stuff: - Added argument requirements.

Example

```yaml menu_title: "{player}'s Profile" size: 9 open_command: dprofile register_command: true args: player: requirements: regex: type: "regex matches" input: "{player}" regex: "^[a-zA-Z]{2,16}$" deny_commands: - "[message] That's not a valid player!" length: type: "string length" input: "{player}" min: 2 max: 32 deny_commands: - "[message] Player must be between 2 and 32 characters long." player: type: "is object" input: "{player}" object: "player" deny_commands: - "[message] Must be a player's username or UUID." count: requirements: size: type: ">" input: "{count}" output: "5" deny_commands: - "[message] Count must be at least 5." items: health: slot: 0 material: STONE display_name: "{player}'s health => {count}" lore: - "%parseother_{{player}}_{player_health}%" ```

- Added a new requirement type `string length`. It has 3 options: - `input` (required): The string used in the requirement - `min` (required): The minimum length the string should be - `max` (optional): The maximum length the string should be - Added a new requirement type `is object`. It has 2 options: - `input` (required): The value to be checked - `object` (required): The type of object to check for This requirement attempts to parse the given input as a certain type of Java object. Supported objects are: int, double, uuid, and player. (player supports both player name and UUID) - Added support for MMOItems materials `material: mmoitems-ITEMTYPE:ITEMID` - Added support for ExecutableBlocks materials `material: executableblocks-ITEMID` - Added support for ExecutableItems materials `material: executableitems-ITEMID` - Added support for SimpleItemGenerator materials `material: simpleitemgenerator-ITEMID` - Added support for Nexo materials `material: nexo-ITEMID` - New `lore_append_mode` option for items. In case you are using materials from different plugins such as MMOItems, they come with their own lore. This option decides what to do with the lore you specify inside the menu. Valid options: `IGNORE`, `OVERRIDE`, `TOP`, `BOTTOM`. Default value is `OVERRIDE`. - New `light_level` option. Takes a number from 0 to 15 and can be used to change the light level of the new LIGHT item. - Added new `trim_material` and `trim_pattern` options to set armor trims for armors. Valid values can be found here: https://hub.spigotmc.org/javadocs/bukkit/org/bukkit/inventory/meta/trim/TrimMaterial.html https://hub.spigotmc.org/javadocs/bukkit/org/bukkit/inventory/meta/trim/TrimPattern.html - Added a new `damage` option. It sets the damage of an item such as armor - Added support for arguments to be used with the `[opengui]` and `[openguimenu]` actions. Example: `- '[openguimenu] MENU1 arg1 arg2'`. The arguments are not required and maintain the old behavior if they are not specified. - Added new PlaceholderAPI placeholders: `%deluxemenus_is_in_menu%`, `%deluxemenus_opened_menu%`, `%deluxemenus_last_menu%` - `%deluxemenus_opened_menu%` - Returns the ID of the menu that the player currently has open - `%deluxemenus_has_open_menu%` - Returns yes/no if a user has a menu opened - `%deluxemenus_previously_opened%` - Returns the previous ID of the menu that the player had opened - Added a new requirement type `has permissions`. It works just like `has permission` but it takes in a list of permissions. It also has a `minimum` option to only check for a number of permissions from the list.

Example

```yaml _requirement: requirements: perms: type: "has permissions" minimum: 1 permissions: - perms.1 - perms.2 ```

- Added support for item hooks inside the `has item` requirement type. Example: `material: itemsadder-` - Added new item options: `hide_tooltip`, `enchantment_glint_override`, `rarity`, `tooltip_style`, and `item_model` - `hide_tooltip` - Hides the tooltip of the item completely - `enchantment_glint_override` - If true, the item will glint, even without enchantments; if false, the item will not glint, even with enchantments - `rarity` - Change the item rarity. Valid item rarities: https://hub.spigotmc.org/javadocs/spigot/org/bukkit/inventory/ItemRarity.html - `tooltip_style` - Use custom sprites for tooltip background and frame - `item_model` - Change the item model - Added new item options: `nbt_byte`, `nbt_bytes`, `nbt_short`, `nbt_shorts`. They are used for setting short and byte values - Added tab completion for the `/dm ...` commands - Added new commands for managing Metadata

Metadata Command Reference

Commands for handling metadata (with support for placeholders): - `show`: Gets the stored value at the specified key as long as it matches the specified type - `list`: Lists all key-value pairs of a specified type - `set`: Sets a value of specified type at the specified key (if a value exists at the given key, it will override it only if the type matches) - `remove`: Removes a value of specified type from the specified key (as long as the existing value matches the given type) - `add`: Used for addition on number types (if no value exists at the given key yet, the addition will be done on a `0` value) - `subtract`: Used for subtraction on number types (if no value exists at the given key yet, the subtraction will be done on a `0` value) - `switch`: Used for switching boolean values. Since `BOOLEAN` type is just an alias for `String`, it will also work for `String` types as long as the values are `true` or `false` (case-insensitive)

- Added a new item option: `model_data_component`. This adds support for the new custom model data component

Example

```yaml items: test: material: dirt slot: 0 model_data_component: strings: ["string1", "string2"] floats: [1, 2, 3] flags: ["true", "false", "true"] colors: ["255, 255, 255", "0, 0, 0"] ```

## Other Important Changes: - Placeholders are parsed before arguments. To change back to the old behavior add `arguments_support_placeholders: true` to the menus you want to revert the change for. Long rant/explanation: This was done for security reasons. Some placeholders do more than simply return values. They execute code based on input values. Arguments are unsanitized user input. So this could lead to some issues. If you're sure that your placeholders don't have weird behaviors that can be taken advantage of, re-enable this option. - Deprecated the following options: `hide_attributes`, `hide_enchantments`, `hide_unbreakable`. The `item_flags` options should be used instead. - Deprecated the `data` option. The `damage` option should be used instead. - Removed support for Minecraft 1.13.2 to 1.16.4. Only supported versions now are 1.16.5 and higher. ## Limitations: - NBT options are not currently supported for 1.21.4+. We're investigating the usage of this particular feature to determine whether it should be brought back. ## Thanks: We want to give a quick shoutout to all those who contributed to this release, BlitzOffline, cj89898, Kqliber, Starmism, iGabyTM, Oribuin, LoJoSho, darbyjack, DongShaoNB, Tanguygab, MemencioPerez, Krakenied, galsever, ValeraShimchuck, xmorose, Boy0000, BitByLogics, LagClear & more. Also thanks to those on the [Discord](http://discord.gg/helpchat) who have been testing early dev builds over on our [Jenkins](https://ci.extendedclip.com/job/DeluxeMenus/)! As always, if you have any issues or questions feel free to jump on our [Discord](http://discord.gg/helpchat).