All versions
5.0.7
Release
neoforge-runiclib-1.21.1-5.0.72 months ago 21.9K
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
Version Release v5.0.7 MC-1.21.1
Misc Additions
- Added
RLTrade, which allows registering villager trades to be registered in the common package instead per-modloader- Trades are registered using
RLServices.REGISTRY.registerVillagerTrade()for Villager trades, andRLServices.REGISTRY.registerWanderingTrade()for Wandering Trader trades- Each one requires a
Supplierthat creates aRLTrade.ProfessionandRLTrade.Wandering, depending on what you're using
- Each one requires a
- Also contains a shortcut method to register custom structure locator maps for convenience
- Code provided by/based on VectorLib's
VectorTradeby @TheArtyrian (GitHub)
- Trades are registered using
Fixes
- Fixed menu registration on Fabric
- Fixed a registration issue with NeoForge that could potentially cause a null return if called too early
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:mk0Htq87:tk5EQpUG"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:mk0Htq87:tk5EQpUG"
}

