Urgent.News

What's breaking now, across hundreds of outlets.

Tech

Skyrim lead chats about the Fallout diehards who hated that Bethesda got the series: 'We had to prove them wrong, and fortunately we did'

Skyrim lead chats about the Fallout diehards who hated that Bethesda got the series: 'We had to prove them wrong, and fortunately we did'

When Bethesda acquired the Fallout license in 2004, many naysayers were vocal about their disappointment. The anger was largely directed at Bethesda for potentially ruining the series, with fans preferring the original, more traditional Fallout experience. Skyrim lead Bruce Nesmith recounted the backlash, stating that there were many Obsidian fans who were concerned Bethesda would turn Fallout into another Skyrim.

However, Nesmith and his team were determined to prove the naysayers wrong, and they succeeded, as Fallout 3 was well-received by both fans and critics. Despite the ongoing criticism, Nesmith believes the best approach is to simply focus on creating the best game possible and let that speak for itself.

Rewritten by urgent.news; may contain errors — check the original.

Read the original at pcgamer.com →

Report a problem with this story

More in Tech

S3 vs REST Storage: Choose by per-User Generated Image Controls in Node Express

Short answer: store every AI-generated image under a server-built users/{userId}/generations/ prefix, keep objects private, return expiring signed download links, delete known keys during user…

  • Use users/{userId}/generations/ prefix for tenant isolation
  • Implement application-level ownership checks for reads, deletes, and signed links
  • Choose between Infrai library or Amazon S3 based on team's preference

Searching a 40,000-Follower List Without Scrolling: Design Notes From Building It

Disclosure: I'm one of the people who built the tool linked in this post. I'm sharing the design thinking, not selling anything. Some AI assistance was used to draft this and I edited it.

  • Search at the source when possible to reduce requests and speed up the process.
  • Cache by the question, not the user, to optimize cache usage and performance.

More from Saturday 21 November →