1.3.0
Compatibility
Changes
The Archivist — v1.3.0 "The Cold Record" Changelog
Every entry has been audited. The records are no longer dramatic; they are factual.
Core System Changes
Narrative Re-Anchoring: We audited every in-game document, chat prompt, and whisper. The entity no longer speaks in generic creepypasta monologues. Its records now reflect the technical anatomy of Minecraft itself: chunk borders as suture marks from older saves, 400ms audio latency between footsteps, bedrock reflection anomalies, and JVM heap accumulation from broken blocks.
The archive does not write fiction. It documents what you leave behind.
Diagnostic & Signal Stability: Streamlined event execution and buffer cleanups across player observation loops. Fake event rollbacks (such as the experience drain and interface locks) now resolve through strict memory buffer restoration rather than noisy chat spam.
General Fixes
- Exit Blocker Rework: Removed placeholder emojis and melodramatic lines from the pause menu and window hook. When exit attempts are rejected, the client now reports low-level OS process locks and pending disk writes.
- Streamer & Dox Safety: Maintained full compatibility with
/archivist safeipacross all new behavioral logs and file fragments. - Crash & Screen Shake Polish: Cleaned up residual debug formatting in memory dump fragments and aligned camera glitch timings with actual client tickrates.
- Metadata & Descriptor Cleanup: Stripped out generic marketing blurbs and redundant descriptors across all internal mod manifests.
Encounters & Events
Rewritten Archival Records & Whispers: All story fragments and ambient chat events have been replaced with cold, clinical observation logs.
Notable revisions include:
- Ten Recovered Archival Logs: Physical books dislodged during mining, documenting abandoned seeds, cached player skins, and uncollected memory pointers.
- Diagnostic Bait: Dropped items are no longer framed as friendly rewards; they appear as confiscated evidence tagged with specimen numbers.
- Behavioral Tracking Whispers: The entity logs real player habits—hesitations before dark ravines, torch placement patterns, and inventory checking ticks.
- Incident Reports: Encrypted notes now generate as corrupted audit trails and thread hang dumps instead of placeholder text.
The Archivist does not need to threaten you. It simply keeps the log running.
The ink is already dry.
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:M0Lvvg6w:sjEkEyu9"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:M0Lvvg6w:sjEkEyu9"
}

