Hi, thanks for the mod!

I have discovered a conflict with Flare Stack Redux, which crashes the game on startup ("item with the name "quality-module" does not exist").

It would seem that Flare Stack Redux first generates voiding recipes for basically every item in the game, after which this mod removes quality modules that served as ingredient in some of those recipes. Mods will usually perform nil checks on objects before changing them, but they can't prevent them from being deleted later by other mods!

For the sake of mod compatibility, I think that it is better to hide the module items than to delete them. That could be accomplished with code such as this:

for _, Item in pairs({
    "quality-module",
    "quality-module-2",
    "quality-module-3"
}) do
    if data.raw.module[Item] then
        data.raw.module[Item].hidden = true
    end
end

The neutralized variant may still show up in some creative mod menus, and they will remain in any inventories, but otherwise the mod should work as intended.

By the way, you may also want to add this:

data.raw["virtual-signal"]["signal-any-quality"] = nil

I hope you find my suggestions helpful, and not bothersome!

Thank you for the report, I am looking into it now.

Aight!

New version uploaded with your improvements included. Thank you very much, greatly appreciated!

Pleasure to help!

Regarding the actual changes made, do keep in mind that it is a good idea to use a nil-check before hiding objects, especially at the final prototype stage (data-final-fixes) where especially many changes may have happened. (Such a check isn't necessary if you simply declare them to be nil.)

Guilty as charged! :D
Version 0.0.3 has been uploaded.

No-no-no, you should make the mod you want to make! 😉 Thanks for the update.

Ugh, truly not the mod I want, but Quality breaks one of my other mods.

Well! Yeah, it's rather unfortunate that quality is so hard-coded. They really ought to make it modifiable pr. prototype, at least so we can prevent unwanted interference with our mods.