Better Than Ocelots - Crucible Resmelting Fix
==============================================

Overrides bwt's own built-in crucible "reclaim" recipes to match the values
you specified directly (superseding my own earlier wiki-pixel-reading,
which got some items right and some wrong).

Install: drop this whole folder (or the zip, most launchers accept zipped
datapacks directly) into your world's `datapacks` folder, then either run
`/reload` in-game or restart the world. This has to be a real world datapack
rather than something bundled in the mod jar - the mod's own built-in data
loads BEFORE bwt's own built-in data in this pack's resource/data order, so
a same-path override shipped inside the mod jar silently loses to bwt's own
copy. A real datapack always outranks any mod's built-in data.

NETHERITE AND DIAMOND: now a straight 1:1 refund
--------------------------------------------------
Per your rule, every netherite item now refunds exactly the netherite
ingots its own crafting recipe consumes, counting each bwt:armor_plate
ingredient as worth +1 extra netherite ingot (computed directly from bwt's
own soul-forge crafting recipes, not the wiki numbers I'd used before):

Sword 3, Pickaxe 3, Axe 3, Shovel 1, Hoe 2, Mattock 4, Battle Axe 5,
Helmet 10, Chestplate 14, Leggings 12, Boots 8.
(Axe was wrong before at 2, Helmet was wrong before at 14 - both fixed.
Pickaxe/Shovel/Mattock/Battle Axe already matched bwt's own defaults, no
file needed. Leggings/Boots were already right.)

I checked diamond the same way against your datapack's own diamond
crafting recipes (which use btwr:diamond_ingot + btwr:diamond_plate) and
every diamond tool/armor recipe already matches 1:1 + plate bonus exactly -
nothing to change there.

IRON / GOLD: corrected to your list
--------------------------------------
Sword:      12 nuggets (both metals)
Axe:        12 nuggets (both metals)
Shovel:     6 nuggets (both metals)
Hoe:        6 nuggets (both metals) - newly added, wasn't touched before
Pickaxe:    2 ingots (both metals) - Gold Pickaxe was wrong before at 6
            gold_nugget, fixed to 2 gold_ingot
Helmet:     30 nuggets (both metals)
Chestplate: 48 nuggets (both metals)
Leggings:   42 nuggets (both metals)
Boots:      24 nuggets (both metals)
Iron Door:  4 iron_ingot
Compass:    3 iron_nugget - was wrong before (gold), fixed to iron
Shears:     12 iron_nugget - was wrong before (2), fixed to 12
Cauldron (bwt:cauldron): 42 iron_nugget - was wrong before (30), fixed
Cauldron (minecraft:cauldron): 42 iron_nugget - newly added, had no recipe
Anvil (minecraft:anvil): 42 iron_nugget - newly added, had no recipe
Minecart: 30 iron_nugget - newly added, had no recipe
Clock: 3 gold_nugget - newly added, had no recipe
3 Detector Rails -> 2 iron_nugget (unchanged, already correct)
3 Powered Rails -> 1 gold_nugget + 2 iron_nugget (unchanged, already correct)
Redstone Latch (btwr_ds:redstone_latch): 2 gold_nugget (unchanged, already correct)
bwt_hct:dormant_soul_forge: 60 gold_nugget - newly added, had no recipe

ONE UNVERIFIED ITEM ID
------------------------
"Iron Chisel" - I couldn't find this mod's jar (tough_environment) in my
workspace to confirm the exact item id, so I guessed tough_environment:
chisel_iron based on the one chisel recipe I could find (tough_environment:
chisel_wood, a wooden chisel crafted from a stick). If the crucible doesn't
pick this recipe up in-game, that id is probably wrong - let me know and
send me the item's actual id (F3+H tooltip, or the jar itself) and I'll
correct it.

Rail (plain, non-detector/powered): left at 1 iron_nugget per 3 rails,
input stack fixed from 8 down to 3 - you didn't call this one out this time
so I left my previous fix in place; flag it if that's not right either.

v227 - CHISEL BRICKS FOR STONE, TUFF AND DEEPSLATE
--------------------------------------------------
EXACTLY TWO BRICKS PER STONE, and where they come from:

  mine 1  solid block   -> brick #1
  mine 2  cracked, break_level 3 -> nothing
  mine 3  cracked, break_level 5 -> brick #2
  mine 4  cracked, break_level 7 -> nothing
  mine 5  broken stone  -> rubble

A chisel steps break_level 3 -> 5 -> 7 -> broken, which is why the cracked
block only ever has three mines and why brick #2 sits at level 5.

Brick #1 is not ours: tough_environment's own vanilla stone.json and
deepslate.json already hand a chisel a stone_brick / stone_brick_2 on the
solid block's break. That is the brick that made three appear in v226 -
level 3 and level 7 were both ours, on top of tough_environment's.

Files under data/tough_environment/loot_table/blocks/ :

  stone_converting.json     - both chisel tiers drop tough_environment:stone_brick
                              at break_level 5 only.
  tuff_converting.json      - NEW relative to the mod (tough_environment ships
                              no table for tuff_converting at all). Drops
                              tough_environment:stone_brick_1 (Mantlestone
                              Brick) at break_level 5, both chisel tiers.
  deepslate_converting.json - the iron-chisel pool is replaced by a DIAMOND-
                              chisel pool dropping tough_environment:stone_brick_2
                              (Deepslate Brick) at break_level 5. Deepslate is
                              diamond-chisel only by design; the mod enforces
                              that.

And data/minecraft/loot_table/blocks/tuff.json :

  Solid tuff. tough_environment gives stone and deepslate a chisel brick on
  their solid break but has no such branch for tuff, and this pack's own
  TuffLayer used to replace tuff's whole table in Java with an
  unconditional tuff_loose + small_stone_1. So a chisel got the loose blocks
  and no brick. Now, matching stone's own structure:

    modern/advanced chisel -> 1 Mantlestone Brick, nothing else
    primitive chisel       -> 1 pile_gravel
    anything else          -> tuff_loose + small_stone_1  (unchanged)

  TuffLayer's LootTableEvents.REPLACE handler is now a pure passthrough, so
  this file is what actually applies. It had to move here: a REPLACE handler
  that ignores the original table cannot see the tool, and would beat any
  datapack that tried to.

These live here rather than in the mod jar because tough_environment ships
its own stone_converting.json, deepslate_converting.json and tuff.json, and a
same-path file inside our mod jar loses to it on load order. A world datapack
always wins.

Everything else about chisel behaviour - break speed, which chisel tier may
convert deepslate, and the "ding" that now marks the two brick-yielding
breaks - is compiled Java inside tough_environment and is handled by mixins
in the mod, not here.
