Tags
Creators
Details
Licensed MIT
Published last month
Updated yesterday
All versions
2.0-neoforge+26.1.1
Release
Simple Config Lib Neoforge 26.1.1 v2.06 days ago 1
Compatibility
Minecraft: Java Edition
26.1.1
Platform
NeoForge
Supported environments
Client-side
Server-side
Client and server
Changes
What's New
- New config sides — every config now declares which side owns it:
- CLIENT — stored and edited locally on the player's machine.
- SERVER — stored on the server and synced down to everyone who joins; only editable by operators.
- COMMON — edited locally like a client config, but synced to all players who join the server, so the option stays identical for the whole game while remaining editable outside a world.
- Config hub screen — when a mod registers more than one config, a hub screen is shown that lists all of them, each with its side label, and lets you open any one from a single settings entry.
- Custom config file name — a config can now set the on-disk file name independently of its internal name.
/simpleconfig reloadcommand — operators can reload SERVER and COMMON configs from disk at runtime without restarting the server; reloaded values are re-synced to all connected players, and onSave listeners now also fire on reload so dependent mods can react to file changes.- Networking utilities — new tools for mods that build on the library:
- A payload-creation utility: implement
SclPayloadon a record and register it once; built-in stream codecs coverString,Integer,BooleanandItemStack, and custom codecs can be added. - A
Network/NetworkClienthelper for sending payloads client→server, server→player, and server→all-players, working the same across Fabric, Forge and NeoForge and across game versions.
- A payload-creation utility: implement
Fixes
- Fix an issue where the keybind for legacy Forge could not be changed in the settings
- Fix a crash on legacy Forge when sending a network packet
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:PY2YT7QI:3ZnFZ7s8"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:PY2YT7QI:3ZnFZ7s8"
}

