You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Don't wanna fill up user's system ssd with redundant mod copies.
Need to find a balance between "put this in your Documents" for write access and "put this somewhere appropriate for storage".
Maybe something along the lines of "if you have an ssd as system disk and an additonal hdd then choose somewhere on the hdd" should be added to the guide anyway.
It is my understanding that there is a mechanism to gain write access in place, this could also be applied to mod library directory if necessary.
The text was updated successfully, but these errors were encountered:
This would be to change the default. I am not a big fan of forcing user to change simply because I have seen far too ma ybusers put mod manager in dumb locations, like in the game directory or configuration files folder. Wipe your config or wipe your your game? Well everything is now gone (I've seen the happen multiple times in logs which is why it defaults to Documents).
Ultimately I think it is up to the user to determine where they should store the mods. I don't think any sort of guidance on disk type should be a factor here. It'll probably be part of a startup prompt once me3cmm migration becomes viable.
This has been implemented into the preview welcome panel, though it needs validation to see if it works out. There are a few remaining things that this panel will need to do such as prevent loading mods until the dialog has closed.
Don't wanna fill up user's system ssd with redundant mod copies.
Need to find a balance between "put this in your Documents" for write access and "put this somewhere appropriate for storage".
Maybe something along the lines of "if you have an ssd as system disk and an additonal hdd then choose somewhere on the hdd" should be added to the guide anyway.
It is my understanding that there is a mechanism to gain write access in place, this could also be applied to mod library directory if necessary.
The text was updated successfully, but these errors were encountered: