Urgent.News

What's breaking now, across thousands of outlets.

Tech

No more Diablo 4 expansions are planned, but there's 'a lot of room' for more storytelling in the leadup to Diablo 5

The Diablo team is "all focused on seasons and getting to Diablo 5," support for Diablo 4 will continue "for a very long time," says Blizzard.

No more Diablo 4 expansions are planned, but there's 'a lot of room' for more storytelling in the leadup to Diablo 5

At BlizzCon, Blizzard revealed that Diablo 5 will be set a century after Diablo 4, with the story unfolding in a Sanctuary overrun by Diablo himself. However, no more expansions for Diablo 4 are planned, as the team is focused on releasing seasons leading up to the launch of Diablo 5 in 2029. Diablo game director Brent Gibson stated that the team feels they've told the story of Hatred, concluding with Mephisto, and now they aim to tell the story of Terror.

Even without expansions, the Diablo 4 narrative isn't over, as Blizzard needs to create an apocalypse in preparation for Diablo 5. Gibson emphasized the game's continuous support, citing Diablo 2 Resurrected as an example. He also mentioned the possibility of running Diablo 4 and its sequel concurrently, but acknowledged that dev resources will likely focus on Diablo 5 after its release.

Written by urgent.news from PC Gamer's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at pcgamer.com →

More in Tech

I ran my scanner against 5 real CVEs. It missed 4. Then I reverted my own fix.

Why this post is different from the last one The last write-up in this series announced four tools. This one is about what happened when I stopped writing tests for my own tools and started checking…

  • Scanner failed to detect 4 out of 5 real CVEs in Python codebases
  • One CVE (CVE-2023-30556) partially detected but classified as uncertain
  • Author reverted fix, removing silent exclusion of 94 real database call sites

Running a nested Proxmox homelab and Docker development on the same Windows machine

Tags: docker, proxmox, homelab, windows I sat down to start a new project and Docker Desktop wouldn't run. I knew why immediately, because I'd already paid this bill once — in the opposite direction.

  • Disable Windows hypervisor to run Proxmox and Docker Desktop simultaneously
  • Create DEV01 VM with Ubuntu 24.04.5, 4 vCPU, 8 GB RAM, 100 GB disk
  • Connect Windows Docker CLI to DEV01 Docker daemon via passwordless SSH

More from Saturday 12 September →