Tags
Creators
Details
Licensed ARR
Published 4 years ago
Updated 17 hours ago
All versions
1.1.11-fabric-mc1.19.4
Release
SuperMartijn642's Core Lib 1.1.113 years ago 101
Compatibility
Minecraft: Java Edition
1.19.4
Platform
Fabric
Supported environments
Client and server
Changes
SuperMartijn642's Core Library 1.1.11
- Initialization of
TextureAtlaseswill no longer load theSheetsclass
SuperMartijn642's Core Library 1.1.10c
- Added compatibility for Quilt loader
SuperMartijn642's Core Library 1.1.10b
- Fixed crash when Plant In A Jar is installed
SuperMartijn642's Core Library 1.1.10a
- Item registry overrides will now also override the block->item map
SuperMartijn642's Core Library 1.1.10
RegistrationHandlerwill now register entries in the same order as they are submitted in
SuperMartijn642's Core Library 1.1.9c
- Registry overrides now replace values in vanilla fields
SuperMartijn642's Core Library 1.1.9b
- Improved registry overrides
SuperMartijn642's Core Library 1.1.9a
- Prevent crashes when scanning for
RegistryEntryAcceptorentries
SuperMartijn642's Core Library 1.1.9
- Fixed crash when
nullis passed intoBlockProperties#lootTableFrom
SuperMartijn642's Core Library 1.1.8
- Added
ResourceAggregatorto allow multiple data generators to write to the same file - All data generators will now generate before anything gets saved
- Entries in json files from data generators will now always generate in the same order
- Fixed
ClientUtils#getPartialTicksreturning the wrong value when the game is paused - Fixed
ItemProperties#toUnderlyingcausing an exception when durability is set - Fixed loot table handling in
BlockProperties
SuperMartijn642's Core Library 1.1.7
- Initial release of SuperMartijn642's Core Library for Fabric
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:rOUBggPv:NCOtuLHj"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:rOUBggPv:NCOtuLHj"
}

