I was scrolling X when the reply from the Destiny2Team landed: the last scheduled patch had been pushed off the calendar. You felt it the same way I did — a small, sinking recalculation of plans and hopes. In a single thread the future of fixes, and the people who built them, became unsettled.
The studio confirmed the delay publicly on X and in a Reddit thread, explaining that several fixes came from developers affected by Thursday’s layoffs. The post called it “not a forever delay,” and promised the team would ship the patch “when possible,” but gave no timeline.
A terse post on X arrived late last night.
The notice was short and clinical: layoffs, fewer hands, and a postponed patch. I’ve followed studio communications long enough to know that when priorities change this quickly, triage replaces polish. Bungie had to choose which problems to chase and which to disable outright — a painful calculus when the clock and headcount both run out.
Why was the Destiny 2 patch delayed?
Because the patch contained fixes authored by people who were part of the layoffs, some work simply vanished with their desks. You should read the team’s posts on X and the follow-ups on Reddit to see the raw thread of decisions: reassign, rewrite, or remove features. With Monument of Triumph declared the end-of-service release, the studio said especially thorny issues might be switched off rather than surgically fixed.
Players are still exploiting Insurrection Prime with Divinity on the Last City rooftop.
The most notorious holdout is the Divinity cheese against Insurrection Prime — a mechanic that cages the boss and bypasses shield immunity. Bungie was investigating a fix, but the compressed schedule meant a patch-ready solution may not have been found. At one point the team weighed disabling Divinity inside the Insurrection Prime Pantheon entirely while they evaluated trade-offs.
Divinity, the community calls it a shortcut; the studio has to decide whether to close the shortcut or leave the door open and accept the damage to intended encounters. That choice is a symptom of a larger problem: with fewer engineers, every minute spent chasing one exploit is a minute not spent on another.
Will Bungie disable Divinity in the Pantheon?
They publicly said they were “running through the pros and cons” of a disable. Disabling a weapon or activity is a blunt tool, but it’s sometimes the quickest way to restore balance when you don’t have the staff for a targeted fix. You’ll see that debate play out on X, Reddit, and in clips on YouTube as players test limits and developers triage responses.
Monument of Triumph shipped on June 9 and left a messy list of interactions.
Between bosses that can be shoved off cliffs and artifact perks that stack into absurd damage, the update delivered both spectacle and instability. Some problems were patched on Tuesday after a brief period of carnage — Bungie let a few of the exploits remain for a short while, giving players a last run of over-the-top moments before repairs.
Other issues — Gambit kills not properly healing the Primeval, Vanguard reputation gains falling far short — were met with a sober message: “cannot promise a fix.” That line reads like a staffing problem in plain text. With Monument of Triumph as the studio’s final update, the team faces two grim options for the remaining bugs: find fixes with a skeleton crew or flip switches that disable affected features.
When will the patch arrive?
The team declined to give a date. Their message was that the delay is temporary, but only “when possible” was promised. You and I both know that “possible” depends on headcount, morale, and the inertia of code left behind by departing engineers — factors that don’t map cleanly to a calendar.
I’ve watched studios weather hard cuts before. This is not just a scheduling problem; it’s a morale problem, and morale is contagious inside a codebase. The remaining developers will carry both the workload and the emotional weight of losing colleagues, which slows everything down and sharpens choices.
The patch pipeline now feels like a house of cards: one removed card and the structure needs rethinking. The Divinity exploit has become a jammed gear in the machine that either needs delicate surgery or blunt force to stop.
I’ll keep tracking announcements on X, Reddit threads, Bungie posts, and reports from outlets like Moyens I/O and YouTube creators who log every new interaction. You should follow those channels if you want real-time signals, but expect updates to arrive in fits and starts as the team recomposes. Do you think Bungie can balance honoring the live community experience with the grim arithmetic of layoffs?