Better Compatibility Checker in All the Mods 10

Better Compatibility Checker is a small utility mod that changes how the multiplayer server list decides whether a server is compatible with your game. The default Forge check is not always accurate, and it can mark a server as incompatible even when it isn't. That confuses players who just want to join.^[1]

Instead, the mod compares the modpack project ID and the modpack version ID that the modpack author sets in a config file. If they match, you see a tick. If they don't, you see an X.^[1]

Who it is for

This one is mainly for modpack authors and server owners. Players mostly benefit from it without doing anything: when you add a server, the server list shows a tick if you and the server are running the same version, and an X if the server or client version is incompatible.^[1]

Configuration

The author opens bcc-common.toml in the config folder, sets the modpack name and the modpack version, and saves. The version has to be updated every time the modpack is updated. Otherwise the check compares stale data.^[1]

In this pack

The pack ships Better Compatibility Checker 21.1.8, using the NeoForge build of the mod. It was already included by pack version 2.25 or earlier.^[2]

Unverified The sources don't show any items, recipes or quests for this mod, and they don't show where it fits in the pack's progression or on the ATM Star path. It also isn't confirmed which modpack name and version values this pack sets in its config.

Better Compatibility Checker works quietly in the background and only shows up when you look at the multiplayer server list. There is nothing to set up on your side as a player.^[1]

What it does for you

The default Forge server compatibility check is not always accurate, so a server can show up as not compatible when it should be fine. This mod replaces that with a comparison of the modpack project ID and the modpack version ID, which the modpack author sets in a config file. You get a tick if they match and an X if they don't.^[1]

Hover over the server entry and the tooltip shows the server's modpack version next to yours. If they differ, it tells you that you are not running the same version of the modpack as the server.^[3]

First steps if you run a server or edit the pack

1. Open the bcc-common.toml file in the config folder. On Fabric the config is named bcc.json instead.^[1]
2. Set the modpack name and the modpack version, then save the file.^[1]
3. Each time you update the modpack, update the version in this config too.^[1]

Better Compatibility Checker is not a machine mod. The sources describe a small utility that changes how the server list decides whether your game matches a server, so there are no multiblocks, power, fluids or item handling to explain here.^[1]

What it actually does

The default Forge server compatibility check is not always accurate, and it can show a server as not compatible when a modpack player adds it. This mod fixes that by comparing the modpack project ID and the modpack version ID that the pack author sets in a config file.^[1]

If the values match, the server list shows a tick. If they do not match, it shows an X.^[1]

What you see in the server list

When your version matches the server, the tooltip lists the server's version and your client version. When it does not, the tooltip tells you that you are not running the same version of the modpack as the server, and then lists the server's version and your client version.^[3]

How it is configured in this pack

Everything lives in the common config file. The pack author sets the modpack name, the project ID and the modpack version, and has to update the version whenever the modpack is updated.^[1][4]

• general.modpackName is set to "All the Mods 10" in this pack.^[4]
• general.modpackProjectID is set to 925200 in this pack.^[4]
• general.modpackVersion is set to 8.1 in this pack.^[4]
• general.useMetadata is set to false in this pack.^[4]

If the server doesn't have the mod

If the mod is on the client but not on the server, it first checks whether the data it needs is set. If that data is not set, it falls back to the default Forge implementation.^[1]

Better Compatibility Checker has only a handful of options, and they all live in bcc-common.toml in the config folder. The mod replaces the default Forge server compatibility check. It compares the modpack project ID and modpack version that the pack author set in that file, then shows a tick if they match or an X if they don't.^[1]

How this pack sets them

• general.modpackName is set to the pack's own name.^[4]
• general.modpackProjectID is 925200. This is the project ID the check compares between client and server.^[1][4]
• general.modpackVersion is 8.1. This is the version the check compares.^[1][4]
• general.useMetadata is set to false.^[4]

Unverified The sources don't say what useMetadata does, and they don't show the mod's default values. So I can't confirm which of these settings the pack changed from the mod default.

Better Compatibility Checker has only moved forward through version bumps in the pack changelogs I have. All the Mods 10 8.1 ships version 21.1.8, and the mod was already in the pack by All the Mods 10 2.25 or earlier.^[2]

Pack updates that changed the version

• All the Mods 10 2.37: updated from 21.1.0 to 21.1.2.^[5]
• All the Mods 10 2.40: updated from 21.1.2 to 21.1.3.^[6]
• All the Mods 10 4.13: updated from 21.1.3 to 21.1.4.^[7]
• All the Mods 10 4.15: updated from 21.1.4 to 21.1.5.^[8]
• All the Mods 10 5.5: updated from 21.1.7 to 21.1.8, the version that 8.1 still uses.^[2][9]

The changelogs only record that the version changed. They don't say which pack release moved the mod from 21.1.5 to 21.1.7.^[8][9]

Unverified What actually changed inside the mod in each of these versions (fixes, features or behavior) is unverified, because no mod changelogs are stored for the shipped jars.