All versions
1.0.0
Release
Personal Chronicles 1.0.0last month 24
Uploaded by
Compatibility
Minecraft: Java Edition
26.2
Platform
Fabric
Supported environments
Server-side
Singleplayer
Required content
Unavailable version
Changes
Changelog
[1.0.0] - 2026-07-04
Added
- Added personal journey logs for every player.
- Added individual player profile files.
- Added readable
.txtoutput for player memories. - Added automatic file creation on first join.
- Added journey log folder:
config/personal-chronicles/journals/
- Added profile folder:
config/personal-chronicles/profiles/
- Added configuration file:
config/personal-chronicles/personal-chronicles.properties
- Added join and leave logging.
- Added death logging with cause and coordinates.
- Added Nether visit tracking.
- Added End visit tracking.
- Added important item milestone tracking.
- Added selected mob kill milestone tracking.
- Added profile auto-updating.
- Added Russian and English language support.
- Added in-game language switching.
- Added commands:
/pchronicles book/pchronicles book <player>/pchronicles journal <player>/pchronicles profile <player>/pchronicles save/pchronicles reload/pchronicles language ru/pchronicles language en
- Added full command alias:
/personalchronicles
Changed
- Built for Minecraft 26.2.
- Built for Fabric Loader 0.19.3.
- Built for Fabric API 0.154.0+26.2.
- Updated the project to Java 25.
- Designed as a server-side only Fabric mod.
- Designed around readable long-term memory files instead of raw statistics only.
Notes
- This mod is server-side only.
- Clients do not need to install the mod.
- Best suited for SMPs, private servers, friend groups, and long-term survival worlds.
- Works well alongside World Chronicles: World Chronicles records the shared server story, while Personal Chronicles records each player's personal journey.
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:VlKicybR:EAXbZ6j8"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:VlKicybR:EAXbZ6j8"
}
