Open WalkerY opened 9 years ago
may be some network issue.. but I suspect some multithreading issue as well
happened again, this time "ERROR: CL_ParseServerMessage: Illegible server message 128" I suspect, that it also might not be the error, but purposeful behaviour of ID to disconnect long sessions. But then they would use some usual disconect msg I gues. Anyway, recently this is almost the only thing that makes bot disconnected and therefore critical as far as I am concerned.
It's not a big issue when bot is a server owner as it can automatically reconect with my autoconnect plugin. BUT it would be highly prefered for bot to use a non-paid account only and in this case it ends up without op after reconnect and therefore needs manual intervention.
One possible solution is to make ql ignore this msg, I could test if this solution doesn't make ql unstable.
Sometimes bot is disconnected from server and I have this message logged from console as reason. Maybe this msg can be ignored somehow instead of disconnecting?