Tags
Creators
Details
0.1.1-beta.4
Compatibility
Required content
Changes
ℹ️ Some internal packages/classes were renamed or reorganized in this release. If you're a mod developer consuming MariesLib directly, check the Changed section below. End users: the override file layout changed but migrates automatically on load, just don't manually re-copy old override files over the new folders. Docs (API.md/ARCHITECTURE.md) are being updated to reflect these changes and will follow shortly.
Added
TooltipMessageRegistry/TooltipColorRegistry: configurable per-item and per-key tooltip colors and messages, with a two-tier override system (modpack config → datapack)ExcludedItemsRegistry: fully exclude specific items from tooltip/classification handlingCommunityTagResolutionStage/SuffixResolutionStage/KeywordResolutionStage: scanner signal logic extracted into a proper resolution-stage cascade- Recipe-inheritance scoring now falls back through component classification when direct tags/lookups come back empty
Changed
SourceClassificationRegistryoverride folder layout reorganized (overrides/Overrides/,overrides/Read_Me/): migrates automatically- Recipe-inheritance scores now merge into already-tagged items instead of being skipped
- Several internal classes split for maintainability: no public API changes
DeathNutritionBehaviorrenamed toRespawnValueBehavior(old accessors deprecated, still functional)
Fixed
SourceClassificationRegistryno longer crashes on malformed override entries: bad entries are now skipped and logged individually- Removed unreachable bundled README resources that could never actually load
- Removed dead-code
ExportResolverRegistry - Corrected
@ApiStatusvisibility tiers for several classes with real cross-mod consumers
Full details: CHANGELOG.md
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:VA0Qgf4B:PV8dTeZS"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:VA0Qgf4B:PV8dTeZS"
}


