Fix H3 RefMod Config

Every RefMod has "magic settings" - the retention level and curve that make its concept actually behave, plus a step curve if you're timing when the ref kicks in. Figuring those out is a small research project of its own. Fix H3 RefMod Config is the pack's answer for people who do that research once and never want to repeat it: it writes your tuned Apply and Step Curve settings into the mod file's own metadata, so anyone who loads the .safetensors later can flip one switch and get the exact configuration it was built with.

Think of it as the sharing/collaboration node. If you only ever run your own mods on your own machine, you can skip it - the widgets on Apply and Step Curve do the same job live. The payoff is when a mod leaves your hands.

How it works

The README lays out the two-sided flow:

1. Creator: tune Apply H3 RefMod (and optionally H3 RefMod Step Curve) until the concept behaves. Then wire mods through this node - Loader → Config → Apply - and set the same values here. Run once: the config (retention + curve + step_curve) is written into the mod's safetensors metadata and the file is re-saved in place. Share the .safetensors as usual.
2. User: load the mod and flip override on Apply (and/or connect the bundle to Step Curve's optional mods input and flip its override). The node reads the first mod in the bundle that carries a config and uses those settings instead of the widgets. Override off is today's default behavior - manual parameters all the way.

The bundle passes through the node unchanged apart from the config attached to each mod and written to disk, so wiring it inline costs you nothing.

Inputs are the settings themselves: retention (1.0 = fully_preserved, 0.7, 0.4 = attribute_transfer, 0.15 = weak_reference), then the frame-curve trio - curve_direction (default concept_at_end here), curve_shape, curve_value - and the denoise-timeline trio - step_curve_direction, step_curve_shape, step_curve_value. Same values and meanings as the nodes they feed. The single output is mods, ready to carry on to Apply.

Install

ComfyUI Manager (search "ComfyUI-MiniMaxH3Mod") or:

cd ComfyUI/custom_nodes
git clone https://github.com/Luisacaotica/ComfyUI-MiniMaxH3Mod

Restart; deps are light (safetensors, numpy, Pillow). You need H3 weights + its VAE in a current ComfyUI; the pack itself downloads nothing, and remember H3's licence excludes the US, EU, UK and Korea from local weights.

Common issues

Config falls back gracefully: if a bundle has no mod with a saved config, override prints a console note and uses the manual widgets - it never silently does nothing, and Apply's curve graph debug output shows the overridden curve so you can see what actually ran. If a config seems to be ignored, check the console for that note and confirm the file was actually re-saved (the node prints the path). And be clear-eyed about what shipping a config buys: it persists settings, not results - the recipient's model, prompt, sampler and other references still shape the output. There's no <Name> trigger magic baked in, just the dials.