recommended and load order independent (+~) dependencies

[OhSnap]

Since we now have recommended dependencies it would be great if there is a way to have an option to make them load order independent. Right now those are exclusive options.
Given mod a and an optional addon a++, it would be great if a could recommend a++, but since a++ is an extension, it wants to run after a. The alternative would be to merge them and add a setting to enable a++, but then handling required dependencies of a++ becomes a mess.

current: a++ must run before a

Code: Select all

mod a:
  dependencies: { "+ a++" } -- recommend a++, force a++ to run first
  
mod a++:
  dependencies: { "~ a" } -- does not work without a

wanted: a++ runs after a

Code: Select all

mod a:
  dependencies: { "+~ a++" } -- recommend, but don't modify load order
  
mod a++:
  dependencies: { "a" } -- does not work without a, forces a to run first

[protocol_1903]

+1, although this feels like a convoluted method of recreating optional dependencies

[Thremtopod]

+1

Before recommended dependencies were added, there was no need to combine "~" with any other modifier; the main use of optional and hidden dependencies is to define load order. But recommended dependencies signal something more specific, giving them more usecases. This feature would fix a dependency cycle that showed up for Rigor Module:

Code: Select all

crushing-industry-tweaks --?--> nulls-k2so-tweaks
nulls-k2so-tweaks --?--> planet-muluna
planet-muluna --+--> rigor-module
rigor-module -(?)-> crushing-industry-tweaks <-- closes the loop

rigor-module needs to load after crushing-industry-tweaks because of changes to some furnace prototypes the latter does in data-final-fixes. planet-muluna has rigor-module as a recommended dependency, but does not actually care about the load order between the two mods; using "+~" instead would accomplish the same goal for that dependency without introducing the dependency cycle.

[MeteorSwarm]

+1. Muluna has no need to load after Rigor Module, even if my recommended gameplay style is to play Muluna with Rigor Module installed.

[protocol_1903]

Honestly, it feels like this would be solved by just making recommended dependencies only change where the mod is shown in the UI, then you can use whatever other dependency marker to define how it would load. If recommended dependencies were load order agnostic, I could add another optional dependency on the mod just to define it loading before my mod.