Tags
Creators
Details
Licensed LGPL-3.0-only
Published 3 years ago
Updated 3 days ago
All versions
4.1.0+neoforge
Release
Assorted Lib 4.1.0 (NeoForge)3 days ago 6
Compatibility
Minecraft: Java Edition
26.2
Platform
NeoForge
Supported environments
Client and server
Changes
4.1.0
- Features added to biomes now go in the same order on both loaders, so one seed gives one world. A feature's place in its generation step decides the seed it is placed from, and the NeoForge side added them in registration order while Fabric sorts by the placed feature's id - identical terrain, every scattered feature somewhere else. NeoForge now sorts the same way.
- Added the instruction manual: an in-game book that any mod depending on Assorted Lib can add a
section to. Chapters are read from
assets/<modid>/manual/*.json, so a resource pack can extend or rewrite them. Right clicking a block, item or creature that has a page opens the book there, and the book shows two pages at once. - Recipe pages are drawn on the screen of the container that makes them, taken from that container's own texture. A container's fuel and tool slots are drawn too, cycling through what they accept.
- The whole manual is data: the book's own look, which mods are in the index, their chapters, which block, item or creature opens which page, and how each kind of recipe is drawn all come from resource packs, so a pack can move a slot, re-point a link, re-skin the book or rewrite a chapter without touching a mod.
- Holding the manual puts a green check mark beside the crosshair when whatever it is on has a page,
so a link is visible before it is clicked. Turn it off with
manual.showPageIndicator. - Right clicking an item frame with the manual opens the page of the item on display.
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:KkmxwW72:jNRs0dej"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:KkmxwW72:jNRs0dej"
}

