FlyHack violations while not really getting kicked
Hi guys,

In the last couple of days some players are getting FlyHack violations in which it says the player is getting kicked. Strange thing though: the players are not really getting kicked and the FlyKick message is being spammed in chat about 50 times. Anybody know what causes this? I have added a screenshot below.



This happened to multiple players. Everytime the chat keeps getting spammed like crazy.

I hope someone has more info on this.

Thanks in advance.
I suppose something cancels the kick?
5b6ed4c9ac8e4.jpg misticos
I suppose something cancels the kick?

Do you know what could be causing this?

Edit: something strange going on. Server log is usually about 5MB. Log is 1.37GB right now. Downloading it to see what's going on.

I just opened my server log (which was 1.37gb) and I noticed the following error was printed a million times.

ArgumentException: is negative
Parameter name: count
  at (wrapper managed-to-native) System.Buffer.InternalBlockCopy(System.Array,int,System.Array,int,int)
  at System.IO.StreamWriter.Write (System.Char[] buffer, System.Int32 index, System.Int32 count) [0x00094] in <437ba245d8404784b9fbab9b439ac908>:0 
  at System.IO.TextWriter.WriteLine (System.String value) [0x00070] in <437ba245d8404784b9fbab9b439ac908>:0 
  at System.Console.WriteLine (System.String value) [0x00000] in <437ba245d8404784b9fbab9b439ac908>:0 
  at Facepunch.Network.Raknet.Server.Kick (Network.Connection cn, System.String message, System.Boolean logfile) [0x00071] in <99d30e73aa6441ef8d8e9b1ee18b21b8>:0 
  at Network.Server.Kick (Network.Connection cn, System.String message) [0x00000] in <d40366da25394b4eb92a161089b305e1>:0 
  at ServerMgr.DoTick () [0x0004c] in <8acaac15a4ae4076850980dfc1a91cc1>:0 
 
(Filename: <437ba245d8404784b9fbab9b439ac908> Line: 0)​
Well this pretty much sounds like something that should not happen. Restart your server.
5b6ed4c9ac8e4.jpg misticos
Well this pretty much sounds like something that should not happen. Restart your server.

Seems to be fixed. Thanks for your reply.