I think I'm actively opposed to requiring categories. The vast majority of modders and recipes don't want anything other than the current default behavior (in my opinion).
I don't think modders currently even consider the category unless they specifically want something other than the default. As well as handling the default of {"crafting"} is dead simple.
And while turning the array of id's into a dictionary sounds really nice, I feel like that's the type of change you go all into (for every instance of id arrays). Meaning it would practically require a major version increase.
Like not even in my dreams do I really hope for it by 4.0...
That's more or less a fancy we're considering, not something we'll fight tooth and nail for.
Whereas I'm considering it for keeping the field optional.
Discussion/Poll: Potential unification of recipe category & additional_categories
- protocol_1903
- Filter Inserter

- Posts: 358
- Joined: Fri Sep 09, 2022 4:33 pm
- Contact:
Re: Discussion/Poll: Potential unification of recipe category & additional_categories
I am of the opinion that a default category (crafting) is the best option. Less overhead required for new modders to learn and it makes sense since most recipes will be of that cateogry.Rseding91 wrote: Thu Oct 23, 2025 7:02 am Unified vs not isn’t really the question here, it’s *if unified* how should it work when it comes to the default value and the crafting category - that’s the more “no solid good option” question.
Py and PyBlock developer, wielder of LUA in arbitrary ways. I make mods. Check them out, maybe.
https://mods.factorio.com/user/protocol_1903
https://mods.factorio.com/user/protocol_1903
