If someone has certain characters in their name, it appears that the chat log can no longer be viewed past their name using the built-in TU Dedicated Server GUI chat log viewer. Viewing the raw text file with an editor (N++, Notepad, etc.) still works.
Steps to Reproduce
Have a player with invalid characters in their name join a dedicated condo.
What I expected to happen
Chat log viewer functions as normal.
What happened
TU Dedicated Server GUI chat log viewer does not work after player with invalid characters join.
Notes / Media
Note that viewing TowerServer_Chat.txt with Notepad works fine, while the built-in chat log fails to load beyond the āĆTĆXoĆNB o u n c eā playername.
Just a guess: this may be a DOS v. UNIX line ending conflict.
its a bit more readable there, but Iāve been unsuccessful in finding a way to automate cleaning up chat logs like this, with awk, grep, sed, etc. however I found I can cut and paste each of those lines in the hypervisor GUI and that cleans it up somehow, but thatās entirely manual
Not sure if that helps anyhow, but if it might, Iām for it, cause this is particularly painful for me, to keep track of who canāt read and touches keypads that are meant for friends only, which are the ones being tagged as āneeds banā
EDIT: Iāve tried using perl, sed, tr, awk, and grep actually, looking through my bash history, to somehow exclude these illegal characters, but Iāve not found or gotten anything working yet with any of those.
Iām still noticing this today, unchanged from my earlier screenshots. If the fix you were working on was finished and pushed, it hasnāt had any effect on linux dedicated servers, at least any that I have seen.
