Bug #1135

CL_ParseServerMessage crash

Added by Spyhawk 5 months ago. Updated 3 months ago.

Status:New% Done:

0%

Priority:HighSpent time:-
Assignee:-
Category:Client
Target version:2.77
OS: Arch:

Description

Ray:
crashed

Error message: "Illegible Server message 69"

Base_Profile_Screenshot_2018.12.22_-_22.23.27.96.png (274 KB) Spyhawk, 22.12.2018 22:21

949

History

#1 Updated by IR4T4 5 months ago

@Ray how did you connect? From another mod, from server browser, +connect etlegacy.com ?

#2 Updated by Ray 5 months ago

IR4T4 wrote:

@Ray how did you connect? From another mod, from server browser, +connect etlegacy.com ?

@IR4T4
I connected thru console: /connect etlegacy.com

#3 Updated by Spyhawk 5 months ago

  • Priority changed from Urgent to Low
  • Target version changed from 2.76 to 2.78

This seems to happen very rarely. We’ll need more feedback or a way to reproduce. At first sight, this looks like some packets were lost on the way.

#4 Updated by IR4T4 5 months ago

  • Target version changed from 2.78 to 2.77

#5 Updated by IR4T4 4 months ago

  • Target version changed from 2.77 to 2.78

#6 Updated by keMoN 3 months ago

  • Priority changed from Low to High
  • Target version changed from 2.78 to 2.77

Copy-paste from a friendly server admin:
"Any idea what would cause a constant stream of "WARNING: bad command byte for client 4" errors in the server console to the point where the clients cannot move and is lagged out, then they get disconnected with the message "cl_parseservermessage: Illegible server message 224", if they try to reconnect immediately they get kicked and a temp ban.

We had this yesterday for lots of clients, I thought it was because we had exceeded the amount of maps as we had uploaded new maps prior to this, once I deleted some maps the issue did not happen again all night but it has begun again today."

#7 Updated by keMoN 3 months ago

Kimi|AHK said in TM Discord that they received this error while playing with a vanilla ET client.

#8 Updated by kimi 3 months ago

ye after that i switch to legacy client and didnt have problem

Also available in: Atom PDF