Not challenging you, but I'm wondering why what appears to me to be an extended archive of older mod versions, is a bad thing. If I understand what you've said here, it's that the collections feature makes it so older/non-updated copies of a mod are archived so that mod users can continue to access them and even if a mod is "current" but part of a collection, it stays available even if you desire to stop working on it? Nexus is now taking that away.įull disclosure: I'm one of Nexus Mods' top 1% mod makers and am monetised on the platform. Their copyrights don't exist (my own mods are wholly copyrighted to Bethesda Softworks, Microsoft, Redmond) and control is all they have. Modders exist in a weird space where creative control is all they have. Some popular modders, Arthmoor is making news recently, are pulling out completely.
The Nexus Mod Manager is quite able to handle mod conflicts, and even to resolve deletions locally on the local machine, giving this same behaviour, but allowing mod makers to delete their mods from the site.
It's a warhammer to solve a problem requiring a katana. The reaction, to not allow a mod to be deleted and to retain previous versions, is ham-fisted. Where mod compatibility (where it exists, I posted many a rant on this topic) is changed, Nexus collections are broken. Now if my mod was part of that load out (and, for Fallout 3, it probably is) and I decide to supersede, change compatibility, or delete my mod, I've broken your collection. Nexus is introducing a feature called "collections" where players can set up their mod load-out for whatever game. It strikes quite close to my heart, as I'm one of the mod makers affected. Various sections of the gaming press are covering this one.
0 kommentar(er)
