The ; replacement is due to implementation details and is DNF.
okay, next update will allow % if it is followed by a space of the end of a string. I think the # problem is inherit in how we (abuse) saytext, so unless you can make it crash that one is DNF too.
These symbols are easily passed thru if typed in console:
] say "a;#%b"
Player: a;#%b
May be you can just fix messagemode input and processing?
Also will be nice if you will make it UTF8 enabled. I can create separate issue and give additional comments on it if you need this.
Thanks!
Nothing extracted yet.
% can't be produced in the chat at all. ";" gets replace with ",", however you use console "say ;" and it will be printed correctly.
There are custom plugins that add "%" functionality back, but then stuff like "%s" will get replaced with player's name, and all sorts of weird stuff, even crashing the client. It would be nice if % was allowed, and chat messages were not passing these filters that replace formatting strings to garbage.
There's another bug in the chat, where you can write # strings from titles.txt, and they will actually get replaced, and possibly break your chat due to broken formatting.