Destiny 2 Crossbow Bug Yeets Bosses Into Orbit | BuyBoosting

Bungie shipped a patch. Players found a better bug.

Update 9.7.0.2 was supposed to be a quiet one. A few number tweaks, a Crossbow adjustment, the usual mid-season housekeeping nobody screenshots. Instead, within about three hours of the servers coming back up, my whole clan Discord was just clips of raid bosses getting punted into the skybox like a Rocket League ceiling shot. Glorious.

The Patch That Broke Gravity

Here's the short version. The Crossbow bolts were supposed to get a damage and projectile fix. What actually happened is the bolts now apply a chunk of physics impulse to anything they hit that isn't anchored.

And bosses, it turns out, are not anchored.

The Carnage Is Real

So now you've got people one-tapping a major in a Lost Sector and watching it sail forty feet straight up like it just got dunked on. Wild. The thing is, this isn't even the funny part for raiders.

The funny part is what it does to mechanics. Half the encounters in this game are scripted around a boss standing in a specific spot, right? Plate phases, damage windows, add spawns timed to position. Launch the boss out of its arena and the script just... shrugs. I watched a clip where someone bolted a boss clean out of the damage zone and the DPS phase soft-locked because the game didn't know where its own raid boss went. honestly that's the most Destiny thing I've seen all year. Bungie's spaghetti code holding the whole sandbox together with duct tape and prayer, and one Crossbow bolt yanks the tape off.

Not even close to the first time, either. I said this last patch and I'll say it again: physics impulse and boss AI have never been friends in this engine.

Why Your Trials Climb Should Care

OK so you're thinking, cool meme, but I'm a PvP player, why do I care? Fair. Here's where it gets interesting. The same impulse change touched Crossbow behavior in the Crucible, and right now the bolt is doing something weird with hit registration on lateral strafes. Translation: peek angles you thought were safe are not safe this week, and a good Crossbow main is abusing it before the hotfix lands.

So the meta read is simple. If you main a slower primary, you're getting clipped from ranges that didn't used to work, and your usual W-key peeks into chokes are coin flips until Bungie reverts this. Adapt or eat dirt.

Look, the honest read on Destiny is that half of climbing Trials is just not gambling on chaos you can't control. You can learn every angle, master the Crossbow timing, hit the gym on your movement — and still get hardstuck because your random teammates third-party the wrong fight every single round. I mean, the bug is funny. Your card going 0-3 because someone refused to trade is not. If the solo queue lottery is what's keeping you off Flawless, the Destiny 2 boost exists for exactly that — skip the coinflip, get the loot, actually enjoy the game again.

What Bungie Does Next

They hotfix it. Obviously. A bug that can soft-lock a raid DPS phase is a day-one revert candidate, no question.

But here's my read on the timing. Bungie loves to let the funny ones marinate a couple of days when they're not actively breaking progression, and the community clipping bosses into orbit is free marketing for a mid-season patch nobody talked about. So they'll wink, post a "we're aware" tweet, and quietly leave it live through the weekend.

And like, who's mad about that? The raiders who want clean clears use the workaround — just don't shoot the boss with the Crossbow, genius — and everybody else gets a week of yeeting majors into the sun.

The Verdict

This is Destiny at its most Destiny. A patch meant to fix one weapon accidentally turned the Crossbow into a gravity gun, and the game is more fun for it. Bungie's engine is held together by vibes and that's exactly why these moments happen.

Prediction: hotfix lands within five days, the boss-launch tech gets patched, and the Crucible hit-reg jank stays live a full extra week because Bungie won't notice the PvP side until the Trials crowd screams loud enough. Screenshot this.