
World Remembers Dear Diary
A personal Minecraft diary that turns your discoveries, deaths, victories, rare finds, and quiet little moments into a living record of your journey. Write your own notes, browse automatic memories, and let your world remember what happened.
Tags
Creators
Details
1.0.0
Compatibility
Changes
World Remembers: Dear Diary 1.0.0
The first full release of Dear Diary is here.
This version includes the complete personal diary system for Minecraft 1.21.1, with a book-style GUI, manual notes, automatic memories, favorites, filters, search, journey chapters, chat sharing, Markdown export, automatic backups, and support for both Fabric and NeoForge.
Dear Diary can remember important moments from vanilla gameplay, including discoveries, deaths, milestones, rare finds, boss fights, PvP victories, and other events that help turn a long playthrough into a readable story.
Highlights
- Personal diary for every player
- In-game book-style diary interface
- Manual entries and automatic memories
- Favorites, filters, sorting, and search
- Journey chapters for long worlds
- Share selected memories in chat
- Clickable coordinates inside diary entries
- Markdown export
- Automatic diary backups on logout
- Configurable automatic memories
- Vanilla PvP memories and milestones
- Full Russian and English localization
- Fabric and NeoForge support
Optional mod compatibility
Dear Diary also includes optional memory support for:
- The Twilight Forest
- The Aether
- Deeper and Darker
- Iron’s Spells ‘n Spellbooks
- L_Ender’s Cataclysm
- Create
- Farmer’s Delight
- Waystones
These mods are not required. Dear Diary works normally without them.
Supported versions
- Minecraft 1.21.1
- Fabric
- NeoForge
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:gEcL6MRh:Ljm7X1rb"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:gEcL6MRh:Ljm7X1rb"
}
