One route might be to push out a new release for a month or something on a beta branch so that modders can see what breaks and provide some time to fix it prior to it being pushed out to everyone.
Take longer to get updates out, but reduce windows where mods are broken.
They’re saying this will take more than 2 months. They’re upset because it effectively undoes a lot of their work, which sucks, but that was always going to be the case unless bethesda went out of their way like a year ago to tell them what was coming. And remember, these guys aren’t even in the creator club or in any way communicating with Bethesda. I just think it’s a little unreasonable to be so independent while expecting Bethesda to anticipate their very specific needs.
I wish Bethesda did and maybe I’m being too generous but idk. Just not really sure I am 100% sympathetic to their plight here.
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.
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
One route might be to push out a new release for a month or something on a beta branch so that modders can see what breaks and provide some time to fix it prior to it being pushed out to everyone.
Take longer to get updates out, but reduce windows where mods are broken.
No, this is a bad idea because it makes too much sense.
It would’ve shaved one month off their currently undetermined new release date it sounds like.
They’re saying this will take more than 2 months. They’re upset because it effectively undoes a lot of their work, which sucks, but that was always going to be the case unless bethesda went out of their way like a year ago to tell them what was coming. And remember, these guys aren’t even in the creator club or in any way communicating with Bethesda. I just think it’s a little unreasonable to be so independent while expecting Bethesda to anticipate their very specific needs.
I wish Bethesda did and maybe I’m being too generous but idk. Just not really sure I am 100% sympathetic to their plight here.
Or they could just keep the legacy endpoints intact while still adding new features.
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.
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