2.1 Mod Porting from a Not Code Person
Posted: Tue Jun 23, 2026 9:55 pm
Hello. These are my brief observations fixing a couple small mods I have. I am not a programmer, so here's what stood out to me.
1) The migration of category into categories also means that mods need to have the categories in an array in order to play well with the recycler mod. They should have the syntax of:
categories = {"cryogenics", "array-element-2", "etc"},
I note this because it seems to be an edge case of the recycler mod not handling non-array objects, and shows up on tests with callbacks to the recycler mod.
I did not test if errors were thrown in the event of loading a mod with categories = "single-category" on the base game only.
2) Similarly, the 2.1 release notes show lots of migrations of prototypes, and instructions to use a different prototype instead.
3) Not too much else, but I'm not a code person. I'd like to hear any other thoughts on the 2.1 porting, as I'm still interested in more coding.
1) The migration of category into categories also means that mods need to have the categories in an array in order to play well with the recycler mod. They should have the syntax of:
categories = {"cryogenics", "array-element-2", "etc"},
I note this because it seems to be an edge case of the recycler mod not handling non-array objects, and shows up on tests with callbacks to the recycler mod.
I did not test if errors were thrown in the event of loading a mod with categories = "single-category" on the base game only.
2) Similarly, the 2.1 release notes show lots of migrations of prototypes, and instructions to use a different prototype instead.
3) Not too much else, but I'm not a code person. I'd like to hear any other thoughts on the 2.1 porting, as I'm still interested in more coding.