Showing posts with label Paragon Board. Show all posts
Showing posts with label Paragon Board. Show all posts

Tuesday, 25 August 2026

Diablo 4’s Paragon Point Bug Is Still Making Earned Points Disappear



There are many acceptable ways to lose power in Diablo IV.

A balance patch.

A bad Transfiguration roll.

Replacing an item and forgetting where half your resistances came from.

Pressing Refund All on your Paragon Board and getting fewer points back than you started with is slightly harder to defend.

Fresh reports from both PC and PlayStation players say Diablo IV is still occasionally leaving characters with missing Paragon Points, including one particularly clear PS5 case where a player had 260 points allocated, refunded the entire board and received only 258 back.

Closing the game did not fix it.

Relogging did not fix it.

And remarkably, variations of this problem have been appearing on Blizzard's forums since June 2023.

Three years later, Diablo IV may still occasionally charge a small administrative fee for changing your build.

A PS5 Player Lost Two Points After Refund All

The cleanest recent example appeared on August 18.

A PlayStation 5 Barbarian on the Eternal Realm says they had 260 Paragon Points invested.

That total matched what they expected from their Paragon level and completed regional progression.

Then they selected Refund All.

The result:

258 points.

Two had apparently disappeared.

The player restarted Diablo IV and logged back in, but the missing points did not return.

They also noted something rather worrying:

This was not the first time they had heard of the problem.

A PC Player Says Blizzard Support Confirmed Points Were Missing

A separate PC report from August 16 describes an even stranger situation.

The player believed their character should have substantially more bonus Paragon Points from completed regional progression and Altars.

After counting everything, they concluded that several points were missing.

According to the player, they contacted Blizzard Customer Support and a Game Master confirmed that their character appeared to be missing Paragon Points, then directed them to file a bug report.

That does not tell us what caused the missing points.

But it makes the report harder to dismiss as someone simply miscounting a complicated Paragon Board.

The thread remained active through August 23 as other players discussed similar problems.

This Problem Goes All the Way Back to Diablo 4’s Launch

The truly impressive part is the age of the complaint.

Blizzard forum posts from June 2023 already contain players reporting characters with fewer Paragon Points than expected.

One player said they refunded two nodes and received only one point back.

Another reported removing and rearranging Paragon Boards before discovering that previously earned points had vanished.

More reports followed throughout 2023.

Then 2024.

Some players associated the problem with manually refunding nodes.

Others encountered it after using Refund All.

Others believed regional Renown or Altars had failed to award points correctly.

So we should be careful about calling this one single bug with one known trigger.

“Missing Paragon Points” appears to describe several possible progression or refund failures that produce the same final result.

Your build planner says you should have another point.

The game disagrees.

Refund All Was Added to Make Respecs Easier

There is an unfortunate irony here.

Blizzard introduced the Refund All button back in Patch 1.2.1 specifically because rebuilding a Paragon setup one node at a time was tedious.

The whole point was convenience.

Press one button.

Get everything back.

Build again.

Players have nevertheless reported Refund All-related missing points since shortly after that feature was introduced.

One November 2023 report describes a character going from 225 points before the reset to 224 afterwards.

A May 2024 player reported losing four after using Refund All.

And now, in August 2026, we have another PS5 report describing the same basic sequence.

At this stage the button has developed history.

Why Two Missing Paragon Points Can Actually Matter

Two points do not sound dramatic in a game where endgame builds involve hundreds.

But Paragon Boards are pathing systems.

One missing point can be the difference between reaching:

  • A Rare Node
  • A Legendary Node
  • A Glyph socket
  • A required stat threshold
  • Or the next Board connection

Modern Diablo IV endgame builds are already separated by enormous amounts of effective power. We recently looked at how Tower scaling magnifies seemingly small build differences at the highest tiers.

Losing one or two permanent points may not destroy a casual build.

For a tightly planned endgame board, it can be enough to force the entire route to change.

Do Not Immediately Assume Your Points Are Gone

There is an important warning before everyone starts counting nodes and panicking.

Diablo IV's Paragon system has changed dramatically since launch.

The maximum level changed.

The number of Boards changed.

Seasonal rewards can add additional points.

Regional progression differs depending on what content and expansions a player has completed.

And online build planners may include points your particular character has not earned yet.

So if your build comes up short, that does not automatically mean you encountered this bug.

The best evidence is a simple before-and-after comparison.

If the board visibly contains 260 allocated points before Refund All and the game returns 258 afterwards, something has gone wrong.

That is much stronger than:

Maxroll says I should have two more.

Players Still Don’t Have a Reliable Fix

Unfortunately, there is no universal workaround.

Old reports contain players who recovered missing points after multiple complete resets and relogs.

Others say restarting did nothing.

Customer Support historically has not been able to manually add missing Paragon Points to individual characters and instead directs players toward the bug-report system.

If you are planning a full respec, the safest approach is therefore surprisingly low-tech:

  • Record your total allocated Paragon Points before resetting
  • Take a screenshot
  • Use Refund All
  • Immediately verify the returned total
  • If points are missing, document the before-and-after numbers in a bug report

It feels slightly excessive.

So does losing permanent character progression because you wanted to try another build.

Diablo 4 Has Enough Reasons to Fear the Respec Button Already

Diablo IV increasingly encourages experimentation.

Balance changes create new builds.

New items create new builds.

Players find a 4GA drop and suddenly discover a class they had no intention of playing yesterday.

We have already seen players worry that Transfiguration can permanently turn a dream item into something they regret.

The Paragon Board should be the comparatively safe part.

Refund.

Rebuild.

Discover the new setup is terrible.

Refund again.

That is the normal Diablo process.

Losing two points somewhere between steps two and three should not be included.

