• Throwaway@lemm.ee
    link
    fedilink
    English
    arrow-up
    13
    arrow-down
    3
    ·
    11 months ago

    A modder doesn’t need to go through his team lead, tech leader, product manager, product owner, designer, and god knows what else.

    He can just do it.

    • kadu@lemmy.world
      link
      fedilink
      English
      arrow-up
      12
      arrow-down
      1
      ·
      11 months ago

      Yeah, people often ignore this aspect when comparing mods with official patches.

      If a mod introduces a game breaking bug that screws your save 20 hours in, or if it causes incompatibilities with some subset of hardware, the mod developer will just update their Nexus Mods pages with “tehehe, sorry guys, I’ve made an ooopsie”.

      If the official game developer ships the same issues, it would be a catastrophe that would cause problems for many paying customers and even full blown refunds.

      I love mods, but there’s a massive difference in the number of steps and QC needed for a modder to introduce a new feature vs the official devs.

      In the case of DLSS though, it should have been here from day one - and it probably would’ve been if the game didn’t have so many ties with AMD.

      • mnemonicmonkeys@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        4
        ·
        11 months ago

        the mod developer will just update their Nexus Mods pages with “tehehe, sorry guys, I’ve made an ooopsie”.

        Which boggles my mind. I made a couple of Skyrim mods years ago, and ended up deleting everything out of shame when someone spotted a bug where a related questline was broken across saves, thinking I was the cause. Turns out it was avtually Bethesda’s fault, but I still haven’t made a mod since

    • brandon@lemmy.zip
      link
      fedilink
      English
      arrow-up
      2
      ·
      11 months ago

      Ever wonder how many meetings it takes to get stuff like this done? Sheesh.