Legacy formatting codes have been detected in a MiniMessage string
danieliustt opened this issue · 6 comments
Type of bug
Error in console
/ess dump all output
Caused by: com.earth2me.essentials.libs.kyori.adventure.text.minimessage.internal.parser.ParsingExceptionImpl: Legacy formatting codes have been detected in a MiniMessage string - this is unsupported behaviour. Please refer to the Adventure documentation (https://docs.advntr.dev) for more information. §fKomanda §ebaltop §fnepavyko:
Error log (if applicable)
https://paste.gg/p/anonymous/fc571eef0c84402ea7285832e3242b52
Bug description
Caused by: com.earth2me.essentials.libs.kyori.adventure.text.minimessage.internal.parser.ParsingExceptionImpl: Legacy formatting codes have been detected in a MiniMessage string - this is unsupported behaviour. Please refer to the Adventure documentation (https://docs.advntr.dev) for more information.
§fKomanda §ebaltop §fnepavyko:
Steps to reproduce
Caused by: com.earth2me.essentials.libs.kyori.adventure.text.minimessage.internal.parser.ParsingExceptionImpl: Legacy formatting codes have been detected in a MiniMessage string - this is unsupported behaviour. Please refer to the Adventure documentation (https://docs.advntr.dev) for more information.
§fKomanda §ebaltop §fnepavyko:
Expected behaviour
Caused by: com.earth2me.essentials.libs.kyori.adventure.text.minimessage.internal.parser.ParsingExceptionImpl: Legacy formatting codes have been detected in a MiniMessage string - this is unsupported behaviour. Please refer to the Adventure documentation (https://docs.advntr.dev) for more information.
§fKomanda §ebaltop §fnepavyko:
Actual behaviour
Caused by: com.earth2me.essentials.libs.kyori.adventure.text.minimessage.internal.parser.ParsingExceptionImpl: Legacy formatting codes have been detected in a MiniMessage string - this is unsupported behaviour. Please refer to the Adventure documentation (https://docs.advntr.dev) for more information.
§fKomanda §ebaltop §fnepavyko:
@SrBedrock Legacy files will not be converted if placed in
plugins/Essentials/messages. This folder is only for use with MiniMessage files.EssentialsX may have already marked your files as converted when you upgraded. With the server stopped, edit
plugins/Essentials/upgrades-done.ymland changeupdateLegacyToAdventure: truetofalse, then replace your legacy files inplugins/Essentials/and restart the server.
@danieliustt Please try following the steps above. If this is still an issue after following the above steps, you need to follow the instructions in the issue template and provide the information requested, otherwise we can't look into this properly.
@danieliustt You can use the HelpChat MiniMessage String Converter to convert your custom message file to use Adventure codes.
Are you using a custom messages file?
If so, you should place the legacy file in plugins/Essentials/ where it will get converted automatically. Do not edit the jar as this is unsupported and these messages will not get converted.
@mdcfe I use a custom messages file, and it was not automatically converted. The file was inside plugins/Essentials/, and in this case, the conversion was not carried out, and the plugin's default file for my language was used instead. When placing it inside the plugins/Essentials/messages/ folder, an error is thrown: https://pastes.dev/QCJ8uB4qy7
Now, custom language files must be inside plugins/Essentials/messages/, and no conversion is performed, regardless of which folder the file is in.
@SrBedrock Legacy files will not be converted if placed in plugins/Essentials/messages. This folder is only for use with MiniMessage files.
EssentialsX may have already marked your files as converted when you upgraded. With the server stopped, edit plugins/Essentials/upgrades-done.yml and change updateLegacyToAdventure: true to false, then replace your legacy files in plugins/Essentials/ and restart the server.