Especially when players were reporting essentially the same problem in the game's launch month.

Diablo IV has changed enormously since 2023.

Apparently some bugs are running Eternal Realm characters too.

Sources

Diablo IV Forums: Missing Paragon Points — PS5, August 2026

Diablo IV Forums: Missing Paragon Points — PC, August 2026

Diablo IV Forums: Missing Paragon Points — June 2023

Diablo IV Forums: Missing Paragon Points After Respec

Blizzard: Diablo IV Patch 1.2.1 — Refund All Added

```

Tuesday, 21 July 2026

Diablo 4 Can Apparently Kick You For Reading Your Own Inventory




Diablo 4 has spent several years adding more systems, more loot decisions and more menus.

It may also punish you for taking the time to read them.

A fresh player report claims that Diablo 4 can disconnect players for inactivity while they are actively working inside menus.

That includes tasks such as configuring a loot filter, rebuilding skills or changing Paragon points.

The game apparently sees a player making dozens of decisions and concludes that nobody is home.

Menu Activity May Not Count As Activity

The complaint appeared on the official Diablo IV forums on July 21.

The player described being automatically disconnected for inactivity despite still using the game.

Another user said the issue can become particularly frustrating while building a loot filter, because unsaved progress may be lost when the disconnect happens.

They also suggested that spending time reworking skills or Paragon points may fail to register as active play.

There are only a few reports in the discussion, so this should not be treated as proof that every player will encounter the same behaviour.

Still, the basic problem is not difficult to understand.

If a player is clicking through Diablo 4’s own menus, the game should probably avoid treating them like an abandoned shopping trolley.

Thirty Minutes Sounds Generous Until You Open The Build Menu

One response suggested that the inactivity timer may be around 30 minutes.

That sounds like plenty of time if the player is standing motionless in town while making coffee.

It sounds considerably less generous when the player is building a complex loot filter, comparing gear or changing an entire endgame setup.

Diablo 4 now asks players to manage affixes, Tempering, Masterworking, Charms, Seals, Paragon paths, skill points and multiple equipment interactions.

That can take time, especially for players who are not copying a finished build from another screen.

Sometimes people actually read the tooltips.

Blizzard should not punish such reckless behaviour.

Loot Filters Make The Problem More Obvious

A loot filter is not something every player will finish in two minutes.

A detailed filter may require players to inspect categories, choose affixes, create rules and repeatedly adjust what the game should display.

That process is gameplay.

It directly affects what appears during combat and how efficiently the player can identify useful drops.

If the game only recognises movement and combat as legitimate activity, it misunderstands how much of modern Diablo happens between the fights.

Loot filters are especially vulnerable because losing unsaved work is more serious than simply being returned to the login screen.

A disconnect can potentially erase a long configuration session and leave the player rebuilding the same rules again.

Nothing improves an action RPG quite like entering the same checkbox twice because the server decided your first attempt lacked enthusiasm.

Diablo 4 Already Demands Plenty Of Inventory Time

Inventory management has always been part of Diablo.

The series is built around finding items, comparing them and deciding what deserves to survive the journey back to town.

Diablo 4 has added more layers to that process.

A single item may need to be evaluated for its base affixes, potential crafting value, build compatibility and whether it can replace something already upgraded.

Players also need to manage materials, consumables, seasonal items and multiple equipment slots.

Even with better storage and filtering tools, there is a lot to inspect.

For more coverage of the current game, visit our Diablo 4 archive.

The Game Cannot Demand Decisions And Then Rush Them

Diablo 4 often wants players to make careful decisions.

Changing a build can involve substantial gold costs, rare materials and several interconnected systems.

One misplaced point or mistaken reroll can be expensive.

At the same time, an inactivity system that ignores menu interaction effectively tells players to hurry up.

Those two design goals do not fit together.

You cannot build a game around detailed character optimisation and then treat detailed character optimisation as suspiciously close to doing nothing.

The inactivity timer makes sense in principle.

Online games do not need players remaining connected indefinitely while genuinely absent.

The issue is not that Diablo 4 disconnects inactive users.

The issue is what Diablo 4 considers inactive.

A Warning Would Solve Half The Problem

The original forum post asked for a warning before the automatic disconnect.

That would be the minimum reasonable improvement.

A visible countdown could tell players that the game is about to remove them and give them time to save unfinished work.

Better still, interaction with any meaningful menu should reset the inactivity timer.

Changing a skill point should count.

Editing a loot filter should count.

Moving through Paragon nodes should count.

Comparing items should count.

The player is clearly present and using the software.

Requiring them to briefly leave the menu and make their character spin in a circle would not make the system smarter. It would simply make the ritual stranger.

Unsaved Progress Is The Real Risk

Logging back into Diablo 4 is usually not a major ordeal.

That is why some players may see this as a minor inconvenience.

The larger issue is losing work completed inside a menu.

If a loot filter or another configuration tool does not continuously save changes, a surprise disconnect can erase meaningful progress.

That turns an ordinary inactivity timer into a small data-loss problem.

The game should either save menu changes automatically or provide a clear warning before ending the session.

Ideally, it should do both.

Players should not have to remember to save every few minutes because the game may suddenly decide that clicking, scrolling and rebuilding an entire character do not qualify as human activity.

This Is A Small Problem With An Easy Fix

Diablo 4 has larger bugs.

Players are dealing with broken progression, seasonal systems and endgame rewards that carry far more serious consequences.

This issue is smaller.

It is also exactly the kind of irritation that should be easy to remove.

Recognise menu input as activity. Add an inactivity warning. Save loot filter changes automatically.

None of that requires redesigning the entire endgame.

Diablo 4 wants players to care about their gear and builds.

It should probably stop disconnecting them while they are doing exactly that.

Sources

```