satisfactorymodding / satisfactorymodding/SatisfactoryModManager

Instead of deleting the entire directory every time someone disables their mods why not just temporarily rename the Mods folder?

Open
#182 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Svelte
Stars
500
Forks
94
Avg merge
9d 19h
Merged PRs (30d)
2

Description

Possibly relevant backstory: I am new to Satisfactory and so might be missing some key issue here.

Main point: I recently started playing Satisfactory and have fallen in love with the game. Loving it as much as I do I have begun to delve into modding and so have begun using this manager to facilitate that. After installing a good number of mods I was curious about the folder structure worked for modding this game and how the manager itself worked and noticed that when I disable mods via the manager it is in essence completely deleting the Mods directory from the Satisfactory folder, which I feel might not be the greatest route for reasons I'll talk about briefly. Curious about why it was being done like this, I re-enabled the mods and waited a few minutes for the mods to be moved back to the game folder and then I went into the Satisfactory folder and simply changed the name of the folder "Mods" to "Mods (disabled)" and launched the game. I was wondering if perhaps renaming the folder was not enough or if the game might not function with an improperly labeled unexpected folder, but no, as far as I can tell the game is running flawlessly as if it was an entirely vanilla install without any Mods whatsoever in the folder structure. So this makes me wonder then WHY does the manager compeltely delete the folder instead of simply renaming it? While it might be a negligible issue if only done from time to time, deleting a bunch of files for no reason and then moving them back isn't exactly great for harddrives as every harddrive whether SSD or HDD has a read/write limit before the harddrive starts to function improprerly. It just seems really unnecessary to completely delete the folder and however many GB of data is there when to me all it appears that you actually need to do is rename the folder to something the game isn't looking for. If there is some reason why this doesn't work like I imagine it does, please let me know, but otherwise this just looks like as unnecessary shortening of the harddrive's lifespan for arbitrary reasons.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files or tests. Start by locating the manager's workflow for disabling and restoring the Mods directory, then inspect how that state change is handled. Done means disabling mods avoids unnecessary deletion while the game starts without mods, and re-enabling restores them correctly.

Written by the indexing model from the issue text.

Assessment

Domain
desktop, tooling
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.