Synthesized mining recipes are marked allow_productivity (app/src/db/synthesize.ts), but no research-driven productivity is ever applied to them — effects.ts only aggregates modules, beacons, and TURD. The only research effects modeled today are recipe-unlock gating (research horizon) and belt/inserter stack-size bonuses for logistics.
Missing:
- Mining productivity research: the researched level should add a productivity bonus to all mining recipes (stacking with modules, respecting the +300% cap already implemented in
effects.ts).
- Recipe-productivity technologies (Factorio 2.0
change-recipe-productivity effects): per-recipe productivity bonuses granted by specific techs.
- Lab research speed, if/where labs are modeled as machines.
Since the mod already syncs live research state over the bridge, the bonus can come from the actual save rather than a manually-maintained preference slider — and the now | future | target research horizon should determine which level applies (current level for now, goal level for target).
First step: read the data dump to confirm which of these Py actually ships (mining productivity levels, any change-recipe-productivity techs) and cite the values, per the repo rule about never assuming Py mechanics.
Part of #31.
Synthesized mining recipes are marked
allow_productivity(app/src/db/synthesize.ts), but no research-driven productivity is ever applied to them —effects.tsonly aggregates modules, beacons, and TURD. The only research effects modeled today are recipe-unlock gating (research horizon) and belt/inserter stack-size bonuses for logistics.Missing:
effects.ts).change-recipe-productivityeffects): per-recipe productivity bonuses granted by specific techs.Since the mod already syncs live research state over the bridge, the bonus can come from the actual save rather than a manually-maintained preference slider — and the
now | future | targetresearch horizon should determine which level applies (current level fornow, goal level fortarget).First step: read the data dump to confirm which of these Py actually ships (mining productivity levels, any
change-recipe-productivitytechs) and cite the values, per the repo rule about never assuming Py mechanics.Part of #31.