Roadmap

• Nutrient decay tuning

• Nutrition balance improvements

• Multiplayer nutrition synchronization UX

• Diet Screen improvements

• Nutrition history and trend visualization

• Recovery and neglect feedback

• Further HUD customization

#Calorie History

• 7-day average

• Trend display

• Historical calorie visualization

• Additional history configuration

#Raw Food / Gut Health

• Initial module — 2026-09-18

• Continued balancing based on gameplay feedback

#Hydration

• Future standalone module

• Designed as a separate system from the nutrition core

• Configurable hydration sources and effects

#Future Nutrition Systems

• Additional nutrient categories where they provide meaningful gameplay

• Ingredient-derived nutrition where appropriate

• More granular nutrition/sub-nutrient systems where supported by data

• More datapack-driven configuration

• Better scanner output → datapack workflow

• Additional datapack override capabilities

• More preset configurations for common server types

• Improve validation and error reporting

• Better tools for diagnosing classification results

#Farmer's Delight

• Expand food classification coverage

• Improve nutrition balancing for Farmer's Delight foods

• Improve datapack compatibility

#Quest & Progression Mods

• Quest triggers based on nutrient thresholds

• Nutrition-based objectives

• Recovery and diet progression objectives

#Advancements

• Balanced diet milestones

• Nutrient-specific milestones

• Neglect achievements

• Recovery achievements

#Accessories

• Curios support

• Equipment-based nutrition effects

• Configurable accessory interactions

#Compat Mods

Ongoing:

• Peak Stamina

• Spice of Life: Onion

• Legendary Survival Overhaul

Future:

• Additional popular food and survival mods

• Community-requested integrations

#CLS-017 — Create Food Classification Trace

Investigate and improve diagnostic visibility for unexpected ingredient/classification contributions.

Example:

createfood:chorus_fruit_ice_cream_sandwich

Current runtime classification:

• Protein: 0.33

• Fruits: 0.26

• Grains: 0.41

The final classification is acceptable and does not represent a player-facing bug. The goal is to make unexpected results easier to understand and diagnose.

#Future improvement

Add ingredient-level attribution to ClassificationTrace.

Example:

• Milk → +0.20 protein

• Chorus fruit → +0.XX fruit

• Flour → +0.XX grains

This would make classification debugging significantly easier for modpack authors and Nourished development.

• Split NourishedConfigScreen.java

• Remove remaining legacy configuration paths as Dynamic UI replaces them

• Continue separating stable and experimental APIs where appropriate

• Remove Classic UI after the Dynamic UI transition is complete

• Dynamic panels and layouts

• Move, resize, and scale UI components

• Registry-driven UI regions and slots

• Shared HUD editing infrastructure

• Dynamic configuration screens

• Color and appearance customization

• Reusable editor components

• Finalize the remaining Classic → Dynamic UI transition

#Tracking

• Player value tracking

• Tracker history and querying

• Value milestones

• Configurable decay

• Versioned tracking data

#Server-authoritative synchronization

• Registry synchronization across clients

• Tracking snapshot validation

• Multiplayer reliability for value deltas

• Robust client/server state reconciliation

• Runtime data resolution

• Source classification

• Source families

• Compatibility discovery

• Runtime diagnostics

• Resolver migration and cleanup

• Ingredient/source attribution

• Datapack schema validation

• Value key validation

• Classification coverage analysis

• Registry validation

• Configuration validation

• Validation report generation

• Runtime state capture on failure

• Classification trace reporting

• Synchronization failure diagnostics

• Registry state diagnostics

• Better contextual error reporting

Goal: Build a compiler-style validation and diagnostic layer for MariesLib-powered data.

• Architecture validation

• Registry validation

• Configuration validation

• Cross-system validation

• Compiler-style diagnostics

• Actionable fix suggestions

The compiler should eventually provide a unified way to inspect a modpack's MariesLib data before and during runtime.

#In Progress

• values/

• effects/

• synergies/

• source_synergies/

• milestones/

• tracking_profiles/

#Available

• source_classifications/

• compat/

• source_families/

• module_locks/

• Expand KubeJS scripting support

• Broader JEI / REI / EMI tooltip coverage

• Third-party mod discovery improvements

• More diagnostic commands under /marieslib

• Improved scanner and inspection tools

• Better Discover → Model → Verify workflows

• Separate stable and experimental APIs

• Split over-sized API and tracking classes

• Complete domain-agnostic audit of marie-ui & marie-commands

• Remove mod-specific assumptions from shared systems

• Establish clearer stable, experimental, and internal boundaries

• Keep architecture documentation aligned with the implementation

• Retrofit Thin Air: ReLived onto AttachedValueSync

• Test tracking and synchronization in additional Marie mods

• Improve third-party mod discovery

• Expand reusable compatibility hooks

• Remove hardcoded mod-specific assumptions where possible

• Maintain README.md

• Maintain API.md

• Maintain ARCHITECTURE.md

• Keep CHANGELOG.md current

• Document stable vs. experimental APIs

• Add developer examples for major systems

• Document datapack schemas and loaders