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
{{ message }}
This repository has been archived by the owner on Feb 28, 2024. It is now read-only.
I find this feature annoying more often than I find it useful. For example if I want to test something with only a single mod and temporarily disable every other mod I would just take all the current mods and throw them into a different folder. The easiest option would be just a subdirectory within mods called like "disabled" and then take them back out of there later.
I don't know if anyone at all uses the subdirectories feature at all. I assume it's there to allow better organization but it actually prevents me from organizing mods how I want (right now I need to put a disabled mods directory OUTSIDE the mods folder which gets kind of annoying to navigate).
A good middle ground would be to have some way to specify a folder shouldn't be searched by the mod loader so for example a dot. That way I could make a folder called ".disabled" and anything inside of there would be ignored, but also I think completely removing this feature is a good option, unless there are actually people who use that to organize their mods.
The text was updated successfully, but these errors were encountered:
I personally don't use this either and found it some amount annoying as I'd sometimes do the same. The main benefit I suppose would be for mods that are packaged as zips or otherwise have multiple files associated with them can be grouped together in a folder.
maybe we could add an option to nml's config to disable it. if we want to be generic then we could maybe make this a regex string for what sub directories to ignore
I'd say ignoring folders with a dot at the beginning is the best option. tying this behavior to config would mean that any mod managers/updaters have to respect that option and it could get messy.
Or just revert the PR :)
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I find this feature annoying more often than I find it useful. For example if I want to test something with only a single mod and temporarily disable every other mod I would just take all the current mods and throw them into a different folder. The easiest option would be just a subdirectory within mods called like "disabled" and then take them back out of there later.
I don't know if anyone at all uses the subdirectories feature at all. I assume it's there to allow better organization but it actually prevents me from organizing mods how I want (right now I need to put a disabled mods directory OUTSIDE the mods folder which gets kind of annoying to navigate).
A good middle ground would be to have some way to specify a folder shouldn't be searched by the mod loader so for example a dot. That way I could make a folder called ".disabled" and anything inside of there would be ignored, but also I think completely removing this feature is a good option, unless there are actually people who use that to organize their mods.
The text was updated successfully, but these errors were encountered: