It seems some variables aren't parsed correctly depending on what caused part of the local to be displayed. In my case triggering the anti-spam via chatcontrol rule causes this to happen.
The rule used here is /adminchat <message> and part of the local file that was edited was Checker.Similarity to include &8{chat_line_smooth} in the message.
The debug file with these changes has been provided below.
Steps to reproduce using the debug file below.
1) talk in chat normally with the same message 2 times to trigger the anti-spam. You will see the normal output here.
2) Talk in the admin channel via chatcontrol rules /adminchat <message> with the same message 2 times to trigger the anti-spam. Here you will see the variables used aren't parsed correctly.
Note Tested on a fresh install.
It seems some variables aren't parsed correctly depending on what caused part of the local to be displayed. In my case triggering the anti-spam via chatcontrol rule causes this to happen.
The rule used here is
/adminchat <message>
and part of the local file that was edited wasChecker.Similarity
to include&8{chat_line_smooth}
in the message.The debug file with these changes has been provided below.
Steps to reproduce using the debug file below.
1) talk in chat normally with the same message 2 times to trigger the anti-spam. You will see the normal output here.
2) Talk in the admin channel via chatcontrol rules
/adminchat <message>
with the same message 2 times to trigger the anti-spam. Here you will see the variables used aren't parsed correctly.debug.zip
Minecraft Version: 1.18.2 MySQL: false BungeeCord: false