Links
Tags
Creators
Details
Licensed CC0-1.0
Published 6 months ago
Updated last month
All versions
1.1.0+26.1
Release
Interactive Enchanted Books 1.1.0+26.15 months ago 865
Compatibility
Minecraft: Java Edition
26.1.x
Platform
Fabric
Supported environments
Client-side
Client and server
Changes
Changelog for version 1.1.0
- Make particle emission based on the book count of nearby chiseled bookshelves
- If there are no books in nearby chiseled bookshelves, no particles will be emitted
- If there is at least one book, particles will be emitted
- With each additional book, the particles lifetime is increased
- Update comparator signal strengths
- New enchantment grouping fills the spectrum of signal strengths more thoroughly while also (hopefully) being future proof
- Add unique particle textures for each enchantment
- Add Enchantment Echo item to allow cloning of enchantments
- Combining an enchanted item with a book creates a Enchantment Echo without destroying the enchanted item
- Combining the Enchantment Echo with an Echo Shard crafts a Enchanted Book
- Enchantment Echos can be used in place of Enchanted Books in the other mod functions
- Add info buttons & panel in the book screen
- These panels show the particle requirements and the cloning of Enchanted Books using Enchantment Echos
- Update tooltip of Enchanted Books to indicate that they are openable
Changes fo integrating custom enchantments
- To realize the lifetime of particles based on the book count in nearby chiseled bookshelves, this book count is encoded in the z velocity of the particle
- To decode the book count and get the correct z velocity refer to EnchantParticle
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:pUwe9qcK:g6tGBRh5"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:pUwe9qcK:g6tGBRh5"
}

