1.0.0
Compatibility
Changes
Finished, and staying that way.
Nothing here is new. 1.0.0 is a promise about what already exists, made now that the two things it was waiting on have both happened: NeoForge 26.2 has left beta, and the mod has been played rather than only built.
What 1.0.0 commits to
- Your worlds keep working. Villager names and everything a villager remembers about you keep their stored shape. Fields may be added later — they have defaults — but nothing already saved will stop being read.
- Settings keep their names. Renaming a config key silently resets it for whoever had tuned it, so they stay put.
- The escape hatch stays.
dialogueEnabled = falsewill always restore ordinary vanilla trading, leaving the mod installed but dormant.
Breaking any of those would be 2.0.0.
Not covered: the network protocol between client and server. It is internal, it is already versioned, and it turns a version mismatch into a clean refusal to connect rather than a subtle misreading. Expect it to keep changing, and expect clients and servers to need matching versions.
Changed
- Now built against NeoForge
26.2.0.62, the stable line, up from26.2.0.48-beta. Requires 26.2.0.62 or newer. - The mod icon appears in the Mods list again. NeoForge split the old
logoFilesetting into a separate icon and banner, and only the banner kept the old name working — so the icon had quietly stopped being shown.
Notes
- No protocol change; 1.0.0 talks to 0.13.0 clients and servers.
- Requires Minecraft 26.2 and NeoForge 26.2.0.62 or newer.
- Existing worlds need nothing.
- Still no mixins.
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:ccEZGZf7:PInYTvBa"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ccEZGZf7:PInYTvBa"
}

