[dshadowwolf]

MMDLib 2.0.2

Brings master-2.0-1.21.1-neo up to 2.0.2. It builds on the machine runtime expansion merged in #105 and adds:

• data-driven sounds, creative tabs and standalone fluids;
• the removal of the vanilla extensions;
• a much larger CraftTweaker integration, with generated docs for CraftTweaker's wiki.

The branch is rebased onto the #105 merge, so this diff is only the 2.0.2 work. CHANGELOG.md has the full 2.0.2 section, including a summary of #105.

Highlights

Build and platform

• NeoForge 21.1.265 (from 21.1.247), now the minimum version. Gradle wrapper 9.9.1.
• Spotless stays at 8.9.0 on purpose.

Vanilla extensions removed (breaking for worlds)

• The fifteen bundled materials are gone, along with their tools, armor, blocks, ammunition, dusts, gears, molten fluids, art, recipes, loot and tags. They now live in BaseMetals 4.0.
• Existing worlds lose items and blocks with those mmdlib: IDs when updated.
• The release jar no longer ships the generator for that content, which ran an external Python script.
• MMDLib's creative tab is renamed "MMDLib".
• The human detector's recipe needs #c:gears from another mod, such as BaseMetals.

Data-driven content

• Sound events: mmdlib/sound/<path>.json, with an optional fixed hearing range.
• Block sound sets: mmdlib/sound_type/<path>.json. A block's sound, or a material's block_sound, can name one.
• Sounds wired in: screen elements take a click-sound. XML machine processors take a looped running-sound and a finish-sound.
• Creative tabs: mmdlib/creative_tab/<path>.json, with ordered contents (items, #tags, whole materials), a translated title, an icon, placement and a search bar. CreativeTabDefinition.builder() does the same in Java.
• Standalone fluids: mmdlib/standalone/fluid/<path>.json declares a fluid family (fluid, flowing form, liquid block, bucket) with no material. A new plain mmdlib:fluid module sits beside mmdlib:molten.
• Other mods' content: they queue their own namespace's sounds, tabs and fluids on their RuntimeContentRegistrar, as with materials.

XML machines and screens (data stays the definition)

• Cycle events: a <processor> can name on-start and on-finish handlers. The new machine-cycle-start and machine-cycle-finish events carry the machine, level, position, machine ID, recipe and cycle length. Handler IDs are checked when machines load.
• Screen value providers: value="@namespace:id" (or max) reads a registered provider. It's type-checked against the element at load, like a getter.

CraftTweaker

All of this is in compat/CraftTweaker, with one gated call site in MMDLib's constructor.

#loader mmdlib startup scripts

• CreativeTabBuilder, SoundBuilder and SoundTypeBuilder build new tabs and sounds or edit ones declared in files (edit, exists, declared).
• FluidBuilder builds standalone fluids, with generated bucket models, blockstates and names.
• ScreenHandlers (click and hover), ScreenValues (whole, decimal, flag, text) and MachineHandlers (start and finish) register functions under mmdlib: IDs that screen and machine XML name.
• RecipeGenerators registers a machine recipe generator. Machine XML runs it through ScriptRecipeGenerator with script="mmdlib:<name>". Each reload it reads the reload's tags and the generator's attributes. The generator class has no CraftTweaker imports, so it fails with a plain message when CraftTweaker is absent.

Recipe scripts

• XML machine recipe types work with CraftTweaker's own <recipetype:...> managers.
• The typed MachineRecipeBuilder covers item, fluid, fluid-tag and energy inputs, reusable (consumed: false) inputs, outputs with chances, and time. It checks groups against the machines that use the type, as recipe reloads do.
• A recipe handler for machine recipes makes /ct recipes dumps print them as builder calls. CraftTweaker's Replacer takes them apart and rebuilds them, keeping each part's group, count, consumption and chance.

Docs for CraftTweaker's wiki

• All 53 script types carry @Document, and every member has a description, parameters, return values and @docParam examples.
• Compiling writes the wiki pages (docs.json plus one page per type, under Mods › MMDLib) to build/crafttweaker-docs.

For mods built on MMDLib

Records with new components. The earlier constructors still exist.

• MachineDefinition gained sounds and events, on top of Add multiblocks, dynamic machine visuals, and recipe controls #105's components. The 2.0.x constructor remains, and constructors without the new values use Sounds.NONE and Events.NONE.
• DefinitionLoader.Loaded, MaterialExtensions.Definitions and Common.Clicks also have new components.

Fluid IDs.

• FluidBuilder.setRegistryName fixes a fluid's ID, as for blocks and items.
• MMDFluid.flowingId() puts flowing_ on the last path segment (test/flowing_syrup for test/syrup). Every material fluid's ID is unchanged.

New public API.

• RecipeProcessor.startedCycles(), cycle() and justFinished().
• ScreenValueProviders, plus a ScreenBinder.bind overload that takes a provider registry.
• GeneratedMachineRecipes.validateGroups.

Removed. StaticAssetRules, which only served the removed artwork.

Build and tooling

• The CraftTweaker annotation processor writes the wiki docs to build/crafttweaker-docs.
• The formatter keeps @param name description on one line, which the docs processor needs. Files the formatter touched under this rule changed only in their Javadoc.
• The Java API Javadoc excludes compat/CraftTweaker, which is documented for the wiki instead.

Testing

• ./gradlew check passes: unit tests, both game-test suites (MMDLib 106, companion 101), Spotless, the line-limit warning task and the static-asset checks. ./gradlew javadoc passes.
• New game tests cover:
  • sound events and sound sets, from data and scripts;
  • creative tabs, from data and scripts;
  • standalone fluids from data and scripts, including placing and picking up with buckets;
  • script screen handlers and value providers;
  • machine cycle events run through real cycles;
  • script machine recipes: typed, JSON, removed, reusable, and refused for a bad group;
  • a Replacer rebuilding a datapack machine recipe;
  • the recipe handler's dump and a full decompose and rebuild round trip;
  • a script recipe generator running in a test machine.
• Every documentation page was checked for completeness.

Known issues

These are listed in the changelog and being fixed by #105's author. Update that section if the fixes land before tagging.

• Multiblock members must keep exactly their authored block state, so a state change (connections, waterlogging, lit) breaks the structure, and under REMOVE_OWNED removes it.
• Dismantling skips members in unloaded chunks, which keep stale links.
• Changing a multiblock definition's version or policy leaves existing controllers unable to form again.

Multiblocks remain an early proof of concept, and their API will change.

🤖 Generated with Claude Code