By using this site, you agree to our Privacy Policy and our Terms of Use. Close
Chazore said:
Zkuq said:

TBH, this is Bethesda we're talking about, so could be poor QA, project management, or something similar. It sounds like an external company did the ports (at least for the third game, so I assume that to be the case for the first two as well), so it's possible Bethesda signalled the intent poorly, which resulted into this mess. My money is on Bethesda on trying their luck instead, but since it's Bethesda we're talking about, incompetence too seems like a plausible explanation.

Even if it was a "mistake", the fact that they desired to add a network account request into 3 games, which never had the same network authentication types decades ago, still isn't required, nor should they be "optional", because we shouldn't need Beth only networking, not when we've seen the 3 consoles and PC handling their own networks independently.

Beth doesn't need anyone to sign up for anything, "goodies" or not. If it's an always online based MP game, a la Fallout 76, then I can easily imagine their need for people to register to their network and make an account, in order to gain access to said game/content.

These 3 games are offline based, and do not really require an always online type connection.

Sure, Beth screw up and poorly handle things from their end, but things like paid mods and simply not adding in human NPC's into an obvious MMO, isn't some accident or mistake. Look at the countless times Todd Howard has been shown lying to consumers. I highly doubt 99% of what he says is something akin to mere mistakes or accidents. If we use poor handling from a publisher and poor coder logic, then I'd love to apply this to every other publisher, because I'm not one to pick favorites with this logic, because I know we're not always cared for to begin with.

Sure, I agree there's no need for online-anything for these games. But it's not entirely implausible that Bethesda really meant for this to be optional because they thought it makes sense for whatever reasons. It probably makes sense for Bethesda, and if it's optional, even I would probably not mind it (although I would probably think it's fairly pointless). Anyway, this whole thing seems like a mess that could (and should) easily have been avoided.

KManX89 said:
Zkuq said:

TBH, this is Bethesda we're talking about, so could be poor QA, project management, or something similar. It sounds like an external company did the ports (at least for the third game, so I assume that to be the case for the first two as well), so it's possible Bethesda signalled the intent poorly, which resulted into this mess. My money is on Bethesda on trying their luck instead, but since it's Bethesda we're talking about, incompetence too seems like a plausible explanation.

I don't know, I'd have an easier time believing they "accidentally" leaked people's credit card/personal info with the duffel bags debacle than I would believing they "accidentally" typed "A Bethesda.net account is required to play this game" into the game's coding, especially since it appears on the game's store pages. They actually hid it at the bottom of the PSN page thinking nobody would see it, sounds pretty deliberate and underhanded to me. Again, shit like that doesn't get coded in "by accident", all signs point to it being intentional.

Yes, that is why I wrote what I did. I deliberately avoided calling this a bug or a programming error because it's almost certain that's not what this is about. The part that makes this a possible error is that when Bethesda hired whatever team to do the port, they might have miscommunicated in a way that resulted in the team believing it was meant to be mandatory when Bethesda might in fact have meant for it to be optional. Even if the team got the intent right initially, it's possible it got twisted somewhere during development. Like I said, I don't believe that to be the case and I think this was intentional, but it's not entirely implausible it really was an error.