Gambling Exposes How Severe the Underlying Transaction/Autosave Bug Actually Is
NEW REPRODUCIBLE EXAMPLE: GAMBLING
I have continued trying to play through the PS4/PS5 offline hitching/freezing issue that has existed since the 3.0 / Reign of the Warlock update, and I recently realized that gambling may be one of the clearest demonstrations yet of how badly the underlying game interaction is broken.
When gambling on PlayStation offline, purchasing an item is no longer an immediate, repeatable action like it was before 3.0.
Normally you can rapidly purchase gambling items one after another and fill your inventory.
Now:
-
Purchase a gambling item.
-
The item enters the inventory.
-
The game hitches/locks for a noticeable period.
-
Another purchase input immediately afterward frequently does not register.
-
You have to wait and/or press the purchase button repeatedly before the next transaction occurs.
-
Items appear in the inventory in a visibly choppy, delayed manner.
-
The same process repeats for every purchase.
Something as basic as gambling away a character’s accumulated gold can consequently take many minutes because the game is effectively pausing between transactions.
This is important because gambling repeatedly invokes the exact type of transaction/identification behavior that has been associated with this bug from the beginning.
It makes the underlying issue extremely easy to reproduce dozens of times consecutively.
This is NOT simply a “Cain identification bug.”
Cain identification was only the easiest trigger I originally found in February.
Over the last six months, this same hitch/freeze has been observed during or immediately around:
-
Gambling transactions
-
Manual item identification
-
Cain identification
-
Vendor purchasing/selling
-
Horadric Cube transmutation
-
Moving items into the Cube
-
Entering portals
-
Entering new areas / zone transitions
-
Autosaves during ordinary gameplay
-
Item drops / certain gameplay events
-
Other seemingly transaction- or save-related moments
Another particularly easy reproduction is gem cubing.
With the console shortcut that allows you to hold the button to move three matching gems directly into the Cube, you can load the three gems, press Transmute, and immediately observe the hitch associated with the resulting cube transaction/save.
Do this repeatedly while upgrading a large number of gems and the interruption becomes extremely obvious.
There is also evidence that these events share an underlying transaction/validation process.
Back in February I captured the Cain identification hitch on video and stepped through the recording frame-by-frame.
During the freeze, a message appeared above Cain that said:
“Waiting For Confirmation Of Transaction.”
That message is normally gone so quickly that a player would never see it.
That led me to suggest at the time that identification may simply be exposing a broader transaction/validation slowdown—that other actions such as vendors, portals, Cube operations, Chronicle-related activity, etc. may pass through some common game-state process that previously completed essentially instantaneously.
Six months of additional observations make that explanation look more relevant, not less.
Gambling is now a particularly useful stress test because it invokes this behavior repeatedly and rapidly.
Instead of one isolated hitch, you can watch the game’s normal interaction loop break over and over again.
This also affects actual gameplay and is especially dangerous in Hardcore.
The problem does not remain safely inside menus.
There are still intermittent stalls during gameplay and around area transitions.
That matters enormously in Hardcore.
If the game stalls during combat, immediately after entering an area, while teleporting, or while enemies are active, the game world does not politely become safe because the client has stopped responding normally.
A fraction of a second or a one-second interruption can be the difference between reacting and losing a Hardcore character permanently.
This began after 3.0 and did not exist before it.
I played D2R on PlayStation for years before this.
The game did not behave this way.
The original problem appeared with the 3.0 / Reign of the Warlock release and has persisted through subsequent patches. A later update temporarily made the presentation even worse by causing the UI itself to disappear/reload during these events, but that was an additional manifestation of the problem—not the beginning of it.
This is also not limited to expansion characters.
I and others have reproduced the underlying hitching with non-DLC/core-game characters as well.
Extensive troubleshooting has already ruled out the obvious local causes.
Over the course of these reports I have tested, among other things:
-
Native PS5 version
-
PS4 version through backward compatibility
-
More than one PlayStation console
-
Reinstallation
-
Fresh PlayStation profile
-
Fresh game data
-
Fresh character with no previous save history
-
DLC and non-DLC characters
-
Migrated and non-migrated characters
-
Cache clearing
-
Database repair/rebuild
-
Current console firmware
-
Removal of loot-filter settings
-
Performance and graphics settings
-
VRR enabled/disabled
-
120 Hz enabled/disabled
-
HDCP changes
-
Legacy graphics-related settings
-
Numerous combinations of in-game video settings
The behavior persists.
At this point, after approximately six months, this needs to be treated as a game-code issue requiring investigation rather than another request for affected players to troubleshoot their consoles.
I will record a consolidated reproduction video.
I intend to capture the major triggers consecutively so there is one clear demonstration showing:
Gambling → identification → vendor transactions → Cube/gem transmutation → area/portal transitions → normal gameplay/autosave hitching.
The gambling example in particular should make the severity extremely difficult to miss because the failure can be reproduced repeatedly within seconds.
Please investigate the common transaction/save/validation behavior behind these events rather than treating each visible symptom as an unrelated bug.
The game ran smoothly on PlayStation before these updates.
Six months later, basic systems such as identifying, cubing and even gambling still interrupt or temporarily lock the game.
For an action-RPG built around repeatedly looting, identifying, crafting, buying, selling and gambling items, that is not a minor cosmetic defect.
It directly breaks the normal gameplay loop.