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
Often when I'm working on a mod list, I'm bouncing back and forth between Steam and RimPy to find new mods, research compatibility, etc. This inevitably leads to me subscribing to a bunch of mods in Steam but then forgetting exactly what they were called to go add to my active list.
I know I can use the Update Log tab to find recently updated mods but it's a bit inconvenient since you can't activate/deactivate mods from there. (I was going to add that it's pretty slow to update -- but that seems to have been fixed at some point... thanks!)
I guess an alternative idea would be to change the update log to allow activating or deactivating mods. That would then be my first stop after spending some time on Steam.
The text was updated successfully, but these errors were encountered:
I see no fast solution to check dates of mods. For now RimPy scans all mod folders and get creation date of each file and folder. The latest one (date) will be consodered as date of mod update. Checking all files of the mods is not fast and that is the problem.
Mark this as enhancement.
Often when I'm working on a mod list, I'm bouncing back and forth between Steam and RimPy to find new mods, research compatibility, etc. This inevitably leads to me subscribing to a bunch of mods in Steam but then forgetting exactly what they were called to go add to my active list.
I know I can use the Update Log tab to find recently updated mods but it's a bit inconvenient since you can't activate/deactivate mods from there. (I was going to add that it's pretty slow to update -- but that seems to have been fixed at some point... thanks!)
I guess an alternative idea would be to change the update log to allow activating or deactivating mods. That would then be my first stop after spending some time on Steam.
The text was updated successfully, but these errors were encountered: