MyCommand v5.7.3
Details
-
FilenameMyCommand.jar
-
Uploaded by
-
UploadedSep 4, 2022
-
Size613.54 KB
-
Downloads11,096
-
MD53a69bad4609c8fe48dd47eb4083231b0
Supported Bukkit Versions
- 1.19.1
- 1.18.2
- 1.17
- 1.16
- 1.15
- 1.14
- 1.13
- 1.12
- 1.11
- 1.10
- 1.9
- 1.8
Changelog
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 :
minimessagetest: command: /mm type: MINIMESSAGE text: - Hello <rainbow>$player</rainbow>, isn't <underlined>MiniMessage</underlined> fun? - "<color:#FF5555>This is a <color:#55FF55>test!" - ecc ecc
With RUN_COMMAND :
minimessagetestruncmd: command: /mmr type: RUN_COMMAND runcmd: - /time set day - $mm$Hello <rainbow>$player</rainbow>, isn't <underlined>MiniMessage</underlined> fun?
Dropped 1.18.2 AnvilGUI support, added 1.19.1 and 1.19.2 support.
Scoreboards can now display more characters on 1.13+ servers.
You can now change the RAW_TEXT character needed to split the various part in config.yml
REGEX: RAW_TEXT_SPLITTER: ";"
You can now use brackets on the playername part of "%mycommand_playerdatafor_[<player_name>]_<variable_name>%" papi placeholder. This make possible to use underscores in the playernames without problems.
Added:
RUN_COMMANDS: SENT_BY_CHAT: true
Until now, commands in MyCommand always got sent as a chat message. 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 command be run as a real command. If you choose this way, every command must be registered to work (and you can use the auto register feature from the last release).
The second solution is the added prefix $PERFORM_COMMAND$, to be used before the command you want to run as it.