Greslin Posted February 24, 2018 Author Share Posted February 24, 2018 If someone makes a mod, sure the mod manager they're using may point out that file x from whatever mod will be overwritten, but does anyone have the ability to test all the mods that exist themselves . . . No, that's where the testers come in. Now suppose someone made the database I'm suggesting. I don't really think we need mod police, running QA on each mod and ensuring that everyone's dependencies work properly. That's the player's job. A LOT of mods are just abandonware. Someone wrote it up, maybe polished it, maybe left it broken, and then lost interest. When you see a two-year-old mod with dependencies, it's a good bet that at least one of them are broken, because we're not required (thankfully) to coordinate that stuff with each other. That's why FO4 modder needs to learn FO4Edit and learn how to do their own detective work. Even so, what you're talking about isn't what this thread's about. Link to comment Share on other sites More sharing options...
Recommended Posts