Floogen / Stardrop

Stardrop is an open-source, cross-platform mod manager for the game Stardew Valley.
https://floogen.gitbook.io/stardrop/
GNU General Public License v3.0
110 stars 30 forks source link

Different profiles is not storing configs correctly #177

Open Chaoschaot232 opened 3 months ago

Chaoschaot232 commented 3 months ago

Profils storing config files wrongly which means that every time I switch to another profile some configs are wrong because changes which where made specific for this profile setup aren't matching the config settings for antoher bundle.

Best example is Challenging Community Center Bundle where I am using Profile 1 with the "Vanilla_SVE" Bundle but Profile 2 uses "Cornucopia_RSV_SVE" Bundle and while I am switching between both correctly saved profiles that specific config.json in the main mods folder isn't correctly re-written so what I am missing here is a config-copy which overwrites then the regulare config to be loadable.

This means that I assume that Stardrop copies the original configs of each mod per profile selection and loads then these specific adjusted configs when starting SDV over Stardrop then.

Is there a way to fix this or has this tbd by the mod author to add such a support? Would be nice to know.

GitHub-Sysadmin commented 2 months ago

This is an issue with the mod not stardrop. The config is stored in a single folder that is enabled on both profile 1 and 2 so it can't change the config. A workaround solution would to use challenging bundle and custom bundle, that way you can use both vani+sve and cornu+rsv+sve. Someone else posted about this and got the answer

Hello there,

it's possible to have them both, but it's tricky. The easiest solution would be, to only enable one of the variants each time your playing. So have the Challenging Bundles installed when playing alone and having only the Custom Bundles installed when playing with friends. Another option would be, to only use the [CCCB]-folder of the custom bundles and changing the manifest inside. To make it functional with the Challenging bundles, you need to change this part:

"ContentPackFor": { "UniqueID": "alja.CustomCCB", "MinimumVersion": "1.0.0" },

to

"ContentPackFor": { "UniqueID": "alja.CCCB", "MinimumVersion": "3.2.0" },

This would lead to only having to update the config.json inside the ChallengingCommunityCenterBundles folder.