The player is understandably not delighted. In a new Diablo IV forum post about the Tower closure, they say the shutdown arrived without a clear in-game warning or visible countdown and effectively ended their competitive Season 14 push before they expected it to end. They describe having a build hitting around 424 trillion damage, with further theoretical scaling available, and believed the new setup was capable of getting them inside the Top 100.
Whether it actually would have done so is unknowable now.
Which is rather the problem.
400 Hours Came Down to One Final Push
The player says they had invested close to 400 hours during Season 14, with the Tower becoming the main purpose of that grind. They had already reached rank 119 globally, then slipped to 167 as other players improved their own runs. Rather than accepting the drop, they started rebuilding specifically for another attempt. New gear. More optimization. More calculations. More farming. The sort of endgame behaviour where Diablo stops being a game about killing demons and quietly becomes a spreadsheet that occasionally screams.
The stated goal was simple: finish inside the Top 100.
That matters more in Season 14 because the Tower is no longer merely a beta experiment. Blizzard officially moved Tower and Leaderboards out of Beta and attached meaningful ranking rewards to them. Players can earn rewards for participating, reaching Tower Tier 100 and finishing inside the Top 1,000, Top 500, Top 100, Top 10 or rank #1, with Halo cosmetics and Prestige Titles tied to performance.
We already looked at why that changes the conversation in our article asking whether Diablo IV's Tower leaderboard measures player skill or simply better RNG. Once Blizzard puts exclusive rewards and visible rankings behind a mode, players will inevitably treat those rankings seriously. Rank 101 is no longer merely one number below rank 100. It can represent a different reward tier.
But Was the Tower Actually Closed Early?
This is where the complaint becomes more complicated.
The original poster describes the Tower as being closed roughly two weeks before the end of the season and argues that the finish line was moved without warning. Another player in the same discussion immediately pushes back on that interpretation, saying leaderboard runs operate in two-week cycles and that the Tower also closes around patches, adding that the same thing happened last season.
The original poster accepts that context but argues that this is precisely the problem. A competitive system should not require players to remember what happened last season, infer the schedule from patch timing or learn the rules through forum replies after the door has already closed. Their suggestion is extremely simple: put a visible countdown inside the Tower interface.
That feels like the stronger argument.
If the closure happened exactly according to Blizzard's intended schedule, then this is not really a story about Blizzard unexpectedly changing the rules. It is a story about those rules apparently not being communicated clearly enough to someone who spent hundreds of hours competing under them.
We Have Already Seen This Problem With the Tower
Unfortunately, the Tower and calendars have met before, and the relationship has not always been romantic. Earlier this year, we covered players discovering that Tower-related seasonal objectives remained visible while the Tower itself was closed. That produced a remarkably similar question: if content becomes unavailable according to a schedule, how clearly should the game communicate that schedule to players whose progression depends on it?
We have also seen smaller rule and reward problems around the mode. A Season 14 bug meant Tower rewards could behave incorrectly for party members while Solo Self-Found visibility was also broken. None of these issues means the Tower itself is a failure. In fact, the intensity of the current complaint suggests almost the opposite. Players care enough about the mode to spend hundreds of hours optimizing for it.
That is valuable.
It also means the boring administrative parts suddenly matter enormously.
A Competitive Leaderboard Needs a Visible Finish Line
Diablo IV is never going to be a perfectly standardized competitive game. Gear matters. RNG matters. Class balance matters. Transfiguration rolls can matter enormously, something we have already seen in Season 14's increasingly elaborate Transfiguration endgame. Two players entering the Tower are not starting from identical equipment and being asked to perform the same mechanical test.
But the calendar is different.
Everybody can understand a countdown.
If a leaderboard closes Friday at a specific time, put that time on the leaderboard. If the final competitive cycle ends two weeks before the season itself, state that explicitly. If a patch temporarily disables the Tower, show it before somebody spends three evenings rebuilding an entire loadout for a run they can no longer submit.
These are not balance decisions. They are interface decisions.
And they become particularly important when Blizzard itself has encouraged players to care about specific ranking thresholds.
The Player Did Not Lose 400 Hours, But the Frustration Makes Sense
It would be unfair to say all 400 hours were wasted. The player reached rank 119 globally, competed near the top of the Spiritborn leaderboard and presumably accumulated everything else that comes with playing Diablo IV at that level. A leaderboard position is also never guaranteed merely because a player believes their new gear can achieve it. The Top 100 contains ninety-nine other people with similarly inconvenient ambitions.
But that is not really what the complaint is about.
The player wanted the chance to try.
They built toward a final run because they believed the competitive window was still open. When they were ready, it was not.
If Blizzard's schedule was operating exactly as designed, then the solution does not require changing the Tower season, giving anybody a free ranking or reopening the leaderboard because one player missed the cutoff.
It requires a clock.
Diablo IV already asks its most dedicated players to track gear rolls, Paragon choices, War Plans, crafting materials, boss keys, Transfigurations and enough multiplicative damage modifiers to frighten a mathematics department.
Remembering when the leaderboard quietly locks should probably not be another build requirement.
