Bethesda Shows Mercy On Fallout 76 Player After Vault Accident

Fallout 76 hasn’t had the best run of luck since its launch last year. It’s been besieged by bugs, has numerous glitches that cause players all sorts of problems, the content is somewhat lacking, and many promises that Bethesda has made have come up dry or severely lacking. And then, there’s Vault 63. This is a “dev room” that players aren’t allowed to go into for one reason or another, and anyone who does go into there is banned for their “crime”.

Which brings us to today’s story, where a glitch during a Rad-Rat Horde event actually spawned a person INSIDE Vault 63. How’s that for ironic? So naturally, the player looked around, took a bunch of screen shots, and then got out, and went to the internet to post them and ask Bethesda not to ban him for what happened because clearly it wasn’t his fault.

So, the question then became, “Would Bethesda show mercy on the gamer? Or, would they go and ban him outright?”

Turns out, they do indeed pay attention to their own subreddits, and the Community Manager for the game replied thusly:

“Glad to hear you got in and out of the Vault in one piece,” they¬†said. “These Vaults are still under construction, but we look forward to sharing more on how they will become part of the game. In the meantime, we also appreciate when players like yourself let us know about stuff like this. We have shared with the team and will let you know if we have any follow up questions. Thank you!”

So it seems they’re quite understanding of this particular incident. But the question of why the vault is still sealed off is one that hasn’t been answered yet. They’ll likely give an answer in due time by when is up for debate.

Regardless, Fallout 76 has some major things that need fixing, and Bethesda is running out of time to do it before all the gamers leave.

1 Comment
  1. joe soap says

    ban him

Leave A Reply

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.