Identifying Heavy Packets and Exporting Error Logs

Excessive packet sizes can lead to payload errors, packet size limit errors, and client decoding crashes. You can identify which packet types generate the most traffic and dump the offending data to your logs.

Review Server Packet Summaries

To view total bandwidth consumption sorted by network message type, run this command on your server:

/connectivity packetsSummary

You can also append a duration from 1 to 5 to view data over a specific number of minutes (for instance, /connectivity packetsSummary 3). The chat will display a comprehensive list of all outgoing server packets sorted from heaviest to lightest by packet type.

Export the Largest Packet to Logs

When a specific packet type appears abnormally large or triggers warnings in your console, locate the exact data structure:

1. Check the summary to find the problematic packet name.

2. Run the command /connectivity printpacket <PacketType>, replacing <PacketType> with the specific packet name shown in your summary.

3. Open your server directory and navigate to the logs folder.

4. Open latest.log in any text editor.

The command dumps the largest captured instance of that packet type directly into latest.log, allowing you to inspect oversized data and locate the origin of the network crash.