A small tracker bug can still make the whole grind feel sketchy
Diablo Immortal has a fresh post-update annoyance on its hands, and this one hits a system players watch closely. A bug-report thread posted on April 1 says the game’s Gem Find Tracker is showing numbers that do not line up with what players are actually finding, with the in-game party buff and the Codex tracker apparently telling two different stories. The thread stayed active into April 4 on Blizzard’s bug-report board, so it is not just a one-minute complaint that disappeared into the void.
That matters because gem tracking is not cosmetic fluff in Diablo Immortal. Players use those counters to measure whether they are hitting daily limits, whether a run paid out properly, and whether event bonuses are actually doing what they are supposed to do. If the tracker starts lying, even a little, the whole reward loop starts to feel slippery.
What players are reporting
The clearest report says the player’s 4-man party buff claimed they had found 5 bound gems that day, while their Codex Gem Tracker showed 11 daily gems found instead. The player specifically says the issue is not about their final totals matching after one last drop. The real complaint is that the display itself seems inconsistent and confusing, especially around the way bound and unbound gems are being counted.
A second Diablo Immortal bug thread, posted the next day, points to the same general problem. That player says after their first few daily gem drops, the icon was showing the wrong split between bound and unbound gems, even though their actual drops did not match what the counter was claiming. That follow-up thread explicitly references the earlier Gem Find Tracker report, which makes this look less like one strange screenshot and more like a pattern players are noticing after the update.
Why this is worth covering
On Blizzard’s Diablo Immortal bug-report index, “The Gem Find Tracker seems BUSTED after the update” was still sitting among current active topics on April 4, alongside other fresh reports. That does not prove the bug is widespread across the whole player base, but it does show the complaint is current enough to be part of the live post-update bug chatter.
There is also a decent theory floating around from Reddit: one player suggested Blizzard may have been trying to prepare the gem counters for the incoming Winds of Fortune event and ended up creating a mismatch in the display. That is still community speculation, not an official explanation, but it is at least a plausible read on why the tracker would suddenly start acting weird right after an update.
When the counter becomes the problem
This is the kind of bug that sounds small until you remember how much live-service games rely on trust. If players cannot tell whether their gem drops are being counted correctly, they start second-guessing the run, the event, and the system itself. Diablo Immortal does not need more uncertainty in a rewards economy that already asks players to watch numbers like hawks. A tracker is supposed to remove doubt, not become part of it.
