Jump to content

Devdraco

Premium Member
  • Posts

    4
  • Joined

  • Last visited

Nexus Mods Profile

About Devdraco

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Devdraco's Achievements

Rookie

Rookie (2/14)

  • First Post
  • Conversation Starter
  • Week One Done
  • One Month Later
  • One Year In

Recent Badges

0

Reputation

  1. Are you in last year? Do you need help getting out lol. Hopefully we can find a way to bring thinking forward, rather than backward.
  2. I hope that you are wrong in this regard, which is why I made the topic.
  3. As this is a more focused issue, hopefully this will not be locked. I humbly plead for work towards the title.
  4. This post was shared on the dubious news that we all know about, by Thaiauxn. I am placing it here in order to sincerely request the following. Adjusted-proposal for the nexus collection system#1 -- Let mods opt in/out of the collection system. Not every mod works in a collection, because not every mod works with a mod manager. The 4GB LAA Patch for New Vegas doesn't work with Vortex or any other mod manager because it is an executable that must be run from the desktop and write to the game's exe. Fallout: New California is the same way. Letting us flag mods as compatible (or willing) to be added to a collection just saves the Nexus time and prevents collections from breaking. A simple checkbox "[ ] Opt-in to the Collection System," should appear next to all uploaded files. #2 -- Mod authors may archive older versions and forward collection links to the desired version. Again, not every version should persist. Version 221 of a mod may have severe bugs that cause a quest to break or spawn missing meshes and textures. We probably archived this version for a good reason, so when a mod is part of a collection that targets the download link, the user may forward to a specific updated file. This works for every collection the mod is currently in. So if a collection targets version 221, it is automatically forwarded to version 231. This address forwarding should link to any version in the achieve or current latest version, via a drop-down list in the manage files section. #3 -- Mod authors may permanently delete their mods. There is absolutely no ethical or legal reason to pursue this change to the TOS. None. It infringes on the EU law which gives people the right to be forgotten and have their private data removed, and it infringes on the rights of modder to control their property, and the safety of users and modders alike who may need to remove a file if it is found to contain private data that should not be released to the public or malware that was unknown at the time. This should not require admin approval or moderator help. This saves Nexus time and money and restore the freedom of mod authors. --- These changes to this system are simple, rational, and solve the vast majority of complaints here. I don't know what the Nexus believes is "the right thing," but it certainly isn't what's posted above using ultimatums and changes to the TOS done in private. Make these changes, and the system becomes rational, ethical, and along with an apology from nexus staff will smooth over the wrinkles as much as possible. Nexus may never restore the trust of authors after this, but this proposal at least shows a willingness to work with the community, instead of forcing changes to TOS that are ethically dubious and simply unfriendly.
×
×
  • Create New...