ModsFinder

bad packets

by badasintended

With Bad Packets, a Fabric client can exchange packets with a Forge server, and the reverse, but only when each mod calls its API to send them.

FabricForgeNeoForgeQuiltClient or server, optionalApache License 2.0Open source1.18.2 – 26.2

What it does

The library carries messages between the different modding platforms, so a packet sent by a Fabric build can reach a Forge build and the other way round. It does not make mods that ship for several loaders compatible on its own: the developer has to call the Bad Packets API to send each packet. Game object id sync is not handled, which the author calls impractical to support.

Key features

  1. Cross-platform packets

    Packets can travel between builds of one mod that run on different loaders, once the mod sends them through the API.

  2. Developer API

    Mod authors call the Bad Packets API to register and send their own messages, which keeps the protocol under their control.

  3. Shared dependency

    Other mods that need cross-platform messaging can depend on this library instead of writing their own transport.

Compatibility

Latest build for each game version and loader.

26.x4 of 4 versions with builds
26.2fabric-0.12.2forge-0.12.2neo-0.12.2fabric-0.12.2
26.1.2fabric-0.12.2forge-0.12.2neo-0.12.2fabric-0.12.2
26.1.1fabric-0.12.2forge-0.12.2neo-0.12.2fabric-0.12.2
26.1fabric-0.12.2forge-0.12.2neo-0.12.2fabric-0.12.2
1.21.x12 of 12 versions with builds
1.21.11fabric-0.11.2forge-0.11.2neo-0.11.2fabric-0.11.2
1.21.10fabric-0.10.2forge-0.10.2neo-0.10.2fabric-0.10.2
1.21.9fabric-0.10.2forge-0.10.2neo-0.10.2fabric-0.10.2
1.21.8fabric-0.9.0forge-0.9.0neo-0.9.0fabric-0.9.0
1.21.7fabric-0.9.0forge-0.9.0neo-0.9.0fabric-0.9.0
1.21.6fabric-0.9.0forge-0.9.0neo-0.9.0fabric-0.9.0
1.21.5fabric-0.8.2forge-0.8.2neo-0.8.2fabric-0.8.2
1.21.4fabric-0.8.2forge-0.8.2neo-0.8.2fabric-0.8.2
1.21.3fabric-0.8.2forge-0.8.2neo-0.8.2fabric-0.8.2
1.21.2fabric-0.8.2forge-0.8.2neo-0.8.2fabric-0.8.2
1.21.1fabric-0.8.2forge-0.8.2neo-0.8.2fabric-0.8.2
1.21fabric-0.8.2forge-0.8.2neo-0.8.2fabric-0.8.2
1.20.x7 of 7 versions with builds
1.19.x5 of 5 versions with builds
1.18.x1 of 1 version with builds
ReleaseBetaAlphaNot available

This mod also publishes snapshot builds. Snapshots are not shown in the matrix.

Required by 8 mods

WTHIT1.16.2 – 26.2PvP Flag1.19.2 – 1.21.1Better Harvesting1.19 – 1.20.2NekoMusic Client1.21 – 26.1.2WTHIT: Small Ships Plugin1.20.1MoeMusic1.18.2 – 26.3

Questions

Does Bad Packets make all multi-loader mods compatible?

No. A mod must use the Bad Packets API to send its packets; the library does not change mods that do not call it.

Is Bad Packets needed on both sides?

Either side can run it, and neither needs it. It is only needed where a mod that uses it runs.

In the catalog

bad packets is one of 3,514 Library mods on ModsFinder, and one of 2,348 Library mods for Fabric. 13,894 mods support Minecraft 26.2.

Library mods3,514Fabric modsMods for 26.213,894

More from badasintended

All projects
WTHIT1.16.2 – 26.2Megane: Fabric1.18.2 – 1.20.1WTHIT Harvestability1.18.2 – 1.20.1slotlink1.16.4 – 1.19.4Megane: Forge1.19.2 – 1.20.1conveniently placed armor slots1.16 – 1.19.2

Similar mods

Fabric API1.14 – 26.3Cloth Config API1.14 – 26.3YetAnotherConfigLib (YACL)1.19 – 26.3Architectury API1.16.5 – 26.3Just Enough Items (JEI)1.8 – 26.3Geckolib1.12.2 – 26.3

What the author says

This means a Fabric client version of a mod that uses Bad Packets can send a packet to a server that uses the Forge version and vice versa. This mod DOES NOT magically make all mods that have versions for different platforms to be compatible with each other, the developer needs to use BP's API to send its packet…
badasintended, on the Modrinth page

Official listing

Owner
badasintended
Published
2022-04-21
Updated on Modrinth
2026-04-05
Facts verified
2026-10-15

Tags

Library
Open on ModrinthCompare