CurseForge · Minecraft mod

Forge Config API Port

NeoForge's & Forge's config systems provided to other modding ecosystems. Designed for a multiloader architecture.

Choose a version Pick your version below, then grab the matching file.

Quick answer

Which Forge Config API Port release matches 1.21.3 Forge?

Updated last month

Best match for your filters [FORGE] [1.21.3] ForgeConfigAPIPort-v21.3.5

Game version 1.21.3

Loader Forge

Forge Config API Port [FORGE] [1.21.3] ForgeConfigAPIPort-v21.3.5 targets 1.21.3 with Forge. The project page does not say whether it belongs on the client. The project page does not say whether it belongs on the dedicated server. No extra mods listed for this file.

Where it goes

Is Forge Config API Port required on the client, server, or both?

The project page does not say whether it belongs on the client. The project page does not say whether it belongs on the dedicated server.

Client Source doesn’t say

Dedicated server Source doesn’t say

Loader for this release Forge

Required install it here Optional supported, not mandatory Not supported do not install here Source doesn’t say do not assume

The source does not explicitly classify this release as client-only or server-only.

Understand client and server requirements Read the Minecraft installation guide

What else does Forge Config API Port [FORGE] [1.21.3] ForgeConfigAPIPort-v21.3.5 need?

[FORGE] [1.21.3] ForgeConfigAPIPort-v21.3.5 on 1.21.3 Forge. Every mod below is checked against that same setup.

No extra mods listed for this file

This file does not list any required mods. Do not add a library just because a different file uses it.

Forge Config Screens [Archived] Optional for Forge Config API Port [FORGE] [1.21.3] ForgeConfigAPIPort-v21.3.5

optional

No matching file

We only count dependency files that match this setup. A file for another loader does not fill the gap.

Before you install it

Add Forge Config API Port without breaking your instance.

Built for Forge Config API Port [FORGE] [1.21.3] ForgeConfigAPIPort-v21.3.5 on 1.21.3 Forge. Pick another file and the loader, install side or required mods may change.

01
Stick to this file

Use [FORGE] [1.21.3] ForgeConfigAPIPort-v21.3.5. It targets 1.21.3 with Forge; another release may have different loader, side or dependency requirements.
02
Bring the mods it needs

This file does not list any required mods. Do not add a library just because a different file uses it.
03
Put it on the correct side

The project page does not say whether it belongs on the client. The project page does not say whether it belongs on the dedicated server.
04
Pick the file you checked

Use the “Get this file” button beside [FORGE] [1.21.3] ForgeConfigAPIPort-v21.3.5. It opens that exact file at the source.

About this project

What does Forge Config API Port add?

Forge Config API Port is a developer library that brings the Forge and NeoForge configuration systems to other mod loaders. It allows mods to use familiar Forge or NeoForge style configs across Fabric, Forge, and NeoForge without maintaining separate configuration implementations. 📦

This mod is intended for mod developers and as a dependency for supported mods. It does not allow Forge mods to run on Fabric, nor does it provide any form of general mod compatibility between loaders. 🔧

By preserving the original APIs, package names, and behavior as closely as possible, the mod makes it easier to maintain multiloader projects and share configuration code between platforms. This helps reduce platform-specific code and keeps configuration handling consistent across supported mod loaders. 🔄

📦 Configuration Library: Brings the Forge and NeoForge configuration systems to additional mod loaders while preserving their familiar APIs.
🔄 Cross Loader Config Support: Use Forge configs on Fabric and NeoForge, or NeoForge configs on Fabric and Forge.
🧩 No Refactoring Required: Preserves original package names and class names, allowing existing config implementations to be ported with little to no code changes.
🏗️ Built for Multiloader Projects: Define and register configs in a shared common module instead of maintaining separate platform specific implementations.
♻️ Shared Configuration Code: Keep a single configuration setup across supported loaders, reducing duplication and simplifying maintenance.
⚡ Native Where Available: No additional library is required on loaders where the chosen configuration system is already built in, keeping dependencies to a minimum for users.