MRC: display still not fixed even after update

This doesn't make grammatical sense and there's that SERVER at the end in green?

"Your handle is trusted from this BBS (Expires in 4wks) " Why not just say 4 weeks?

Seems I cannot assign it to codefenix.

assigned to @codefenix

These are messages returned from the MRC server, and are not controlled within this or any other MRC clients. I can explain them though.

For the first one, there is supposed to be a break between the words "rooms" (the end of one server message) and "SERVER" (the start of the next server message). I've informed StackFault of this issue, and recently sent him a reminder.

For the second one, StackFault simply made a decision to use shorthand to express the trusted handle expiration. He runs the MRC server; that's his prerogative.

closed

I have no horse in this race, I just wanted to point out that the client can manipulate text it displays.

lineFromServer.replace(/roomsSERVER/, "rooms\r\nSERVER");

Chasing time abbreviation is likely more painful and not worth it, but also possible.

I would not attempt to manipulate incoming messages at all.

Edited to elaborate: each part of the incoming message packet has special meaning. The "SERVER" is the "from_user" field in the beginning of the next packet. Simply inserting a CR-LF in front of "SERVER" does not fix the problem, because the remaining packet string would need to be processed by the client separately from the proceeding packet. Besides, it's incomplete since the two meshed packets exceed the legal length of one packet anyway.

For the record, the Mystic clients see the same faulty startup message too.

TL;DR: The server needs to fix what it's sending out.