[2.0.72] manually advancing the crafting progress on a quality recipe makes normal quality output

[kiwimLisa]

Modifying the crafting_progress through script or command on a quality recipe make a normal output instead of the desired quality.

Both the script and command are consistent with this unwanted outcome.

exemple of the bug

10-28-2025, 00-33-49.png (259.32 KiB) Viewed 274 times

[Rseding91]

Thanks for the report however this is working correctly. You need to also set result_quality if manually setting crafting_progress *and the machine hasn't already started crafting*.

[PennyJim]

Then this should be moved to Documentation Improvements so we can ask for that to be mentioned.
Something like:

Note: setting a non-zero value while it's zero will start a normal craft free of cost and irrespective of recipe quality. Set result_quality to have another quality result.

I'm not the keenest on my chosen wording, but something to that effect.

[curiosity]

"Note: if this starts the crafting process, result_quality will not be set automatically and will default to normal, even for quality recipes."

But it's pretty stupid that a quality recipe has no inherent quality to it.

[Rseding91]

The engine could make an attempt at guessing which quality should be used, which seems reasonable to do. It won’t handle modules in the machine, or global beacon effects applied. But it might still be better then defaulting to normal.