Links
Tags
Creators
Details
0.1
Compatibility
Changes
Prerelease. Some notes, from the README you should especially be aware of:
-
Current minor bug - default book tint
- When I grayscaled the book texture, I did it with imagemagick's
colorspace grayand that is not the same as what Mojang did. You can see that the "no-tint" texture is quite darker than the original vanilla texture. I don't see this as a critical issue because it allows the actual book dying to work.
- When I grayscaled the book texture, I did it with imagemagick's
-
Possible bug - signing dyed books
- If you dye a book and quill, then write in it, and sign it, I don't think the game will carry over the color and NBT data. I'm not sure yet.
-
Note: Written Book Textures
- The "Written Book" texture in the game's resource pack is actually not the same as a regular book or a book and quill. It's slightly darker. It's just hard to notice because of the glint. For now, the model is the same as the book so its a bit more consistent if you have another way to remove the glint, so you don't have to play eeny-meeny-miny-moe with it after you spent time finding what color tint you want for your book. Same goes for the book and quill.
-
The GUI: Do we want to change the 'red' color around it according to the dye?
- This is an interesting question! Because when you make a book cover, or technically 'dye' a book, you don't want to ruin the pages. If you were making a cover then it would go on top of the base book, which is kind of what this mod is doing in the background. So... I'm open to discussion.
-
Enchanted Books
- I feel like the only reason people would do this is client side, but there are probably texture packs or other mods that just show the enchantment on the texture so you dont have to struggle through a chest to find your specific enchantment.
-
Mod compatibility
- Other than maybe Patchouli, I haven't found a consistently up-to-date with vanilla Minecraft, a mod that contains a replica of the 'book' item. If I do, compatibility for this would be fun and easy, so if you find something, let me know (or make a pull request, contributions are welcome!)
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:5WCXfsFO:i6pYX8uB"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:5WCXfsFO:i6pYX8uB"
}

