Mineralogy 6.1.2.120062 for Minecraft 1.20.6 (NeoForge)

Mineralogy 6.1.2.120062 for Minecraft 1.20.6 NeoForge

• Added the first NeoForge Mineralogy baseline while retaining gameplay,
  world, registry, configuration, migration, recipe, documentation, relief,
  mining-tag, and furnace-state parity with the accepted Forge 1.20.6 release.

• Replaced Forge loader wiring with NeoForge 20.6 events, registries,
  capabilities, fluids, conditions, metadata, NeoGradle builds, and isolated
  CI. Forge and NeoForge artifacts remain deliberately separate.

• Made c: the canonical interoperability namespace while retaining narrow
  forge: aliases for historical consumers. Configurable vanilla recipes use
  dynamically rebound union tags in both modes; optional Mineralogy recipes
  use top-level neoforge:conditions.

• Updated all pickaxe and harvest-tier tags to the supported optional
  tag-entry object format. This restores normal mining speed and drops for all
  1,133 pickaxe-mined Mineralogy blocks, including every derived rock form.

• Synchronized a retained rock-furnace block entity with its new block state
  before reattaching it during lit/unlit transitions, preventing stale chunk
  state while preserving fuel, contents, and progress.

• Delegated terrain, strata, ore, and covered fluid-deposit generation to the
  released OreSpawn 4.0.16.120062 provider engine, retaining the supported
  [4.0.6,5.0.0) range; removed Mineralogy's parallel
  geology, geome, ore, noise, and stone-replacement generators.

• Preserved all world-facing registry, tile, NBT, recipe, asset, patch, and
  pre-flattening conversion identities while moving production packages to
  zone.moddev.mc.mineralogy. Existing 1.10/1.12 chunks are protected during
  1.20.6's flattening conversion. Legacy rock-furnace IDs are established
  before Mojang data fixing, then all pre-namespaced tile IDs are made safe
  before NeoForge constructs block entities, so inventories and progress survive
  and an uppercase vanilla ID cannot abort the complete chunk load.
  Legacy state tables now support the complete 12-bit mod block-ID range in
  both development and packaged runtimes, and each selected save reinstalls
  its own numeric mapping after the client enumerates multiple old worlds.

• Added compatibility-safe controls for drywall, rock-salt lamps, mineral
  dusts, and fertilizer, plus the stable five-way grouped creative tabs.
  Disabled content remains registered and usable in established worlds.

• Preserved vertically mounted legacy rock-salt lamps on torch-supporting
  blocks such as fences during pre-flattening world conversion.

• Corrected relief occlusion so their intentionally open centres reveal the
  supporting block face instead of culling it and exposing the sky/void when
  mounted on floors, walls, or ceilings.

• Made the historical COBBLESTONE_EQUIVILENT option functional through
  target-native per-family block and item tags, including vanilla aliases,
  reapplied after data reloads by rebinding the canonical tag sets and clearing
  the caches held by already-parsed NeoForge 20.6 recipe ingredients. Chert and
  pumice remain unconditional cobblestone equivalents.

• Added isolated Mineralogy crude-oil source and flowing fluids, block, bucket,
  rendering resources, and the covered Ocean deposit declaration.

• Uses Minecraft 1.20.6's native granite, diorite, andesite, basalt, and tuff for
  new OreSpawn terrain while retaining Mineralogy's historical registrations
  and conversion aliases. Native smooth basalt joins Mineralogy's smooth-basalt
  family without replacing Minecraft's basalt-smelting route. Deepslate remains
  a terrain and ore host rather than becoming a construction family.

• Preserved rock-furnace save recovery and novaculite's 3/15/1 properties;
  corrected replacement drop semantics and exact full-block Silk Touch results
  for double slabs.

• Ported the accepted recipe contract as 1,427 native JSON recipes and matching
  advancements: safe 4-to-1 mineral packing, charcoal and Base Metals dust
  gunpowder routes, exact slabs, slab recombination, construction-form brick
  conversions, progressive sand polishing, matching-slab rock furnaces, and
  blank-to-marked relief progression. Each rock-furnace recipe is revealed as
  soon as its matching slab is acquired, before a vanilla furnace is crafted.

