What Forge Config API Port works with.
| Platform | Java Edition |
|---|---|
| Loaders | Fabric, Forge, NeoForge |
| Minecraft versions | 1.16.5, 1.18.2, 1.19.4, 1.20.1, 1.20.6, 1.21.1, 1.21.8, 1.21.11, 26.1, 26.2 |
| Environment | Client, Server |
Forge Config API Port brings Forge and NeoForge's built-in config screen system to Fabric, so a mod can define its settings once and get a working config menu on every loader it ships for. It installs on Fabric, Forge, and NeoForge, covers Minecraft 1.16 through the current 26.2 drop, and runs on both the client and the server since most of what it adds is compile-time API rather than a gameplay change.
What Forge Config API Port does
Minecraft Forge and NeoForge ship a config system with an in-game screen built in. Fabric and Quilt never got an equivalent, so mod authors targeting more than one loader from a shared codebase had no common way to expose settings. Forge Config API Port copies that Forge and NeoForge config code, packages it as a standalone library, and ships matching builds for Fabric, Forge, and NeoForge, so a multiloader mod's config code path stays the same everywhere. That is also why a mod update can suddenly list this as a required dependency: the mod moved its settings to the shared Forge-style config API instead of a loader-specific one, and needs this port to make that API available on Fabric.
Supported loaders and Minecraft versions
- Fabric: current build 26.2.1 for Minecraft 26.2
- Forge: current build 26.2.1 for Minecraft 26.2
- NeoForge: current build 26.2.1 for Minecraft 26.2
- Project history reaches back to Minecraft 1.16, with builds published for most releases since
All three loader builds are on the same 26.2.1 release right now, so there is no version gap between them at the moment. That has not always been true for every past release, so double check the loader and version filter on the download page before grabbing a file for an older Minecraft version.
Dependencies and client or server side
On Fabric, Forge Config API Port requires Fabric API to load. Mod Menu is listed as optional, but on Fabric you need it to actually open a mod's config screen from the pause menu; without Mod Menu the config API still works, a depending mod just has no in-game entry point to reach it. Forge and NeoForge already ship Fabric API's equivalent natively, so neither needs an extra dependency to run this. Client and server sides are both marked optional, matching what you would expect from an API library: it does nothing on its own and only matters where a dependent mod actually uses it.
Installing Forge Config API Port on Fabric
- 1.Install Fabric Loader for your target Minecraft version. The Fabric install guide covers this step by step.
- 2.Download Fabric API and the Fabric build of Forge Config API Port for the same Minecraft version from Modrinth.
- 3.Optionally add Mod Menu if you want an in-game button to open the config screens this library powers.
- 4.Drop all three jars into your instance's mods folder and launch.
Downloading and installing Forge Config API Port
Questions about Forge Config API Port.
5 questions
What does Forge Config API Port do?
It ports Forge and NeoForge's built-in config screen system to other mod loaders, mainly Fabric. Instead of every mod loader needing its own config UI code, a multiloader mod can write its settings once against this shared API and get a working in-game config screen on Fabric, Forge, and NeoForge alike.
Why does a mod suddenly require Forge Config API Port as a dependency?
The mod likely moved its settings to the shared Forge-style config API so the same config code works across every loader it supports, instead of maintaining separate config systems per loader. On Fabric, that shared API does not exist natively, so the mod needs Forge Config API Port installed to provide it.
Does Forge Config API Port work with Fabric?
Yes. Fabric is one of its three supported loaders alongside Forge and NeoForge, and it is the loader this port matters most for, since Fabric has no built-in equivalent to Forge's config screen system. Fabric API is a required dependency for the Fabric build.
Do I need Mod Menu to use Forge Config API Port on Fabric?
Not to run it, but you need Mod Menu to open a config screen from the pause menu on Fabric. Mod Menu is marked as an optional dependency because the config API still functions without it. A dependent mod without any other settings menu will have no visible way to reach its config screen unless Mod Menu is installed.
Which Minecraft version does Forge Config API Port support?
Builds go back to Minecraft 1.16 and continue through the current 26.2 release, with separate downloads for each supported version. As of the latest release, Fabric, Forge, and NeoForge are all on the same 26.2.1 build for Minecraft 26.2, so there is currently no version gap between loaders.
