Better Compatibility Checker in FTB Evolution 2
FTB Evolution 2 1.4.0 ships version 26.1.2.1 · First seen in 1.0.2
Better Compatibility Checker is a mod in FTB Evolution 2 1.4.0, where it is version 26.1.2.1. Changes the default server compatibility check to compare modpack versions (Summary from the mod's Modrinth page.)
Better Compatibility Checker guide for FTB Evolution 2
Last verified for FTB Evolution 2 v1.4.0 on Oct 13, 2026 · text last changed Oct 13, 2026
Also applies to:All the Mods 10 2.21 to 8.3All the Mods 10: To the Sky 1.9 to 2.1.0All the Mods 11 0.1.0 to 0.12.0-betaAll the Mons 0.3.0-beta to 1.3.0FTB Skies 2 1.0.1 to 1.24.0FTB Skies 2: Aero 1.0.3 to 1.10.0FTB StoneBlock 4 1.1.1 to 1.23.0
- Sections
- 4
3 sections are written for this pack; 1 is shared from another pack's guide.
Every recipe and number here was checked against FTB Evolution 2 1.4.0, read from the running game on Oct 17, 2026.
What is Better Compatibility Checker?
3 parts
Same as in the All the Mods 10 8.1 guide
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.
How do you get started with Better Compatibility Checker?
2 parts
Better Compatibility Checker is a different kind of mod from most in the pack. It is about the multiplayer server list, not about building or crafting. It replaces the default Forge server compatibility check with a comparison of modpack versions, so a server only shows as incompatible when the pack versions really differ.[1]
What you will see in game
When you add a server, the mod shows a tick if you and the server run the same modpack version, and an X if you do not. Hovering over the entry shows the server's version next to yours. If the versions differ, the tooltip tells you that you are not running the same version of the modpack as the server.[1][3]
The settings in this pack
The mod reads its settings from config/bcc-common.json, and the pack ships it already filled in. The project page mentions a bcc-common.toml, but in this pack the file is the JSON one. Nothing needs setting up on your side, but here is what is in it:[1][4]
- modpackName.value holds the pack's own name. Its comment in the file reads "The name of the modpack".[4]
- modpackVersion.value is set to 1.0.0. Its comment in the file reads "The version of the modpack".[4]
- useMetadata.value is false. When enabled, it makes the mod use the metadata.json to determine the modpack version. The file's own comment says to only enable it if you know what you are doing.[4]
If the data the mod needs is not set, or the mod is missing on the server but present on the client, it falls back to the default Forge check.[1]
How does Better Compatibility Checker work?
3 parts
Better Compatibility Checker has no machines, multiblocks or power to manage. It does one job: it changes the default server compatibility check in the multiplayer list so that it compares modpack versions instead.[1]
How the check works
The default Forge compatibility checker is not always accurate, and it can show a server as not compatible when you add it. This mod fixes that for modpacks. It compares the modpack project ID and modpack version ID that the pack author set in a config file. You see a tick if they match and an X if they do not.[1]
The tooltip shows both versions, one labelled Server and one labelled Client (You). If they differ, it also tells you that you are not running the same version of the modpack as the server.[3]
What the pack sets in the config
The pack's settings live in config/bcc-common.json. These are the options it sets:[4]
- modpackName.value is described as the name of the modpack. In this pack it is set to the pack's own name.[4]
- modpackVersion.value is described as the version of the modpack. In this pack it is set to "1.0.0".[4]
- useMetadata.value makes the mod use the metadata.json to determine the modpack version. In this pack it is false, and the config comment says to only enable it if you know what you are doing.[4]
When the server does not have the data
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 check.[1]
Which Better Compatibility Checker config options matter?
1 part
Better Compatibility Checker is configured in one file in this pack, config/bcc-common.json. When you add a server, the mod compares the modpack name and version set there and shows a tick if they match or an X if they do not.[1][4]
What this pack sets
- modpackName.value is set to the pack's own name. The file describes it as the name of the modpack.[4]
- modpackVersion.value is set to "1.0.0". The file describes it as the version of the modpack, and the mod compares this version to decide between the tick and the X.[1][4]
- useMetadata.value is set to false, so the mod does not use metadata.json to determine the modpack version. The file's own comment says to only enable this if you know what you are doing.[4]
Sources
- Better Compatibility Checker project page (modrinth) · official mod data
- All the Mods 10 8.1 mod list · pack file
- bcc names, screen text and descriptions (English lang file) · official mod data
- FTB Evolution 2 1.1.0 config: config/bcc-common.json · pack file
Where this guide comes from
Written from what FTB Evolution 2 itself ships: its files and recipes, the in-game guidebooks and the mods' own pages. Every statement links to the source it came from, and the numbers are checked against the pack before publishing.
Guide last verified Oct 13, 2026.
Report wrong info
Version in each release
9 releases, first in 1.0.2
| FTB Evolution 2 | Version | Jar | Where it came from |
|---|---|---|---|
| 1.4.0 Oct 17, 2026 | 26.1.2.1 | better-compatability-checker-neoforge-26.1.2.1.jar | From the published release |
| 1.3.2 Oct 16, 2026 | 26.1.2.1 | better-compatability-checker-neoforge-26.1.2.1.jar | From the published release |
| 1.3.1 Oct 15, 2026 | 26.1.2.1 | better-compatability-checker-neoforge-26.1.2.1.jar | From the published release |
| 1.3.0 Oct 14, 2026 | 26.1.2.1 | better-compatability-checker-neoforge-26.1.2.1.jar | From the published release |
| 1.2.2 Oct 13, 2026 | 26.1.2.1 | better-compatability-checker-neoforge-26.1.2.1.jar | From the published release |
| 1.2.1 Oct 12, 2026 | 26.1.2.1 | better-compatability-checker-neoforge-26.1.2.1.jar | From the published release |
| 1.2.0 Oct 12, 2026 | 26.1.2.1 | better-compatability-checker-neoforge-26.1.2.1.jar | From the published release |
| 1.1.0 Oct 10, 2026 | 26.1.2.1 | better-compatability-checker-neoforge-26.1.2.1.jar | From the published release |
| 1.0.2 Oct 8, 2026 | 26.1.2.1 | better-compatability-checker-neoforge-26.1.2.1.jar | From the published release |
"From pack files" means the list came from the pack's own files; "from the published release" means ForgeBase read the jars of the release itself.
Items and blocks
We can't match this mod to the pack's item list: it registers as bcc, and the pack's recipe dump has nothing under that name. That means we found nothing, not that the mod adds nothing. Search the item browser
Config options (how FTB Evolution 2 sets them)
6 settings this pack ships for the mod. We don't have the mod's own defaults to compare them against yet.
Show settings
| Setting | FTB Evolution 2 value |
|---|---|
modpackName.comments config/bcc-common.json | ["The name of the modpack"] |
modpackName.value config/bcc-common.json | FTB Evolution 2 |
modpackVersion.comments config/bcc-common.json | ["The version of the modpack"] |
modpackVersion.value config/bcc-common.json | 1.0.0 |
useMetadata.comments config/bcc-common.json | ["Use the metadata.json to determine the modpack version","ONLY ENABLE THIS IF YOU KNOW WHAT YOU ARE DOING"] |
useMetadata.value config/bcc-common.json | true |
Comments and tips
Loading comments...