Yaribz

> Indeed, it can be done done via parsing the !xxx and host messages, but this is a bit hacky and I guess not reliable because SPADS plugins could change...

> The content does matter when you try to make a GUI for it, though. Indeed, my first post is only related to the "hard to follow players chat problem"....

A quick answer because I don't have much time right now: for me only the vote system would really benefit from 2.2. For other functionalities, 2.1 would be just as...

Actually the more I think about it, the more I think introducing a few new generic commands in lobby protocol for battle data/event communications would be ideal. This would allow...

Concerning the other commands which would benefit from being included in lobby client GUI, I mostly agree with what you proposed. I guess it's the most used ones: !ring, !status...

But what about "AUTOHOSTCOMMAND command data" where the "command" parameter has to be in a whitelist in uberserver code or configuration file? That way you have the best of both...

Here is a part of the protocol updates I have in mind: [part 1](https://github.com/Yaribz/SPADS/wiki/Lobby-Protocol-Modification-Proposal-part-1:-introducing-a-generic-way-to-send-battle-data)

> Looks good so far, happy to implement that. Nice, FYI I added a section at the end about extensibility and backward compatibility. I guess it might be useful to...