Suggested / Compatibility / Integration type flag for mod developers
Posted: Tue Jan 20, 2026 8:49 pm
This is based on a discussion from Discord (#mod-dev-help Jan 20th 2026)
This thread serves as a place for mod discussion on the topic.
Many mod creators currently use the "Dependencies" field in info.json to identify direct support or compatibility for a different mod with our mod in an effort to cross-promote our mods to players of other mods. So if Mod A shows an optional dependency for Mod B, and someone is searching for Mod B or otherwise viewing it, then Mod A is shown in search results. There are other non-direct functional uses like this employed by various mod creators.
But this is not the intended use by WUBE, and it can also cause unintended circular mod dependencies loops.
Circular mod dependencies loop
Mod A has an optional dependency for Mod B
Mod B has an optional dependency for Mod A
First, why would a mod creator want to do this
(unrelated to directly functional fixes)
Mod A - could be an overhaul mod or otherwise large mod, but the author wants to add support for Mod B in their mod and change things based on Mod B being loaded.
Mod B - could be a cross-integrations mod or other content mod. But the author wants to add their own support or functionality if Mod A exists.
This can be done internally, just detecting the active mods via if mods["mod-a"]
However, if both mod authors are trying to expose or otherwise promote this cross compatibility to players searching the mod portal (both website and in-game portal) then the author could add optional compatibility for the desired mod.
This however, is not the correct use of Dependencies, and if both mod authors decide to do this, then we have our Circular mod dependencies loop as a possible problem.
Request:
A new system that operates much like the Dependencies definable in info.json, but viewable & searchable in the mod portal (both website and in-game portal).
But has no direct control over Dependencies load order/etc.
Maybe we can call it "Integration" or something similar.
A counter to this request would be "why, then, we just end up with people complaining about xyz mod not being listed."
The intent is for the mod author to show off what mods they have directly added support for either due to complexity, the other mods author didn't or wouldn't add direct integration for, or otherwise because the mod itself adds support for 2 conflicting mods (mod C and mod D break each other due to item or recipe issues) and the mod in question fixes the issue between the mods.
This thread serves as a place for mod discussion on the topic.
Many mod creators currently use the "Dependencies" field in info.json to identify direct support or compatibility for a different mod with our mod in an effort to cross-promote our mods to players of other mods. So if Mod A shows an optional dependency for Mod B, and someone is searching for Mod B or otherwise viewing it, then Mod A is shown in search results. There are other non-direct functional uses like this employed by various mod creators.
But this is not the intended use by WUBE, and it can also cause unintended circular mod dependencies loops.
Circular mod dependencies loop
Mod A has an optional dependency for Mod B
Mod B has an optional dependency for Mod A
First, why would a mod creator want to do this
(unrelated to directly functional fixes)
Mod A - could be an overhaul mod or otherwise large mod, but the author wants to add support for Mod B in their mod and change things based on Mod B being loaded.
Mod B - could be a cross-integrations mod or other content mod. But the author wants to add their own support or functionality if Mod A exists.
This can be done internally, just detecting the active mods via if mods["mod-a"]
However, if both mod authors are trying to expose or otherwise promote this cross compatibility to players searching the mod portal (both website and in-game portal) then the author could add optional compatibility for the desired mod.
This however, is not the correct use of Dependencies, and if both mod authors decide to do this, then we have our Circular mod dependencies loop as a possible problem.
Request:
A new system that operates much like the Dependencies definable in info.json, but viewable & searchable in the mod portal (both website and in-game portal).
But has no direct control over Dependencies load order/etc.
Maybe we can call it "Integration" or something similar.
A counter to this request would be "why, then, we just end up with people complaining about xyz mod not being listed."
The intent is for the mod author to show off what mods they have directly added support for either due to complexity, the other mods author didn't or wouldn't add direct integration for, or otherwise because the mod itself adds support for 2 conflicting mods (mod C and mod D break each other due to item or recipe issues) and the mod in question fixes the issue between the mods.