MiniMessage prefixes from LuckPerms incorrectly converted to Legacy format when ParsePlayerNamesWithMiniMessage is enabled

[MrShard]

Description: Problem Description: When using LuckPerms prefixes in MiniMessage format (e.g., <#e3c4a6>⭐ ), InteractiveChatDiscordSRVAddon automatically converts them to Legacy format (§x§e§3§c§4§a§6⭐ §r), which causes a parsing error when the ParsePlayerNamesWithMiniMessage: true setting is enabled. Steps to Reproduce:

Set a prefix in LuckPerms using MiniMessage format:

/lp group owner meta setprefix 100 "<#e3c4a6>⭐ "

In InteractiveChatDiscordSRVAddon config, set:

yaml ParsePlayerNamesWithMiniMessage: true

Expected Behavior: The prefix should be correctly processed in MiniMessage format without errors. Actual Behavior: The prefix is converted to Legacy format, and then the plugin attempts to parse it as MiniMessage, causing an error:

[00:11:40 WARN]: com.loohp.interactivechat.libs.net.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.
[00:11:40 WARN]:        <§x§e§3§c§4§a§6>⭐ <reset>MisterShard <gray>⌚
[00:11:40 WARN]:           ^^
[00:11:40 WARN]:        at InteractiveChat-4.3.2.0.jar//com.loohp.interactivechat.libs.net.kyori.adventure.text.minimessage.internal.parser.TokenParser.parseString(TokenParser.java:170)
[00:11:40 WARN]:        at InteractiveChat-4.3.2.0.jar//com.loohp.interactivechat.libs.net.kyori.adventure.text.minimessage.internal.parser.TokenParser.resolvePreProcessTags(TokenParser.java:112)
[00:11:40 WARN]:        at InteractiveChat-4.3.2.0.jar//com.loohp.interactivechat.libs.net.kyori.adventure.text.minimessage.MiniMessageParser.parseToTree(MiniMessageParser.java:195)
[00:11:40 WARN]:        at InteractiveChat-4.3.2.0.jar//com.loohp.interactivechat.libs.net.kyori.adventure.text.minimessage.MiniMessageParser.parseFormat(MiniMessageParser.java:209)
[00:11:40 WARN]:        at InteractiveChat-4.3.2.0.jar//com.loohp.interactivechat.libs.net.kyori.adventure.text.minimessage.MiniMessageImpl.deserialize(MiniMessageImpl.java:82)
[00:11:40 WARN]:        at InteractiveChat-4.3.2.0.jar//com.loohp.interactivechat.libs.net.kyori.adventure.text.minimessage.MiniMessageImpl.deserialize(MiniMessageImpl.java:46)
[00:11:40 WARN]:        at InteractiveChatDiscordSrvAddon-4.3.2.0.jar//com.loohp.interactivechatdiscordsrvaddon.listeners.DiscordCommands.onSlashCommand(DiscordCommands.java:774)
[00:11:40 WARN]:        at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
[00:11:40 WARN]:        at java.base/java.lang.reflect.Method.invoke(Method.java:580)
[00:11:40 WARN]:        at DiscordSRV-Build-1.30.1.jar//github.scarsz.discordsrv.api.ApiManager.invokeMethod(ApiManager.java:344)
[00:11:40 WARN]:        at DiscordSRV-Build-1.30.1.jar//github.scarsz.discordsrv.api.ApiManager.handleSlashCommandEvent(ApiManager.java:319)
[00:11:40 WARN]:        at DiscordSRV-Build-1.30.1.jar//github.scarsz.discordsrv.api.ApiManager.onSlashCommand(ApiManager.java:293)
[00:11:40 WARN]:        at DiscordSRV-Build-1.30.1.jar//github.scarsz.discordsrv.dependencies.jda.api.hooks.ListenerAdapter.onEvent(ListenerAdapter.java:483)
[00:11:40 WARN]:        at DiscordSRV-Build-1.30.1.jar//github.scarsz.discordsrv.dependencies.jda.api.hooks.InterfacedEventManager.handle(InterfacedEventManager.java:96)
[00:11:40 WARN]:        at DiscordSRV-Build-1.30.1.jar//github.scarsz.discordsrv.dependencies.jda.internal.hooks.EventManagerProxy.handleInternally(EventManagerProxy.java:88)
[00:11:40 WARN]:        at DiscordSRV-Build-1.30.1.jar//github.scarsz.discordsrv.dependencies.jda.internal.hooks.EventManagerProxy.handle(EventManagerProxy.java:70)
[00:11:40 WARN]:        at DiscordSRV-Build-1.30.1.jar//github.scarsz.discordsrv.dependencies.jda.internal.JDAImpl.handleEvent(JDAImpl.java:159)
[00:11:40 WARN]:        at DiscordSRV-Build-1.30.1.jar//github.scarsz.discordsrv.dependencies.jda.internal.handle.InteractionCreateHandler.handleCommand(InteractionCreateHandler.java:75)
[00:11:40 WARN]:        at DiscordSRV-Build-1.30.1.jar//github.scarsz.discordsrv.dependencies.jda.internal.handle.InteractionCreateHandler.handleInternally(InteractionCreateHandler.java:59)
[00:11:40 WARN]:        at DiscordSRV-Build-1.30.1.jar//github.scarsz.discordsrv.dependencies.jda.internal.handle.SocketHandler.handle(SocketHandler.java:36)
[00:11:40 WARN]:        at DiscordSRV-Build-1.30.1.jar//github.scarsz.discordsrv.dependencies.jda.internal.requests.WebSocketClient.onDispatch(WebSocketClient.java:952)
[00:11:40 WARN]:        at DiscordSRV-Build-1.30.1.jar//github.scarsz.discordsrv.dependencies.jda.internal.requests.WebSocketClient.onEvent(WebSocketClient.java:839)
[00:11:40 WARN]:        at DiscordSRV-Build-1.30.1.jar//github.scarsz.discordsrv.dependencies.jda.internal.requests.WebSocketClient.handleEvent(WebSocketClient.java:817)
[00:11:40 WARN]:        at DiscordSRV-Build-1.30.1.jar//github.scarsz.discordsrv.dependencies.jda.internal.requests.WebSocketClient.onBinaryMessage(WebSocketClient.java:991)
[00:11:40 WARN]:        at DiscordSRV-Build-1.30.1.jar//github.scarsz.discordsrv.dependencies.ws.client.ListenerManager.callOnBinaryMessage(ListenerManager.java:385)
[00:11:40 WARN]:        at DiscordSRV-Build-1.30.1.jar//github.scarsz.discordsrv.dependencies.ws.client.ReadingThread.callOnBinaryMessage(ReadingThread.java:276)
[00:11:40 WARN]:        at DiscordSRV-Build-1.30.1.jar//github.scarsz.discordsrv.dependencies.ws.client.ReadingThread.handleBinaryFrame(ReadingThread.java:996)
[00:11:40 WARN]:        at DiscordSRV-Build-1.30.1.jar//github.scarsz.discordsrv.dependencies.ws.client.ReadingThread.handleFrame(ReadingThread.java:755)
[00:11:40 WARN]:        at DiscordSRV-Build-1.30.1.jar//github.scarsz.discordsrv.dependencies.ws.client.ReadingThread.main(ReadingThread.java:108)
[00:11:40 WARN]:        at DiscordSRV-Build-1.30.1.jar//github.scarsz.discordsrv.dependencies.ws.client.ReadingThread.runMain(ReadingThread.java:64)
[00:11:40 WARN]:        at DiscordSRV-Build-1.30.1.jar//github.scarsz.discordsrv.dependencies.ws.client.WebSocketThread.run(WebSocketThread.java:45)

And in Discord: Unable to retrieve data. (-2)

Additional Information:

PlaceholderAPI correctly returns the prefix in MiniMessage format: /papi parse MisterShard %vault_prefix% outputs <#e3c4a6>⭐ This confirms that LuckPerms is configured correctly and the issue is specifically with how InteractiveChatDiscordSRVAddon processes the placeholder

Versions:

InteractiveChat: 4.3.2.0 InteractiveChatDiscordSRVAddon: 4.3.2.0