DrMeepso / WebFishingCove

A dedicated server for WebFishing!
43 stars 7 forks source link

"Error responding to packet!" #19

Closed iNightboat closed 1 day ago

iNightboat commented 1 day ago

After starting the server, my entire console gets clogged with the error "Error responding to packet!". Because of this, login messages, sending messages from the console, and possibly something else stop working. How can I get rid of this incessant spam and why can this happen?

p.s. the whole error is displayed in the console:

-- Error responding to packet! -- System.IO.InvalidDataException: The archive entry was compressed using an unsupported compression method. at System.IO.Compression.Inflater.Inflate(FlushCode flushCode) at System.IO.Compression.Inflater.ReadInflateOutput(Byte bufPtr, Int32 length, FlushCode flushCode, Int32& bytesRead) at System.IO.Compression.Inflater.InflateVerified(Byte bufPtr, Int32 length) at System.IO.Compression.DeflateStream.CopyToStream.CopyFromSourceToDestination() at Cove.Server.Utils.GzipHelper.DecompressGzip(Byte[] gzipBytes) in /home/runner/work/WebFishingCove/WebFishingCove/Cove/Server/Utils/GzipHelper.cs:line 15 at Cove.Server.CoveServer.OnNetworkPacket(Byte[] packet, CSteamID sender) in /home/runner/work/WebFishingCove/WebFishingCove/Cove/Server/Server.Packet.cs:line 14 at Cove.Server.CoveServer.RunNetwork() in /home/runner/work/WebFishingCove/WebFishingCove/Cove/Server/Server.cs:line 359

DrMeepso commented 1 day ago

This is happening Because someone is connecting and sending packets are in the incorrect format for what the server is expecting. Dose this happen only after you or someone else joins, if so remove any mods you have and the error should go away. I'll add a hide packet error message config setting in the next update

DrMeepso commented 1 day ago

Fixed in nightly 79

iNightboat commented 17 hours ago

Updated to nightly-82

I may be wrong, but after disabling the error display via the config, the login messages disappeared when logging on to the server. Maybe "joinMessage" is also considered an error and is not displayed in the console because of this, so please check.

iNightboat commented 17 hours ago

Updated to nightly-82

I may be wrong, but after disabling the error display via the config, the login messages disappeared when logging on to the server. Maybe "joinMessage" is also considered an error and is not displayed in the console because of this, so please check.

Also, the display of user messages has disappeared in the console. I think that "showErrors" turned off not only errors, but also all system messages displayed earlier in the console.