1.3.9+26.2
Compatibility
Changes
1.3.9+26.2
This is a technical/maintenance release: no new features, focused entirely on fixing a serious data-integrity bug in the World Journal and finishing the in-game command support that had been requested but never actually shipped.
Fixed
- World Journal entries mixing between different worlds (major bug). On this Minecraft
version, the way the game reports a singleplayer world's own save folder could resolve to the
same generic path for every world instead of that world's actual folder. As a result, every
singleplayer world ended up sharing one single journal file instead of getting its own — so a
brand-new world could show deaths, trades, advancements or notes that actually happened in a
completely different world, and deleting a world and creating a new one with the same name
could resurrect the deleted world's entries.
- Each world's journal is now tied to its own save folder through a small hidden marker file stored inside that folder, completely independent of the folder's name — this can't reoccur, even if you reuse an old world's name.
- If you had already been affected, opening the singleplayer world list now shows a one-time recovery screen (it keeps appearing until you act on it) offering two choices: delete the old shared file and let every world start with a clean journal, or pick which of your worlds should receive the old file's recovered entries.
/journalcommands now actually exist. These had been asked for previously but never wired into the mod:/journal add <text>— logs a manual entry on the current in-game day, without opening the book screen/journal removeday <day>— shows how many entries exist for that day; running/journal removeday <day> confirmdeletes all of them/journal clear— shows a warning about what's about to happen; running/journal clear confirmpermanently wipes the current world's entire journal
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:DinbWefJ:iKTXRRLG"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:DinbWefJ:iKTXRRLG"
}

