MariesLib

!(https://cdn.modrinth.com/data/cached_images/6ff9551d7494d4f1f52a4428de2a2167786ee548.png)

# MariesLib

> I wanted to pull out all the reusable code from Nourished and place it in one library. MariesLib is a shared library behind Marie's mods. > > It handles the hard problems auto-classifying thousands of items from modded content, three-tier compat with modpack overrides, player tracking with memory and decay, datapack tooling with validation, a generic dynamic-UI framework, and more so consuming mods can focus on gameplay.

MariesLib 0. 1. 1-beta is still under development.

Development is ongoing as more systems are being refined, expanded, and stabilized. Recent work has focused on a full dynamic-UI editing framework (drag/resize, cross-component snapping, group edit mode, a slider-based config panel, and a pluggable command-center screen), a generic milestone system that works against any tracked value, and honest classification-confidence fixes across the scanner and runtime resolver.

More updates will be shared as development progresses.

> Version 0. 1. 1-beta. 4 is split into four modules: > > `marie-core`: classification, tracking, compat, registries, config, milestones > `marie-commands`: command/KubeJS integration > `marie-resources`: datapack tooling and validation > `marie-ui`: the dynamic UI/editing framework > > This modular structure keeps maintenance manageable and lets individual systems evolve independently.

## Community

(https://discord.gg/EZnFJsfQup)

Questions, suggestions, and development discussions are welcome. A lot of the bug fixes and new features came from here.

## Do you need to install this?

Yes: if you use a mod that depends on it.

> Mod loaders and launchers that resolve dependencies automatically should pull MariesLib in for you. If a Marie mod fails to load, check that MariesLib is present and up to date.

### For mod developers

Every Marie mod requires MariesLib as a separate mod on the classpath. There is no JarJar bundling. Declare `marieslib` as a required dependency and wire your runtime through `MarieContext` at bootstrap.

## What it provides

| System | What it does | |---|---| | Classification | Runtime source resolution, scanner tooling, and classification traces | | Compat discovery | Three-tier compatibility registry with modpack overrides | | Registry lifecycle | Lifecycle-aware registries with snapshots, freeze/reset, and reload support | | Tracking & values | Player value tracking, memory windows, decay, and effect hooks | | Generic accumulator tracking | Arbitrary numeric trackers (`MarieTracking`): daily/weekly/monthly periods with retained history, usable for anything a consuming mod wants to count | | Milestones | One-time achievements, either against nutrient-style intake or against any `MarieTracking` tracker, registerable via Java, datapack JSON, or KubeJS | | Notifications | A stacking, mergeable popup system anchored above the XP bar, for discrete player-facing events | | Dynamic UI | Drag/resize, content-scale/padding editing, cross-component snapping, group edit mode, and a pluggable command-center screen see below | | Diagnostics | Datapack validation, unknown-item logging, and debug commands | | Config tooling | Presets, import/export, share codes, and module locks | | Utilities | JSON helpers, bounded LRU cache, running averages, validation |

> It is designed to stay lightweight, modular, and reusable, and to provide a foundation rather than a gameplay framework.

## The classification pipeline

This is the core of MariesLib.

When a consuming mod needs to reason about a source it has never seen before, MariesLib resolves it through staged runtime logic:

• Runtime resolution: with caching and cascade fallbacks
• Token normalization: for domain-specific source vocabulary
• Recipe inheritance: with honest, non-suppressive multi-value blending: a name-based keyword match no longer silently locks out a genuinely conflicting recipe signal; contested categories now show up with real, non-inflated confidence instead of a falsely "stable" result
• Override registries: via `config//source_overrides.json`
• Classification traces so developers can inspect exactly why a source resolved the way it did, step by step

> There is also a developer-facing scanner** for bulk analysis of unclassified or under-classified sources including multi-value detection (finding sources that should carry more than one category, like a composite recipe item spanning several value groups), an ambiguous-sources report for anything genuinely needing manual review, and a generated starter datapack of recommended tag entries. It is not a player-facing gameplay feature.

> The exact pipeline is determined by the consuming mod. MariesLib provides the infrastructure; gameplay decisions remain the responsibility of the mod usi