Diablo IV’s The Tower and its competitive leaderboards debuted with Patch 2.5.2 on January 12, 2026, promising a fresh competitive endgame challenge that ranks players based on speed and score. This new beta system has been one of the most anticipated features of Season 11, but many players are now searching for answers as score tracking issues and leaderboard bugs have emerged almost immediately after launch.
In this article, we’ll cover:
🔹 What’s currently bugged and what isn’t
🔹 How Blizzard is responding
🔹 What players should track while bugs are active
And most importantly, how to stay ahead of the curve instead of getting frustrated. Let’s break it all down.
What Exactly Is The Tower & Its Leaderboards?
Before we dig into the issues, a quick refresher:
The Tower is a timed endgame dungeon where players fight through multiple floors, collect progress through kills and Orbs, and compete for leaderboard placement based on completion time and tiers. It’s built to push Diablo IV players into high‑skill territory, offering bragging rights and competitive depth previously missing from the game.
Leaderboards are split by:
-
Solo vs. party
-
Game mode (Hardcore vs. Normal)
-
Class
-
Platform filters (PC/console)
Rounds are scheduled in two‑week cycles throughout Season 11.
Major Leaderboard Bugs After Launch
Despite the official release, players quickly began reporting issues in both official and community channels:
1. Scores Not Populating Correctly
The most widespread issue is that leaderboard results are not showing properly for all players or classes right now. Many players have completed The Tower successfully — and even seen in‑game completion screens — yet their run fails to appear on the leaderboards.
This has caused confusion and frustration among competitive players who expected instant score tracking.
2. Backend Tracking Errors
It appears the issue is not gameplay‑breaking — runs still complete normally — but rather a data reporting/display problem on leaderboards. Reports indicate the system may not be recording results properly for some players, especially when switching filters or viewing certain classes.
Players are still able to access The Tower and climb floors, but their results may not show up reliably on leaderboards.
3. Community Reports Reflect Confusion
Across Reddit and forums, players have voiced similar issues. Many confirmed that the leaderboard doesn’t reflect their run even after they completed it, while others mentioned additional unrelated bugs such as skills malfunctioning after the update (e.g., Paladin Judgment interactions).
What Isn’t Broken — Yet
Despite leaderboard bugs, The Tower itself is fully playable. Players can still:
-
Enter and run floors
-
Fight monsters and collect Orbs
-
Trigger pylons and reach bosses
-
Complete runs locally and normally
The core gameplay loop is unaffected — the bugs live in the leaderboard recording and display layer.
Many users on Reddit also confirm they can enter and play The Tower successfully with the latest update — it’s specifically the leaderboard backend that’s malfunctioning.
Blizzard’s Official Response — What We Know So Far
Blizzard Community Managers have acknowledged the problem. According to posts on Blue Tracker and other official feedback channels, the team is actively investigating an issue that is causing leaderboard results to not display correctly for all classes.
Key points from Blizzard’s response:
-
The Tower is a beta feature — bugs are expected in early rollout
-
Leaderboard recording issues are known and under investigation
-
No fix ETA has been provided yet
-
Developers are asking for player feedback via official forums and subforums
This acknowledgement — while still early — confirms the issue isn’t unique to specific platforms or player error; it’s on Blizzard’s radar and will be addressed in future patches or hotfixes.
Timeline & What Blizzard Has Said About Future Fixes
Since this is labeled a beta leaderboard system, Blizzard intends to refine the feature over upcoming hotfixes and patches. The official patch announcement indicated that The Tower and its leaderboards are expected to evolve over multiple seasons, and that player feedback is part of shaping its future.
Scheduled leaderboard rounds (e.g., January 12–26 and January 26–February 9) may also influence when leaderboard bugs must be resolved so that players aren’t disadvantaged mid‑season.
None of the official statements provide a firm date for leaderboard fixes, but both Blizzard and community managers have reiterated that because this is a beta feature, issues will be worked on and improved over time.
What You Should Track While Bugs Are Active
Here’s how to stay competitive and make sure your best runs aren’t lost in the glitch:
🔎 1. Record Run Screenshots/Videos
Capture your final time and tier reached in screenshots or short clips before exiting a run — this gives you a record of your performance in case the leaderboard doesn’t log it properly.
📊 2. Check Multiple Filters
Some players report that scores appear under certain filters (e.g., specific class, mode) and not others. Try switching filters if your run doesn’t immediately show.
📡 3. Monitor Official Patch Notes
Keep an eye on official Blizzard patch notes and forums for leaderboard or beta system updates in hotfix releases or future patches.
🗣 4. Follow Community Feedback Threads
Reddit threads and forum posts often surface new issues and workarounds faster than official channels — use them to stay updated on affected classes or conditions.
Community Reaction — Mixed Feelings
Player sentiment is split. Many are disappointed that the much‑anticipated competitive leaderboards launched with bugs, while others remind the community that this is a beta feature, and some hiccups are expected.
Some players feel that without rewards beyond prestige, The Tower lacks incentive, which intensifies frustration when leaderboard scores don’t register properly.
Other players understand the bugs as part of the iterative process and encourage patience while Blizzard resolves backend issues.
Regardless of stance, community discussion itself fuels search traffic and makes this topic highly relevant for readers right now.
Is This Just a Display Bug or a Deeper Problem?
Current reports and Blizzard’s own feedback suggest that the leaderboards issue is mostly data reporting/display related, not fundamental gameplay breaking. Runs still complete properly; they just may not appear reliably on leaderboards yet.
This is often seen in early beta leaderboard systems in other games — the challenge for Blizzard is ensuring accuracy and fairness once competitive rankings matter more.
Conclusion — What Players Need to Know Right Now
Diablo IV’s new Tower leaderboards beta brings competitive endgame excitement, but it also arrives with significant leaderboard bugs that impact score recording and visibility.
Key Takeaways
✔ The Tower runs are playable but leaderboard results may not log correctly.
✔ Blizzard acknowledges the issue and is investigating fixes without a set ETA.
✔ This feature is in beta — bugs are expected and player feedback matters.
✔ Players should record their run results manually and monitor filters for visibility.
Staying updated, sharing feedback, and preparing for leaderboard fixes will give competitive players an edge once issues are fully resolved.
👉 Next recommended reads:
Comments
Post a Comment