All versions
1.0.2
Release
Collection Book 1.0.24 months ago 11
Compatibility
Minecraft: Java Edition
26.1.x
Platform
Fabric
Supported environments
Client and server
Required content
Any compatible version
Changes
Changelog - 1.0.2
Performance Optimizations (Client)
- GUI Render Cache: Cached all item and block icon
ItemStackinstances insideEntryData. The icons are now created once when a tab is loaded instead of instantiating hundreds ofItemStackobjects every frame during screen rendering. - Details Panel Caching: Title, wrapped description text, and discovery status components are now cached and updated only when the selected or hovered item changes, significantly reducing Garbage Collector churn and improving FPS.
- Static Assets Cache: Moved category and reward icons to cached maps/arrays to prevent redundant instantiations.
Customization & Modpack Support
- Dynamic Rarities & Blacklists: Moved all hardcoded rarity mappings (Legendary, Epic, Rare) and block/item blacklists from Java code (
RarityRegistry) into thecollection_book.jsonconfiguration file. - Config-driven Checks: Rewrote
RarityRegistryto dynamically load values from the configuration file, allowing server admins and modpack creators to customize rarity assignments and blacklisted items/blocks directly without recompiling the mod. - Client Count Sync: Updated client-side calculations for mob totals to filter non-living entities, matching the server's optimized count logic.
- Unobtainable Items Filter: Added default blacklist exclusions for survival-unobtainable blocks and items (e.g. Bedrock, Barrier blocks, Light blocks, Command blocks, Spawners, Jigsaws, Structure blocks, Debug sticks, and End Portal frames) to keep survival mode collections clean and achievable.
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:RC6FS22d"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:qg6PEouJ:RC6FS22d"
}

