All versions
1.0.1
Release
Collection Book 1.0.14 months ago 17
Compatibility
Minecraft: Java Edition
26.1.x
Platform
Fabric
Supported environments
Client and server
Changes
Changelog - 1.0.1
Performance Optimizations
- Optimized Inventory Scanning: Removed the periodic full inventory tick scan. Replaced it with an event-driven mixin on player inventory changes (
Inventory.setItem), capturing items obtained from picking up, crafting, and container transfers instantly. - Smart Biome & Structure Detection: Players are now tracked on chunk boundaries. Checking for biomes and structures now triggers only when a player crosses into a new chunk (16x16 blocks), eliminating heavy structure manager lookups every second.
- Registry Query Caching: Cached the heavy registry count loops in
RewardManager. The total collectibles count is computed once at startup and cleared/recalculated only during datapack reloads (/reload), resolving registry-loop lag spikes. - Entity Count Filter: Refined the mob collection logic to filter out non-living entities (arrows, boats, TNT, etc.), only targeting entities that extend
LivingEntity.
Network Optimizations
- Incremental Syncing: Full collection data is now synchronized only when the player joins the server.
- Lightweight Discovery Packets: Discovering new items, blocks, biomes, or mobs now sends a tiny incremental update packet rather than the entire collection history.
- Instant UI Opening: Opening the book now uses client-side cached data instantly, triggered by a lightweight signal packet, removing network latency.
Bug Fixes & Diagnostics
- Invalid Reward Warnings: Added console log warnings to notify server administrators if a configured milestone reward (such as a potion effect or item) does not exist in the registry.
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:qg6PEouJ:E8ZlSMQ1"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:qg6PEouJ:E8ZlSMQ1"
}

