When The Last of Us Multiplayer Died | Analysis by Brian Moineau

When a Beloved Franchise Almost Went Live: The Last of Us Multiplayer's Rise and Fall

The Last of Us Multiplayer quietly became one of gaming’s most bittersweet “what if” stories. Fans remember Factions — the tense, soulful multiplayer mode from the 2013 original — and many hoped Naughty Dog would return to that magic. The Last of Us Multiplayer, a standalone live-service project often called Factions or The Last of Us Online, grew into an ambitious effort over several years, only to be dramatically scaled back and reportedly cancelled after being “about 80%” complete. (darkhorizons.com)

Why this mattered

For context, Naughty Dog built its reputation on cinematic, character-driven single-player games. Shifting a studio like that into the world of AAA live service multiplayer is not just a technical challenge — it’s a cultural and business pivot. The Last of Us multiplayer started as an extension of The Last of Us Part II’s ideas, evolved into a full project, and attracted big internal investment and high expectations. Yet, in a development landscape increasingly dominated by persistent online games with huge upkeep costs, the studio faced a trade-off: finish and support a sprawling live service, or refocus on the narrative experiences that define Naughty Dog. (dexerto.com)

  • It reportedly spent years in development — some sources say around seven years — and reached a late stage before being shut down or heavily reassessed. (gamesradar.com)
  • Internal voices and external partners were involved: there were reports of consultations and reviews, including input from other studios. (gamesradar.com)

What “80% done” actually means

Saying a game was “80% done” can be emotionally charged and technically misleading. Developers and studios measure progress differently. Often the visible systems, art, and core loops make up a large portion of early progress, while the remaining 20% can include the hardest parts: balancing, server infrastructure, anti-cheat systems, live ops tooling, monetization frameworks, and long-term support planning.

In other words, 80% might mean the prototype and many fundamentals existed — but not that the game was ready to ship or sustain a live community at scale. Reported quotes from former leads emphasize how close the project felt internally, yet also how daunting the last stretch was. (darkhorizons.com)

The industry tug-of-war

Transitioning from single-player excellence to live service success is difficult for any studio. There are several pressures that informed Naughty Dog’s decision-making:

  • Live services require continuous content updates, community management, and significant post-launch support teams.
  • AAA live games need long-term monetization strategies and technical backbones for servers, matchmaking, and anti-cheat.
  • Prioritizing one major live project can siphon talent and resources away from cinematic single-player titles, which often define a studio’s brand and revenue potential.

Because of these factors, Naughty Dog reportedly chose to reallocate resources toward other single-player projects, like the studio’s secretive Intergalactic: The Heretic Prophet, rather than commit to the long-term demands of an online Last of Us. That choice underscores a broader industry reality: not every beloved IP benefits from becoming a live service. (gamesradar.com)

What fans lost — and what they still have

Fans lost more than a potential new game; they lost a vision of how The Last of Us could translate into persistent, emergent multiplayer storytelling. Many players long for a refined, narrative-aware PvP experience that retains the franchise’s emotional weight.

However, there are silver linings:

  • The original Factions remains a touchstone and a design reference for team-based tension. Re-releases and memories keep its spirit alive.
  • Knowledge and prototypes from the canceled or paused project may inform future Naughty Dog work or inspire smaller-scale multiplayer experiments from former team members. (gamerant.com)

A closer look at the timeline

To clear confusion, here’s a concise timeline of the publicly reported events:

  • Development reportedly began around 2020, initially tied to The Last of Us Part II’s ecosystem. (forbes.com)
  • Over subsequent years, the project expanded into a standalone live-service title with a significant team.
  • Around late 2023 and into 2024, reports suggested the game was being reassessed or scaled back amid internal reviews and company priorities. (gamedeveloper.com)
  • Recently, statements from developers and coverage cited the project being “about 80%” complete at its cancellation or pause, triggering fresh debate about what “complete” means in practice. (darkhorizons.com)

Final thoughts

My take: the story of The Last of Us Multiplayer is a useful reminder that big ideas and beloved IPs don’t automatically equal sustainable live-service games. Quality, long-term support, and alignment with a studio’s identity matter just as much as ambition. While it’s heartbreaking to see a project with apparent momentum shelved, the choice to prioritize what a studio does best — especially when that’s telling powerful single-player stories — can be the braver, more honest path.

That said, the appetite for a well-made, emotionally resonant multiplayer Last of Us remains. If the right team, scope, and business model emerge — perhaps from former Naughty Dog talent or a smaller, more focused studio — fans may still get something that honors Factions without promising the impossible.

What to watch next

  • Anecdotes from former team members and interviews with studio leads will be telling about how much of the canceled work survives internally.
  • Any projects launched by ex-Naughty Dog devs could be fertile ground for The Last of Us-style multiplayer design.
  • Industry shifts in how publishers handle live services (shorter live ops, hybrid monetization, or tighter scopes) may open the door for revisiting similar projects with less risk.

