Barrage feels bad against objects.
Not bosses.
Not elite packs.
Not some nightmare meat wall with three affixes and a personal grudge.
Objects.
A fresh Blizzard forum thread has players asking whether Barrage is still weak or awkward against destructible targets, objective objects, portals, exploding masses, and other non-enemy targets that Diablo 4 keeps placing inside actual gameplay loops.
Which raises a very fair question:
Why does a skill that can fill the screen with arrows sometimes feel like it has a personal problem with furniture?
Barrage Is Supposed to Feel Fast and Fluid
Rogue is one of Diablo 4’s sharpest classes when it feels right.
It is fast, mobile, precise, and just a little smug about it. A good Rogue build should feel like a knife fight happening at sprint speed while the rest of Sanctuary is still looking for its boots.
Barrage fits that fantasy on paper.
Fire a spread of arrows. Hit multiple enemies. Move. Repeat. Keep pressure up. Turn the screen into a very expensive pin cushion.
Against packs, that can feel great.
But when the game asks Barrage players to destroy objects, interact with objective targets, or burn down non-standard entities, that smooth feeling can start to fall apart.
The Problem Is Not Just Damage
This is where build-feel matters.
Players are not only asking whether Barrage has enough raw damage. Raw damage is easy to argue about. Diablo players can argue about damage numbers until the sun burns out and someone still says “skill issue” in the final comment.
The bigger issue is targeting and reliability.
If a skill feels good against monsters but clumsy against objects, then every objective involving objects becomes a little speed bump. Exploding masses, portals, Undercity time bonus objects, Nightmare Dungeon destroy objectives, environmental targets, event props, whatever strange little thing the game decides must die before progress continues.
Those moments are not side content when they block a run.
They are the run.
So if Barrage struggles there, Rogue players notice.
Diablo 4 Keeps Making Players Kill Things That Are Not Really Enemies
Part of the frustration comes from Diablo 4’s own activity design.
The game loves objects.
Destroy the thing.
Click the thing.
Break the thing before the timer gets rude.
Kill the portal.
Pop the mass.
Smash the objective while monsters do their best to turn your character into wet paper.
That structure is everywhere in Diablo 4’s seasonal and endgame content. It appears in dungeons, events, Undercity-style activities, Infernal Hordes-style encounters, and objective-based loops where players need their build to work against more than just enemies with legs.
So “bad against objects” is not a niche problem.
It is a recurring tax on the build.
Barrage Should Not Need a Second Personality
The annoying part is that players often end up mentally separating their build into two modes:
The fun mode, where Barrage shreds monsters.
And the awkward mode, where the build has to deal with some stationary target that does not behave like the rest of the game.
That feels bad.
A core skill should not suddenly feel like it needs a backup plan just because the target is a portal instead of a demon. If the game asks a build to destroy objective objects, then those objects need to interact cleanly with the skills players are actually using.
Otherwise, it stops feeling like combat and starts feeling like the Rogue is trying to negotiate with scenery.
Season 14 Makes Object Problems More Visible
Season of Death Awakening is already busy enough.
Blizzard’s Season 14 overview is packed with systems: Pandemonium Ruptures, Deathtoll Chambers, War Plans, Party Sync, Solo Self Found, Mythic Uniques 3.0, Superior Lair Keys, new boss reward structures, and more.
That means players are moving through a lot of activity types quickly.
The more systems the season adds, the more likely players are to run into weird skill interactions. A build might feel amazing in one loop, then suddenly awkward in another because the target type changes from “monster” to “object that somehow has more emotional armor than a demon lord.”
That is why this kind of Barrage complaint matters.
Season 14 is not just testing damage.
It is testing whether builds feel consistent across all the little pieces Blizzard has bolted onto the endgame.
Rogue Mobility Makes the Clunk Feel Even Worse
Rogue players are especially sensitive to this because Rogue is supposed to feel smooth.
The class fantasy is momentum. Dash in, fire, reposition, evade, punish, disappear, repeat. When Rogue works, it feels like violence with choreography.
So when Barrage hits an object and suddenly feels clumsy, that contrast is brutal.
It is like watching a sports car fly down the highway, then stop dead because someone placed a folding chair in the lane and the car needs three attempts to understand it.
That is not the fantasy.
Rogue should not feel elegant against demons and confused by props.
This Is the Kind of Issue Patch Notes Often Miss
Balance patches tend to focus on big numbers.
More damage.
Less damage.
Cooldown changes.
Scaling adjustments.
Legendary aspect tuning.
All of that matters, obviously. But the feel of a skill often lives in smaller interactions. Targeting rules. Projectile behavior. Object hit detection. Whether a stationary objective counts properly. Whether arrows spread in a useful way against non-monster targets. Whether the skill wastes its potential because the object does not behave like an enemy pack.
Those things rarely look exciting in patch notes.
They are not headline changes.
But they can decide whether a build feels polished or cursed.
Players Do Not Want Barrage to Break the Game
This is not a demand for Barrage to delete every object in one click while Rogue players sip wine and judge the rest of the class roster.
Players are not asking for objective targets to become irrelevant.
They are asking for basic consistency.
If a skill can kill monsters efficiently, it should not feel randomly awful against required objects. If Diablo 4 wants objectives to matter, those objectives should support the same combat language the rest of the game uses.
That means skills need to hit them cleanly.
Not perfectly.
Cleanly.
The Object Problem Is Bigger Than Barrage
Barrage is the current discussion, but the issue points to a broader Diablo 4 problem.
Objects have always been a little strange in ARPGs. Some builds melt them instantly. Some builds treat them like they are cursed with legal immunity. Some skills behave beautifully against mobs and then turn into wet noodles against a stationary thing that the dungeon insists must be destroyed.
That creates uneven friction between builds.
And friction like that feels bad because it is not really about build identity.
A build being weak at single-target is one thing.
A build being strong at AoE but weaker at bosses is understandable.
A build being good at killing demons but awkward at killing a glowing objective barrel is just annoying.
That is not a meaningful trade-off.
That is the game stepping on its own shoelaces.
Blizzard Should Look at Object Interactions More Closely
The fix may not be as simple as “buff Barrage damage.”
It might involve object targeting rules, projectile spread behavior, hitbox size, how objective targets receive damage, or whether certain skills need special handling against non-enemy entities.
That is not glamorous work.
But it is important work.
Because ARPG builds live or die by feel. If a build feels smooth in combat but clunky whenever the activity asks for an object kill, players will eventually avoid either the build or the activity. Neither outcome is good.
Diablo 4 does not need every skill to be equally perfect everywhere.
But it does need required objectives to stop exposing awkward mechanical gaps.
Let the Arrows Hit the Thing
Rogue players are not asking for the moon here.
They are asking for Barrage to feel less weird when Diablo 4 tells them to destroy something that is not technically a monster.
That is a fair ask.
Season 14 already has players wrestling with Mythic crafting rules, War Plan bugs, gem salvage problems, loot filter anxiety, cache issues, Pit hazards, class bugs, and enough endgame systems to make a demon accountant blush.
The last thing Barrage players need is to lose momentum because an objective object apparently has a private feud with arrows.
Diablo 4’s Rogue should feel sharp.
Fast.
Fluid.
Dangerous.
Not like a professional assassin who can murder demons but gets confused by a portal.
Sources: Blizzard Forums: Is Barrage still really bad vs. objects?, Blizzard: Hunt the Death Cult in Season of Death Awakening