• Reconciled Minecraft's native andesite, basalt, diorite, and granite with
  their retained Mineralogy world-compatibility blocks. Native blocks now
  unlock and feed every non-conflicting matching Mineralogy recipe. The four
  vanilla 2x2 polished-block recipes are replaced by block-plus-sand routes so
  the 2x2 recipes remain available for Mineralogy bricks. The six shared
  andesite, diorite and granite slab recipes plus all nine matching stonecutter
  routes now produce Mineralogy's more capable slabs, while the vanilla slabs
  remain registered and tag-compatible. Twelve exact shapeless compatibility
  recipes convert each raw or polished Mineralogy slab to its matching vanilla
  slab and back at a lossless 1:1 ratio for modpacks that require an exact
  vanilla item. Recipe advancements use the same exact item or family tag as
  the recipe they reveal.

• Extended Minecraft 1.20.6's native stone crafting and tool-material tags so
  every enabled cobblestone equivalent, including all 27 legacy rock families
  and target-native aliases, works in the complete vanilla contract. Nineteen
  JSON overrides backed by dynamically rebound tags cover furnaces, brewing stands, redstone and
  conversion recipes, and all stone tools without changing their IDs,
  patterns, outputs or other ingredients. Disabled mode restores the native
  ingredients and keeps blackstone, chert and pumice valid. Matching-slab
  rock-furnace upgrades and vanilla cobblestone construction recipes remain
  distinct.

• Added configurable tag-backed overrides for the coast, sentry, and vex armor-trim
  template duplication recipes. Enabled mode accepts the Mineralogy
  cobblestone union; disabled mode restores exact vanilla cobblestone. Their
  existing template-owned advancements remain untouched.

• Added sends_telemetry_event: false to every generated recipe advancement,
  including every overridden Minecraft advancement.

• Prevented NeoForge 20.6 from silently reducing optional carbon- or coal-dust
  gunpowder recipes to nitrate plus sulfur when their compatibility tag is
  empty; every loaded gunpowder recipe now requires all three components.

• Added 17 reviewed UTF-8 JSON locales with the same 938 ordered keys, including
  Brazilian and European Portuguese, Canadian French, Japanese, Korean, and
  Russian.

• Added first-start player, developer, content, provider, and version guides,
  plus an exact provider example. Existing exported guides are never
  overwritten. NeoGradle Eclipse launches keep their required processed
  bin/main mod output; if Eclipse removes Gradle's staged guide copies, the
  exporter reads the authoritative source-checkout guides without weakening
  packaged-jar validation.

• Added independent, atomic migration of valid non-default legacy ore settings
  into a Mineralogy OreSpawn provider override, including deterministic reports
  and exclusive-to-inclusive maximum-height conversion.

• Mineralogy 6.0 JSON upgrades now retain the original global and per-world
  geology files byte-for-byte while mapping their old block-named rock and ore
  entries onto Mineralogy's stable provider rule IDs. This prevents duplicate
  ore generation and preserves world-specific geology choices on first start;
  established OreSpawn files remain authoritative and reloads are byte-stable.

• Preserved 1.20.6-native wall tall-side blockstates and models, wall/item tags,
  loot tables, fluid APIs, rendering setup, and pack format 32 resources.

• Added reproducible Java 21 main, sources, and Javadoc artifacts, exact released
  OreSpawn dependency verification, guarded 1.20.6 CI, and the four-component
  release tag 6.1.2.120062.

• Adopted NeoGradle 7.1.38 and Gradle 9.2.1 on the pinned Java 21 toolchain.
  The NeoForge build no longer carries ForgeGradle's Mavenizer or auxiliary
  Java 8/25 toolchains, and release audits reject fixture leakage.

• Isolated CI's verified OreSpawn artifact in an exclusive Gradle repository so
  dependency resolution cannot fall through to an unverified public copy.
  Release verification also enforces Maven coordinate
  zone.moddev.mc.mineralogy:Mineralogy, its generated POM, and the jar's
  Maven-Artifact manifest entry.