2.0.0

Updated for Pixelmon 9.3.1 on Neoforge/Minecraft 1.21.1

Full Changelog: 1.2.1...2.0.0

Note: Hex color codes in Nicknames do not parse properly at the moment when multiple colors are used at once; this is a Pixelmon bug (https://pixelmonmod.com/tracker.php?p=2&t=22591).

1.2.1

+ Fixed an issue where regex was only checking the first word of the nickname instead of the whole nickname
+ Moved spec registration to PixelmonInitEvent to resolve an unpredictable boot failure
+ Fixes event listeners not working correctly when reloading
+ On evolve, the %nickname% placeholder will now be replaced with the Pokémon species
+ Fixed unnickable spec not registering correctly
+ Added deny messages for triggering the nickname blacklist and preventing colors in nicknames
+ Added a null check to the post-evolve event to prevent a rare crash

Note: Hex color codes in nicknames do parse and display correctly but will reset back to white after a server restart or relog. This is a Pixelmon bug.

Full Changelog: 1.1.0...1.2.1

1.1.0

This update introduces new options that allow you to now fully automatically update nicknames based on specs; No more needing to set nicknames in your /give commands, or manually fix nicknames after the Pokémon has evolved!

+ Added `update-on-evolve` setting to individual nickname settings defined via config
  - Forcefully re-applies the configured nickname setting to any spec-matching Pokémon when it evolves, refreshing the %species% placeholder
  - For example, if a "Christmas Snover" evolves it will actually become a "Christmas Abomasnow" on evolve instead of keeping the name of its pre-evolution species
+ Added `update-on-received` setting to individual nickname settings defined via config
  - Forcefully apply the configured nickname setting immediately when a player receives the Pokémon
+ Added `notify-modified-on-received` toggle (Defaults to `false`)
  - If `update-on-received` is true for any setting, should the player immediately be notified that the nickname was modified? 
+ Added `replacement-list` section to config
  - If *any* placeholder returns what you specify in `find`, replace it with what you specify in `replace-with`. This can be used for example to fix custom palette, form, and species names not parsing correctly, or to use custom icons or text in place of types (ie "🔥" instead of "Fire" (if the smooth font in the game actually supports displaying the unicode symbol that is)), etc.

The following example shows how you might use these new settings; this example would make sure any pokemon with a Christmas ribbon have their define nickname format applied when it is immediately received, when the pokemon evolves, and when the player tries to modify it. If it is a Charmander, it will be nicknamed Spicy Christmas Charry Boi. If it has the "prestige" palette, it will be named Spicy Christmas Prestige Charry Boi.

notify-modified-on-received: false
force-nicknames:
    christmas-pokemon:
        name: %type1% Christmas %palette% %species%
        specs-to-match:
        - ribbon:christmas
        player-editing-allowed: true
        update-on-evolve: true
        update-on-received: true
replacement-list:
-   find: Fire
    replace-with: Spicy
-   find: Charmander
    replace-with: Charry Boi 
-   find: pixelmon.palette.prestige
    replace-with: Prestige

Note: Any forced nickname update (such as update-on-evolve or update-on-received) will set the %nickname% placeholder to be blank. This prevents a situation where the nickname will repeat itself.

Full Changelog: 1.0.0...1.1.0

1.0.0

Initial release