Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MiniMessage formatting isn't parsed correctly in command usage messages #5941

Open
AfkF24 opened this issue Sep 19, 2024 · 0 comments
Open
Labels
bug: unconfirmed Potential bugs that need replicating to verify.

Comments

@AfkF24
Copy link

AfkF24 commented Sep 19, 2024

Type of bug

Other unexpected behaviour

/ess dump all output

https://essentialsx.net/dump.html?id=0f67e7d0773c4bce881387f3a94ef038

Error log (if applicable)

No response

Bug description

Title

Steps to reproduce

  1. In config.yml set verbose-command-usages: false (didn't test if it still happens while this is true)
  2. Change some command usage message in custom language file, e.g.
msgCommandDescription=
msgCommandUsage=<yellow>Test\: <gold>/<command> <arg1> <arg2></gold>.
msgCommandUsage1=<yellow>Test\: <gold>/<command> <arg1> <arg2></gold>.
msgCommandUsage1Description=
  1. /ess reload or restart the server (when this starts working on a random occasion, Custom command usage messages default to English versions #5940)

Expected behaviour

Formatting tags should get parsed correctly

Actual behaviour

Formatting tags don't get parsed
image

Additional Information

No response

@AfkF24 AfkF24 added the bug: unconfirmed Potential bugs that need replicating to verify. label Sep 19, 2024
@EssentialsX EssentialsX deleted a comment Sep 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug: unconfirmed Potential bugs that need replicating to verify.
Projects
None yet
Development

No branches or pull requests

1 participant