For more information see here Bug Report Template Build: 4470 Mode: Multiplayer Dedicated SERVER NAME: N/A SEED-ID: N/A If applicable: MODIFIED PLAYFIELDS: Yes, but ship weapons and cockpits are vanilla config Reproducibility: Sometimes Severity: Major Type: Combat/PvP Summary: CoQ spam due to network packet content exception Description: This issue has been plaguing the server for a while now, and there's no way we can reliably reproduce the issue, but we know it does happen in relatively short order after PvP has started. The issue occurs when 3 or more players are in SV PvP in the same playfield. The blueprint doesn't really matter, but the issue occurs when a player in an occupied cockpit (doesn't matter which one) dies to enemy fire in such a way that causes a CoQ. The weapon has to be some kind of hitscan weapon usually (we used miniguns that triggered it reliably, but we are unsure if missiles do as well). This CoQ error makes the server think the dead player is still piloting the ship, even though the ship doesn't have a cockpit anymore. Using entity commands shows the player still as as the pilot of the dead ship, even though the player has since respawned. Any number of actions done by this player will then trigger a CoQ for all other players in the same playfield (including that player). Actions known to cause CoQs at this point include firing weapons, using gm command, entering cockpits, turning a ship on and off, and probably others. The only known fix is to fully reset the server, which stops the CoQ spam, or maybe logging all players off, it's hard to tell. The error seems to occur reliably when the player and cockpit are destroyed simultaneously we think, but we are unable to reproduce this because the game seems to assume cockpit death before player death 90% of the time. We couldn't reliably trigger this regardless of what weapons we used, but we now if often happens with miniguns Steps to Reproduce: 1) Have at least 2 ships controlled by 2 hostile factions 2) Engage in PvP with 3 or more players rendered/present 3) Attacking a player with hitscan weapons only, destroy the players cockpit (not the player), ideally try and trigger both cockpit and player destruction simultaneously 4) CoQ happens with specific error (see logs), at this point the dead player may trigger more CoQs as they continue to interact on the playfield 5) Have temporary resolution by restarting the server. The affected player no longer triggers CoQs by their actions. Screenshots, Crash Logs, any other Relevant Information or Download links: Can provide more details and the full scenario where the issue is caused.
There are allot of errors related to faulty config files Any of those errors can be the reason to the network failure