Sources




Related update: We recently published an article that expands on this topic: read the latest post.


Related update: We recently published an article that expands on this topic: read the latest post.

Steam Goes Fully 64‑Bit on Windows | Analysis by Brian Moineau

Steam finally goes fully 64‑bit on Windows — and it actually matters

A small, quiet change rolled out in December 2025 that will make a surprising number of problems less annoying over time: Valve has converted the Windows Steam client to a native 64‑bit application. If that sounds like a nerdy footnote, stick with me — this is the kind of technical housekeeping that unlocks better stability, simpler development, and fewer edge-case crashes for millions of PC gamers.

What to know right away

  • The Steam desktop client for Windows 10 (64‑bit) and Windows 11 is now a native 64‑bit application (stable rollout in December 2025).
  • Valve will continue delivering a 32‑bit build only to systems that require it until January 1, 2026; after that date 32‑bit Windows installs will no longer receive updates or support.
  • The update also bundled several quality‑of‑life fixes and controller/input improvements (friends/chat reporting tweaks, recording/export fixes, better controller support, Big Picture/Remote Play bug fixes).

Why this upgrade matters

Upgrading an app from 32‑bit to 64‑bit is more than a checkbox for developers. For Steam, the switch brings practical benefits:

  • Better memory handling. A 64‑bit client can address far more memory, which makes it harder for leaks or memory‑hogging bugs to bring the whole Steam client (and sometimes the running game) to its knees.
  • Cleaner toolchain and testing. Valve no longer has to maintain two separate native builds for modern Windows installs, which reduces platform complexity and frees engineering time.
  • Compatibility with modern platform pieces. Many modern libraries, browser engines, and drivers are optimized for 64‑bit Windows — moving the client to 64‑bit aligns Steam with that ecosystem and avoids fragile edge cases.
  • A path for future features. Removing a legacy constraint lets Valve adopt newer subsystems or optimizations that assume 64‑bit execution.

Put simply: this is an investment in long‑term stability and fewer weird failures for the vast majority of Steam users.

What else shipped with the December update

Valve didn’t stop at the binary switch. The release notes and coverage show a batch of smaller but tangible fixes and additions:

  • Friends & Chat: new reporting options for suspicious or harassing messages inside group chats (right‑click to report and optionally block/unfriend).
  • Game recording: fixes for exporting H.265 videos and clipboard issues on certain NVIDIA 50xx GPUs.
  • Steam Input: expanded controller support — including Nintendo Switch 2 controllers over USB, improved GameCube adapter behavior in Wii U mode (with rumble), and pairing improvements for high‑end controllers like DualSense Edge and Xbox Elite.
  • Big Picture / Remote Play: stability and usability fixes (fewer in‑game purchase failures for some titles, Remote Play mouse movement fixes across multiple monitors when using touch).
  • Miscellaneous stability fixes: for the embedded browser helper and other components that could occasionally spawn stray windows.

These are the small wins that make day‑to‑day Steam use more pleasant.

Who’s affected (and who isn’t)

  • Practically everyone on modern Windows is unaffected in a painful way — if you’re on Windows 10 64‑bit or Windows 11 you get the 64‑bit client automatically.
  • A vanishingly small group of users on 32‑bit Windows 10 (Valve’s telemetry puts this at around 0.01% of the user base) will still be able to run Steam for a short while, but their client will stop receiving updates and security fixes after January 1, 2026. If you’re in that group, upgrading to a 64‑bit OS is the practical recommendation.
  • 32‑bit games remain supported. This change affects the Steam client binary and support lifecycle for 32‑bit Windows OSes — it doesn’t mean Valve is suddenly dropping older games.

The broader context

The move fits a larger trend across the industry: operating systems and large platform apps are shedding 32‑bit legacy support. Microsoft’s push and the natural hardware turnover means most PCs now run 64‑bit Windows, and browser engines and middleware are drifting away from 32‑bit compatibility. For Valve, consolidating around 64‑bit simplifies interactions with anti‑cheat vendors, browser components, and controller vendors — all of which tend to favor 64‑bit builds.

It’s also a subtle signal about priorities: Valve is choosing engineering simplicity and future readiness over maintaining obscure legacy setups. For a platform serving hundreds of millions of users, that pragmatism makes sense.

My take

This isn’t flashy, but it’s the kind of under‑the‑hood improvement that compounds. You won’t see a headline getting you excited about a new feature, but you will notice fewer random crashes, smoother controller behavior, and a slightly cleaner Steam client experience over time. For power users and developers, it removes a constraint that used to complicate troubleshooting and testing. For the tiny fraction still on 32‑bit Windows, the deadline of January 1, 2026 makes upgrading unavoidable if you want continued support.

Sources




Related update: We recently published an article that expands on this topic: read the latest post.


Related update: We recently published an article that expands on this topic: read the latest post.