Links
Tags
Creators
Details
v1.0.1
Compatibility
Changes
Librarian Insight 1.0.1
This update focuses on faster lectern updates, improved reliability after loading chunks, more vanilla-like interactions, and direct access to Librarian trading.
Changes
-
Faster Lectern Trade Display
- Librarian trade information now appears much faster after a villager claims a lectern.
- Removed the noticeable 5–10 second delay that could occur before the enchanted book appeared.
-
Improved Chunk & World Loading
- Lectern trade displays now restore properly when loading a world or returning to previously unloaded chunks.
- Players should no longer need to walk directly next to a lectern before its trade information appears.
- Existing Librarian/lectern associations are restored and refreshed automatically.
-
Trade Directly From the Lectern
- Added the ability to access trading directly through the Librarian Insight lectern interface.
- Trading uses Minecraft's normal merchant system, preserving vanilla prices, stock, XP, trade uses, and other mechanics.
-
More Vanilla-Like Lectern Interaction
- The player's hand now swings when right-clicking a lectern to open Librarian Insight.
- The Librarian Insight menu can now be closed using the player's Inventory key, just like vanilla interfaces.
- Custom inventory keybinds are respected.
Fixes & Improvements
- Improved responsiveness of Librarian/lectern association updates.
- Improved restoration of cached trade information.
- Preserved stale-data cleanup when lecterns are broken or reassigned.
- Existing rendering, pricing, themes, status information, commands, and trade calculations remain unchanged.
Librarian Insight does not modify villager trades or trading mechanics — these features provide faster and more convenient access to vanilla information and trading.
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:QwkQ5kWH:q59vhqyn"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:QwkQ5kWH:q59vhqyn"
}

