• tal@lemmy.today
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    7 months ago

    So, I’m not saying that I agree with them slagging on Bethesda here. Hell, they haven’t even released their mod yet. Doesn’t break things for their players.

    But there is legitimately an issue where Bethesda pushes out an update and mods break. They have talked to a few of the very core mod creators early before to help alleviate breakage, but it can still leave mod-using players with a broken environment for some time.

    Obviously, Bethesda’s primary responsibility is to people playing vanilla, the stuff that they release.

    But there are a lot of modders and people playing with mods, especially a decade after release.

    Some of it is just a hard technical problem. There’s gonna be some degree or breakage at updates.

    But I think that it’s also true that there are a few things that Bethesda could do to help alleviate the breakage beyond what they have.

    Plus, you know, even aside from mods, doing a beta branch does have some benefits. Lets Bethesda find out about some bugs before they push an update to everyone. They won’t catch everything with internal testing.

    • BolexForSoup@kbin.social
      link
      fedilink
      arrow-up
      1
      ·
      7 months ago

      Like I said in my edit, I’m not entirely defending Bethesda here. I’m just trying to look at this case specifically and not let their entire history color it, as difficult as that may be. FOLON is somewhat turning this into a blame game, where I don’t think anyone’s really at fault except arguably Bethesda in that specific case.

      Even with all of that in mind, Bethesda should have been in better communication with modders. There’s no doubt here. They are critical part of the overall success and staying power of their games.

      From a business/PR standpoint, Bethesda missed a great opportunity to regain some rapport with the community post-Starfield