The server sends op_codes which the client doesn't understand.
I'm not aware if any of those messages would be even relevant for the client (as in: it would appreciate the information but the message would have to be sent in a different format or at least using a different op_code) or if the information the server tries to send, has no meaning for the client at all.
I have attached one of those errors, and the op_code the client can't handle is 0x41d - according to the comment in opcodes.h the last/"biggest" code in Vanilla would be 0x342, so the client might be indeed right to complain.
Steps to Reproduce
Play Vanilla WoW for a while
Receive Errors
Read the errors
Scratch your head and think "Odd. Those shouldn't be here!?"
Expected behavior
The client fully understands all the data it receives from the server
Suggested Workaround
Delete Blizzard's Error Application so it doesn't pop up and just set up a cron job to delete the error logs ever day
Bug Details
The server sends op_codes which the client doesn't understand. I'm not aware if any of those messages would be even relevant for the client (as in: it would appreciate the information but the message would have to be sent in a different format or at least using a different op_code) or if the information the server tries to send, has no meaning for the client at all.
I have attached one of those errors, and the op_code the client can't handle is 0x41d - according to the comment in opcodes.h the last/"biggest" code in Vanilla would be 0x342, so the client might be indeed right to complain.
Steps to Reproduce
Expected behavior
The client fully understands all the data it receives from the server
Suggested Workaround
Delete Blizzard's Error Application so it doesn't pop up and just set up a cron job to delete the error logs ever day
Crash Log
This is a CLIENT(!!!) error:
Core SHA1 Commit Hash
I don't know
Database SHA1 Commit Hash
I don't know
Operating System
Debian Buster
Client Version
1.12.1 (Classic)