Packet parser requires nick tag where the Node.js server didn't
teistiz opened this issue · comments
The current parser rejects packets in which a nick tag doesn't immediately follow the API version token.
To match the behavior of the Node.js implementation, it should accept any number of nick tags in the payload, including no nick tag at all (the Node.js server displays the user as "anonymous" in that case).
Example payloads that are accepted by effectserver but not valoserveri:
No nick tag:
[1, 1, 0, 0, 255, 0, 0, 1, 1, 0, 0, 127, 0]
Nick tag last:
[1, 1, 0, 0, 127, 0, 0, 1, 1, 0, 0, 255, 0, 0, 97, 98, 99, 0]