@Dune since chiller and fookonauts clients are caught up to master most of the time, people are actually indirectly playing on the nightly, is his point I guess
09:43
CChat just has a lot of behaviour that's not very easy to refactor
it doesn't for me either, but it working fine on other servers suggests to me that they are doing something wrong, rather then the client doing something wrong
e.g. the same exact alivefng server sends [chat_commands]: adding server chat command: name='help' args='<command>' help='show the cmd list or get more information to any command'
11:59
this is also wrong
12:00
it should be "s" or "r" for an old server and a new server can add a description with "s[command]"
12:00
@Dune that message is literally printed out as soon as we unpack the msg
This kind of broken server commands never worked right? not like we broke compatibility somewhere
12:04
The way to make it work in that case would be to send plain text to the server, but you don't want to set that as a fallback in case the server doesn't catch the command, right, that's dangerous
Okay how about this, if parsing fails, I check that the currently selected command is registered by the server, if it is, I just send the command and arguments as is in a command packet