Let's release it, otherwise it will remain on my pc until 2023.

Added MiniMessage chat format to be used if you like it. You can achieve rawtext like results, but in a more cleaner way, and probably with less problems.

For this release you can use it in 2 way. The first one is to put as a type MINIMESSAGE, instead of TEXT, and write your messages under the text field. The other one, is to be used inside the RUN_COMMAND type, and here, you have to use the $mm$ prefix, like you'll already do for the $text$ one. Note, console support is there, but the message will appears without formatting.

Example of use :

With RUN_COMMAND :

AnvilGUI:
Dropped 1.18.2 AnvilGUI support, added 1.19.1 and 1.19.2 instead.

Scoreboard:
Scoreboards can now display more characters on 1.13+ servers.

RawText:
You can now change the RAW_TEXT character needed to split the various part in config.yml

PlaceholderAPI related :
You can now use brackets on the playername part of %mycommand_playerdatafor_[<player_name>]_<variable_name>% papi placeholder.
This change, make it possible the use of "underscores" in playernames without problem.


Commands in general (RUN_COMMAND):

file config.yml:
Until now, commands in MyCommand always got sent as a chat message. (to make unregistered commands work)
Lately with all the changes in Minecraft, sending chat colors inside a message results in a "Illegal chat character" kick message (in paper based servers).
To workaround this, i've added a way to make all the commands, listed in your runcmd list, to be performed as a command and not a chat message.
If you choose this way, every command must be registered to work (and you can use the auto register feature from the last release). Of course, if this is enabled, non-registered commands in a runcmd list will not be performed.
The second solution is the added prefix $PERFORM_COMMAND$, to be used before the command you want to run as it.