Forge Config API Port Mod FAQ

It's a background library, not a feature mod, so you won't see a menu or items from it. It lets other mods that were built around Forge's config system load and save their config files on your mod loader, which is why those mods' options work at all.

Use the config button on the mod's entry in your mod list menu, or the config key/button the mod itself adds. Forge Config API Port provides the config screen framework, but the mod still has to register its own config screen for you to open it.

They live in the config folder inside your game directory, usually as .toml files named after the mod. Some mods split settings into separate files for common, client, and server options.

The mod probably hasn't registered a config screen, or the config file failed to load because of a syntax error. Check the mod's config file for typos or invalid values, and look at the log for a parsing error mentioning that mod.

Yes, the .toml files are plain text and can be edited in any text editor. Close the game first, make your changes, then save, or the game may overwrite your edits on exit.

This usually means the file is being regenerated because it failed to parse, or the mod is writing defaults on startup. Check the log for a config error and make sure you're not editing the file while the game is running.

Yes, it should be installed on both sides, since configs can be server-side, client-side, or common. If it's missing on one side, mods depending on it may fail to load or their configs won't sync.

No, they serve different purposes and generally coexist fine. Forge Config API Port handles the config backend, while mods like Cloth Config or Configured provide the screen you see in-game.

It has negligible impact on gameplay performance since it only reads and writes config files. Any startup delay you notice is more likely from the mods using it than from the library itself.

Yes, config files are portable as long as you both run the same mod and version. Copy the relevant .toml files from your config folder into theirs, but avoid sharing files that contain personal paths or server-specific values.

It is a compatibility library that brings the Forge and NeoForge configuration systems to other mod loaders. It lets mods use Forge or NeoForge style configs across Fabric, Forge, and NeoForge without maintaining separate configuration implementations.

It supports Fabric, Forge, and NeoForge. On Forge and NeoForge no additional library is required because those config systems are already built in.

The Modrinth project page lists Minecraft 1.21.11, 26.1, 26.1.1, 26.1.2, 26.2, and 26.3. The wiki summary lists Minecraft 26.3 – 26.4 with NeoForge.

No. It is a developer library for configuration systems and does not add any items or blocks.

No. It does not allow Forge mods to run on Fabric, and it does not provide general mod compatibility between loaders. Its purpose is only to bring the Forge and NeoForge config systems to other loaders.

No. It is only needed on loaders like Fabric where the chosen configuration system is not already built in. On Forge and NeoForge the config systems are native, so no additional library is required.

Yes. On Fabric it requires Fabric API to be installed.

Yes. It is required on both the client and the server.

No. It preserves the original package names and class names, so existing config implementations can be ported with little to no code changes.

It is a library. It is intended for mod developers and as a dependency for supported mods, and it is categorized as an API and Library.