remove dependency on farming

[fluxionary]

currently, there is an optional dependency on farming, in order to craft inventory bags out of cotton and string. this is not needed - the recipes will continue to function when farming is present, whether this mod depends on it or not.

depending on farming causes problems. farming depends on stairs. if i want to create an alternate "stairs" implementation which registers custom recipe types with unified inventory, we now have a dependency cycle.

ideally the bags (content) should be excised from the core of unified_inventory, which should just be an API, but that's a lot of work.

[SmallJoker]

Please add a note to the relevant crafting recipes that an optional dependency is intentionally not added to the mod.conf file due to possible circular dependencies

[fluxionary]

Please add a note to the relevant crafting recipes that an optional dependency is intentionally not added to the mod.conf file due to possible circular dependencies

will do, but crafting recipes are never hard dependencies, and i think it should be normal to treat them that way.

[SmallJoker]

Neither is faming a hard dependency. It's a recommendation to have the best experience with unified_inventory to not miss out on bags (unless another recipe is added). I suppose such a note does not matter too much because this repository is barely ever updated.

Will merge soon (TM)

[fluxionary]

hard dependency

i think we're on the same page, but i think i should have said something like "explicit dependency" instead of "hard dependency". in this ontology, optional dependencies are also explicit dependencies.

• it is an error to try to initialize a mod w/out "hard" dependencies present and loaded
• it is not an error if a mod has an optional dependency (explicit, but not hard) which isn't present or cannot load for some reason
• some integration code, like recipes, works as intended w/out requiring explicit dependencies on on other mods involved in the recipes