[2.1.12] quality_min/change have misleading tooltips when used in combination
Posted: Mon Jul 27, 2026 3:59 pm
When you assign either of these properties on a recipe product, viewing the tooltips in Factoriopedia suggests that quality_min is applied both before and after the quality_change step.
Reproduction mod with the following contents in data-updates.lua:
Using this example mod along with the Quality mod, when the Iron gear wheel recipe is set to Normal mode, I expect it to output Rare gears (if it is unlocked), because quality_min would clamp it to Uncommon before quality_change steps up to Rare.
What actually happens is that it always outputs Uncommon gears (with or without the Uncommon quality unlocked):
Based on my understanding from the ItemProductPrototype docs and my own testing, quality_change always runs completely before any quality_min/max clamping.
I also shared this Lua algorithm on another thread, of how I think Quality adjustment currently works in the game.
Either the two tooltips (from the first two images) are misleading, or the adjustment implementation is incorrect.
Reproduction mod with the following contents in data-updates.lua:
Code: Select all
local gear = data.raw.recipe["iron-gear-wheel"]
gear.results[1].quality_min = "uncommon"
gear.results[1].quality_change = 1
gear.can_set_quality = true
What actually happens is that it always outputs Uncommon gears (with or without the Uncommon quality unlocked):
Based on my understanding from the ItemProductPrototype docs and my own testing, quality_change always runs completely before any quality_min/max clamping.
I also shared this Lua algorithm on another thread, of how I think Quality adjustment currently works in the game.
Either the two tooltips (from the first two images) are misleading, or the adjustment implementation is incorrect.