For situations where users must have mods in their normal A3 folder locations, or in custom mod folders, avoiding the Workshop and downloading normally from ArmaHolic, etc.
In general, after some initial confusion, I think the current Launcher setup for mod handling is fine and intuitive, and is certainly vastly preferable to mod duplication. Adding the View Workshop Folder in Explorer option to Launcher would be the simplest way to make mod handling by Launcher more user friendly. Ideally, rather than opening the mod folder itself, this would open the parent folder with the desired sub-directory highlighted using explorer's /select parameter Įxplorer /e, /select, C:\Games\Steam\steamapps\workshop\content\107410\682496867 One thing the launcher could do to make it easier to match workshop folders to mods is include a View Workshop Folder in Explorer widget in the panel for each subscribed mod. People who run servers or eschew the official launcher should *know stuff* - that's just how it goes with modded games on PC - including in this case how to create file system links which will yield the best of all worlds (single copy, updated automatically, visible in the A3 folder). Not duplicating mods is patently a better default behaviour and is entirely transparent for anyone who exclusively uses the provided launcher.
