A while ago I wrote some code that searches through the AST tree of Uberserver code, and tracks the possible paths the server takes in response to incoming protocol commands. Then, with some hacks, for each incoming command I outputted a list of (i) the outgoing commands that might be sent as a response (ii) the lines of code which send these responses. It's fairly accurate. E.g. https://pastebin.com/hgmsEPBR
Here's the code. It's only going to be useful to someone trying to fix up the lobby protocol docs after they fall into dis-repair (which is what I was doing). Leaving it here in case someone wants it years into the future..
autogenerating codes paths in Protocol.py
For the discussion of infrastructure improvements and changes.
1 post • Page 1 of 1