Create:CompactMachinesPOR

0.3.43 — Item data components are no longer lost Fixed factories producing an Uncraftable Potion instead of a Water Bottle. Item identity was tracked by registry item ID only, so data components (e.g. potion_contents) were dropped both when sampling (ITEM.getKey(stack.getItem())) and when creating output (new ItemStack(item, count)). Fix: a count-1 item "template" carrying full components now travels the whole pipeline (IO sampling → trace → verdict → factory container) and is used to rebuild outputs. Templates are saved in factory NBT (old saves fall back to plain IDs), the goggles tooltip uses the template's hover name, and input whitelist entries keep their real components. Known limitation at this version: different component variants of the same item ID were still merged into one channel.

0.3.44 — Item identity upgraded to ID + component signature Fixed a more severe effect of the same root cause: channels that consume and produce the same item ID cancelled each other out (Water Bottle → Awkward Potion, both minecraft:potion). The three-scan net balance saw net ≈ 0 and dropped the channel entirely at solidification — the factory neither consumed nor produced anything. Item identity is now id#<sha256-16> (reduced to the plain ID when no components are present), derived from the canonical NBT hasher so signatures stay stable across sessions. Evaluation side: flow keys carry a signature; IO blocks report the real stack signature; inventory snapshots, container expansion and AE2 contents are keyed by signature; rate audit and replay net balance look up by signature; dropped items use the stack signature. Factory side: containers, rate tables and REPLAY pattern tables are keyed by signature, so different component variants of the same item get their own slots. Item handler slots are generated per signature with template-based stack rebuilding; NBT uses signature keys with backward compatibility for old plain-ID saves; fuel matching uses the container's item ID. Anti-dupe semantics unchanged: identical ID and identical components still cancel out, so no items can be created from nothing. No config changes or save migration needed — existing factories load as before.