Diagnosing Whether XXL Packets Is Actually Needed on Your Setup

Signs You Need It

The clearest symptom is a disconnect during the joining/loading screen with a message referencing packet size, payload size, or a maximum length being exceeded. This typically occurs right as the server syncs recipes, tags, or registry data to your client.

How to Confirm

1. Reproduce the disconnect and read the exact error in your client log.

2. Look for a line mentioning a packet or payload exceeding a size limit.

3. Note whether the disconnect happens consistently at the same point during join.

4. If the error mentions recipe sync or registry data, this mod is very likely the fix.

When It Isn't the Answer

If your disconnect mentions a timeout, a handshake failure, a mod mismatch, or a missing registry entry, the packet size limit is not your problem. Those are separate issues — version mismatches, missing mods, or network problems. Adding this mod won't help and may mask the real cause.

Testing Cleanly

Remove other packet-related mods before testing so you can attribute the fix correctly. Add this mod alone, restart, and reconnect. If the join succeeds, you've confirmed the cause. If it still fails, the log will point you toward the actual culprit.