Repository navigation
Update documentation: packet-wise flag is called cap not add-cap - #3018
Conversation
|
Thank you! Out of curiosity, what are you planning to do with the parser? |
I was trying to stitch together a code-generator for the network protocol. I was hoping to be able to snoop into the communication for turn changes. No offense intended, the one in the repo looked very scary and I didn't dare hack it. I've not gotten any further than parsing because I'm missing all the enum-declarations from C. While I would feel honored to replace yours, it would probably not increase maintainability. Unless you prefer hacking someones Haskell code instead of python. |
|
I have put it up here, in case of further interest: https://gist.github.com/Hyalunar/1c0663e35f6ea77a3cc2d5795474d343 |
|
Thanks! I don't know how much info you want to gather about TC but it might be just a few packets, and in that case it's more efficient to write the decoder by hand. |
Perform the in fix discussed in #3017
The flag name for packet capability-dependence was probably mis-spelled because the name is so similar to the field-wise flag.