Connectivity Mod FAQ

Run the mod's network stats command and see if it returns traffic data — if the command isn't recognized, the mod isn't loaded. You can also check your mods list or server log for the mod's startup message.

Use /connectivity packetsClient to see outgoing traffic from the client side. There's a matching server-side command for viewing traffic from the server's perspective.

DecoderException usually means a packet was malformed or exceeded the size the connection could handle during login or play. Connectivity Mod logs the offending packet and its source so you can identify which mod is sending bad data.

Ghost blocks are typically caused by oversized or dropped packets that the client never receives. Enable the mod's packet logging and oversized-packet warnings to find the source, then address the mod or payload causing the issue.

The mod is optional on both sides, so you can run it client-only or server-only. However, some fixes (like login timeout handling and malformed traffic protection) work best when installed on the server.

No, Connectivity Mod is not compatible with Timeoutout or XL packets mod. You'll need to remove one of them to avoid conflicts.

Turn on packet logging and advanced error logging through the mod's config or commands, then reproduce the issue. The logs will capture oversized packets and their sources, which you can attach to your report.

The mod is designed as a diagnostic and fix tool, so normal operation has minimal overhead. Packet logging and advanced error logging are more verbose, so disable them when you're not actively debugging.

Connectivity Mod includes login timeout fixes that extend or handle the login handshake more gracefully. Combined with its error logging, you can see whether a specific packet or mod is stalling the connection.

It means a mod is trying to send a packet bigger than the network can handle, which often causes kicks or ghost blocks. The mod logs which packet and source triggered it so you can track down the culprit.

Just install it and play normally — the mod works passively in the background, watching your connection and logging problems as they happen. To see what it's doing, open chat and run the client-side stats command to view your outgoing traffic.

It fixes and diagnoses network problems like login timeouts, play timeouts, DecoderException, oversized packets, and ghost blocks. It also logs suspicious or malformed traffic and gives you commands to inspect what's being sent and received.

No — it's optional on both sides, but you get the most benefit when it's on the server, since that's where most connection fixes and traffic monitoring happen. Client-side installs are still useful for packet logging and outgoing traffic stats.

Use the client-side packets command in chat to view outgoing traffic from your game. On the server side, similar commands show incoming traffic and per-player connection details.

Enable packet logging, then watch the log for warnings about oversized data — the mod reports the source of the packet so you can trace it back to the offending mod. Once you know which mod it is, you can remove or update it.

DecoderException usually means a packet was malformed or too large for the network to handle. Check the mod's log output for the packet source, then remove or update the mod responsible, or raise the packet size limit if the mod supports it.

No — it's not compatible with Timeoutout or the XL packets mod, since they overlap in what they try to fix. Pick one and remove the others to avoid conflicts.

No — Connectivity Mod is a Java Edition mod and does not run on Bedrock. Bedrock has its own networking stack and doesn't support Java mods.

The passive fixes have negligible overhead, but enabling detailed packet logging or advanced error logging can add noticeable cost on busy servers. Turn logging off when you're not actively debugging.

It helps by catching and logging the malformed or oversized packets that often cause ghost blocks, but it can't fix every cause. If ghost blocks persist, check the log for warnings and identify the mod sending bad data.