Page MenuHomeFeedback Tracker

Steam Workshop mods not being deleted after extraction
Assigned, WishlistPublic


Whenever I download a mod it first downloads it to the steamapps/workshop/content/107410 folder from the appropriate steam library and then it seems to extract it to the Arma 3 folder.

This seems to be normal behavior, but the mod in the workshop folder is not being deleted, which is a big issue because some mods take several gigabytes of space and having 2 copies fills up my ssd too quickly.


Legacy ID
Steam Workshop
Steps To Reproduce
  1. Download a mod from the steam workshop
  1. Start Arma 3 launcher
  1. Notice how the mod is in both the Arma 3 folder and the steamapps/workshop/content/107410 folder

Event Timeline

Cyprus edited Steps To Reproduce. (Show Details)Dec 31 2015, 1:47 AM
Cyprus set Category to Steam Workshop.
Cyprus set Reproducibility to Always.
Cyprus set Severity to None.
Cyprus set Resolution to Open.
Cyprus set Legacy ID to 1623806294.May 8 2016, 1:24 PM

we know about this but those files are not ours to manage, not they can't be safely deleted or modified without compromising functionality of Steam client.

We're trying to find a safe way to remove the data redundancy, but at the moment there is no magic solution for this, all of them have some severe disadvantage (that includes also the most famous symbolic link/mklink hack).

Cyprus added a subscriber: Cyprus.May 8 2016, 1:24 PM

I'm sorry I'm not sure what you mean by the first sentence. If I delete the mods from the steamapps/workshop/content/107410 folder after the mod is transferred to the Arma 3 folder everything seems to be working fine. Is there a reason why this can't be done automatically?

R3vo added a subscriber: R3vo.May 8 2016, 1:24 PM
R3vo added a comment.Dec 31 2015, 3:38 PM

Don't delete those files, it will eventually corrupt the data needed by the launcher to properly detector mods. Once the issue appears you have to check the data integrity and redownload all mods. Trust me, I've been there.

Unfortunately the best result is that Steam's going to re-download the data back into those folders; the worse results includes that Steam will force you to wait until it does that and won't allow you to play, or that it gets stuck in the update loop. It the past those worst results were more probable, but Valve improved the client regarding this, but the client behavior in such situation is still undefined.

Ultimately we'll offer (the most likely) an option to link the mods directly to Steam Workshop cache, but we want to make the best effort to ensure that Steam can recover when from people meddling with those files even when they will be instructed not to do so.

Is Valve aware of the issue? Should I make a report on their support page?

No need to do that, we have contacts directly on their engineers :).
From their perspective it works as designed, although they are still improving it. Six months ago, we've dismissed the idea of symlinking as too dangerous, and now we're considering releasing it to public.

Cyprus removed a subscriber: Cyprus.Jun 1 2016, 7:37 AM
R3vo removed a subscriber: R3vo.Nov 6 2020, 11:43 AM