Contents (4)
You installed Bad Packets, the dependent mod loads, but something still breaks: disconnects, desyncs, or packet errors in the log. Work through these checks.
Verify Both Sides Match
The most common cause is a mismatch between client and server. Bad Packets needs to be present on both, and the dependent mod needs to be present on both, ideally at matching versions. If the server runs one version and the client another, packet handling can fail even though the game launches.
Check the Dependent Mod's Requirements
Bad Packets is only the transport layer. The mod using it still has its own version requirements. Confirm that mod supports your game version and loader. A mod built for a different game version may load but fail once packets start flowing.
Read the Log Carefully
Look for lines mentioning the dependent mod or Bad Packets during connection. Errors there usually point to the real culprit: a version mismatch, a missing side, or a mod that only partially integrated the API.
When to Stop Troubleshooting
If the dependent mod was never designed for cross-loader use, no amount of Bad Packets configuration will fix it. In that case, switch to a build of that mod made for your loader, or drop it from the pack.
