Rogue Shadow Clones Turn On Their Owners

By Indie Kings | October 14, 2026

Updated October 14, 2026: Per Duskforge relaying players, Diablo 4 Season 15 Rogue players report that Shadow Clone attacks can kill the Rogue who summoned them, including cases tested against training dummies, and the exact cause remains unclear.

Image: Rogue shadows artwork. Credit: Duskforge.

What players say happened

Per Duskforge relaying players, Rogue players in Diablo 4 Season 15 report that their own Shadow Clone can attack and kill them. The report describes the moment in direct terms. A Rogue is playing, there is no visible enemy nearby, health drops, death follows, and the suspected source is the active clone.

That framing matters because it reverses the normal expectation for a summon style skill. A Shadow Clone is supposed to fight beside the Rogue. It is supposed to copy relevant actions and add damage. In these reports, the clone is described as a liability rather than support. Duskforge uses the phrase go rogue to describe the behavior, which fits the player experience of being hit by a friendly effect.

The same account stresses that players asked an understandable question after these deaths. They asked what just killed them. The relayed answer is uncomfortable. The answer is presented as pretty much your own clone. That wording is important. It is not framed as certain in every death. It is framed as highly likely in the pattern being discussed.

Readers should keep that scope in mind through the rest of this article. This is a report about player reports. Duskforge is relaying Reddit and Blizzard forum reports, not publishing a confirmed mechanical breakdown from Blizzard. The strength of the story is the repeated pattern across players. The limit of the story is that the exact cause is still described as unclear.

The practical takeaway in this section is simple. If a Season 15 Rogue dies with no enemy in sight while Shadow Clone is active, these reports say the clone belongs on the suspect list. That does not prove the clone caused every such death. It means players documenting the issue have repeatedly arrived at the clone after ruling out visible enemies.

Why training dummy reports matter

One verified beat in this story is that Shadow Clone attacks on owners are reported even against training dummies. That detail deserves attention because training dummies change how a player reads a death. In open combat, many effects can overlap. Damage numbers, ground effects, enemy projectiles, and companion attacks can arrive in the same second. A target dummy setting removes much of that noise.

Per Duskforge relaying players, the clone can turn into a liability even against training dummies. That suggests the problem is not only a confused reading of a busy fight. It suggests at least some players saw hostile behavior from the clone in a controlled setting where no ordinary enemy attack should explain the damage.

This does not establish the full trigger. A dummy test can show that self damage happened. It cannot by itself show why it happened. It also cannot show which item, skill rank, charm, mercenary state, or timing detail made the difference. Still, the dummy detail is useful for two reasons. First, it makes accidental misattribution less likely. Second, it gives other players a safer conceptual test to understand: if damage arrives with no enemy present, the friendly clone becomes harder to dismiss.

Players who read these reports should not treat dummy behavior as proof that every Rogue will see the same result. Different builds, different charms, and different companion states may behave differently. The reported point is narrower and still important. At least in the relayed cases, the clone problem was visible enough that dummies did not remove it.

The dummy angle also helps explain why this story spread. A strange death in a Pit or open dungeon can be written off as lag, a missed enemy, or a misread effect. A strange hit in front of a dummy is harder to ignore. It invites a second test, a clip, a post, and then another player saying the same thing happened to them.

Timeline and where reports appeared

Per Duskforge relaying players, the reports discussed here appeared over the last couple of weeks before the October 13 2026 Duskforge article by Jaymo. That timing places the issue inside Season 15 discussion, not as an old report resurfaced from a prior season. The article date matters for readers because seasonal behavior can change with balance changes, fixes, and new items.

The reports are described as multiple reports on Reddit and the official Blizzard forum. That sourcing matters. Reddit can surface clips, short reproductions, and build details quickly. The Blizzard forum is closer to the support and feedback channel where players expect developers to see an issue. When similar complaints appear in both places during the same period, the pattern becomes harder to dismiss as one bad session.

Duskforge is named here as the relay, not as the original discoverer of every case. The correct attribution is that Duskforge relayed Reddit and Blizzard forum reports. That distinction protects accuracy. Indie Kings did not independently verify each forum thread. Duskforge did the relay and editorial summary. Readers who want the primary threads should use the Sources link at the end to reach the Duskforge article and follow its references.

The timeline also helps set expectations. A couple of weeks of reports is enough to establish a pattern worth covering. It is not enough to establish a complete mechanical explanation. That is why later sections keep returning to the same careful phrase. The exact cause is unclear.

For players, the timeline question is practical. If someone died this way earlier in Season 15, these reports suggest they were not alone. If someone has not seen it yet, the reports do not prove they will see it. They show that the issue has been reported repeatedly in recent Season 15 play.

What is known about the cause

The most important limit in the source is also the clearest. It is still unclear what exactly is causing the problem. That sentence should guide every conclusion in this article. There is a strong reported association with Shadow Clone and Aspect of Imitated Imbuement. There is not a confirmed step by step cause.

That distinction matters because players naturally want a fix. They want to know which item to remove, which skill to avoid, or which order of actions is safe. The current relayed state does not provide that certainty. It provides suspects, correlations, and one reported charm swap test. It does not provide a verified root cause.

It helps to separate three levels of knowledge. The first level is the observed outcome. Rogues die and suspect their clone. The second level is the associated setup. Shadow Clone plus Aspect of Imitated Imbuement appears repeatedly. The third level is the mechanism. That third level is missing. Nothing in the relayed aspect text explains self damage, and none of the clone upgrades are described as supposed to trigger self damage.

This gap is frustrating, but it is also normal for a live game bug report at this stage. Players see the outcome first. They compare setups second. The precise interaction may require internal data, broader reproduction, or a developer response. Until then, the honest status is association without confirmed mechanism.

Readers should therefore treat every workaround in this article as reported or suggested, not as a guaranteed fix. The only fully consistent protection described in the source is avoidance: do not use the suspected combination. That is costly, as explained below, but it follows directly from the uncertainty.

Aspect of Imitated Imbuement in plain terms

The Duskforge relay places Aspect of Imitated Imbuement at the center of the discussion. The reported issue is described as definitely related to Shadow Clone and that Aspect. Again, related does not mean fully explained. It means the two elements keep appearing together in problem reports.

The article quotes the practical function of the Aspect in plain terms. Shadow Clones also mimic the Imbuements. Casting an Imbuement Skill grants an active Shadow Clone increased damage within a stated range. The relayed rank one range is 40 to 60 percent increased damage, marked as multiplicative in the source display. Salvage wording and imprint potency wording are also included in the source, but the core combat idea is the mimic behavior plus the damage grant.

In normal play, that design is easy to understand. The Rogue applies an Imbuement. The clone copies the Imbuement behavior. The clone hits harder for the relevant window. Nothing in that description says the clone should redirect damage to the Rogue. Duskforge makes that point directly. There is nothing on the Aspect itself that points toward it suddenly inflicting damage to the player.

The same logic is applied to Shadow Clone upgrades. None of the upgrades should trigger self damage either. That makes the bug harder to explain from text alone. If neither the Aspect text nor the clone upgrades describe self harm, then the reported self harm looks like unintended behavior rather than a misunderstood cost.

This section cannot resolve the contradiction. It can only preserve it accurately. The reported setup points to the Aspect and clone. The readable text does not predict self damage. That mismatch is why the story calls the problem a bug and why players are left testing around it.

Which builds are named in the reports

Per Duskforge relaying players, the builds most directly named are Dance of Knives and Penetrating Shot builds that use both Shadow Clone and Aspect of Imitated Imbuement. Poison versions are specifically mentioned. The source names Poison Dance of Knives and Poison Penetrating Shot as builds that rely on the Aspect and the clones.

That build detail matters because it explains exposure. A player who only occasionally uses a clone is less likely to notice a rare misfire. A player whose rotation depends on clones and Imbuements will summon the suspected combination constantly. More repetitions mean more chances for the reported behavior to appear and more reason to connect deaths to the clone.

The source does not say that only those builds can experience the issue. It says players using those builds might have experienced deaths with no enemies in sight. Readers should not expand that into a claim about every Rogue build. The verified statement is narrower. The named Dance of Knives and Penetrating Shot setups are the ones highlighted in the relay.

Poison is mentioned as the relevant Imbuement family in those examples. That fits the Aspect discussion because the clone is supposed to mimic Imbuements. It does not prove Poison itself is the trigger. It shows the context in which the reports arose. A Poison Dance of Knives Rogue or Poison Penetrating Shot Rogue is a natural user of the exact combination under suspicion.

This site has also covered the one button Rogue build reported as strong enough for Pit 130.

That prior coverage is mentioned here only to place Rogue build discussion in context. The present article is not about that build. It is about the Shadow Clone self damage reports relayed by Duskforge. Readers should keep the two topics separate and not assume the same setup is involved.

Why simply removing the clone is costly

The obvious response to a suspected clone bug is to stop using the clone. The source explains why that choice hurts. Builds such as Poison Dance of Knives or Poison Penetrating Shot rely on the Aspect and the clones, so removing one of them also removes a lot of damage.

This is a classic live game tradeoff. The suspected piece is also a load bearing piece. A Rogue can step away from Shadow Clone or Aspect of Imitated Imbuement, but then the build loses the mimic damage and synergy it was built around. That may mean slower clears, weaker burst windows, or a need to redesign aspects, skills, and supporting choices.

The tradeoff also affects testing. A player who removes the clone may see deaths stop, but that alone does not identify the mechanism. It only shows that the suspected combination was necessary for the observed outcome in that setup. A player who keeps the clone keeps damage but keeps risk, including the reported Hardcore risk discussed below.

For that reason, workaround talk in the community tends to focus on smaller changes first. Players would rather swap a charm than abandon a core skill. The next section covers the one charm swap report that Duskforge relays. It is still only a report, but it shows the direction players prefer: keep the build intact if possible.

The key point for readers is that avoidance is not free. The source is explicit that removal costs damage. Any advice to simply avoid the clone should acknowledge that cost rather than treating it as a minor tweak.

Spellbound Steel Charm and Legacy of the Sightless reports

The most specific equipment lead in the relay concerns charms. Duskforge says there have been reports saying that the Spellbound Steel Charm set might be the actual trigger for the bug. That is careful language. Might be the actual trigger is not confirmation. It is a community hypothesis passed along in the relay.

The suggested response is also relayed. If a player has this problem and has this set equipped, the suggestion is to try swapping for another set such as Legacy of the Sightless. That is presented as something to try, not as an official fix. It is the kind of practical test players use while waiting for a developer answer.

Duskforge adds a small direct test result. The article says the author tried with Sightless, and the clones seem to attack normally with that one. That wording is observational and limited. Seem to attack normally is not the same as proven safe in all cases. It means that in the tried setup, the abnormal behavior was not observed.

Readers should give this lead the right weight. It is more specific than saying the cause is unclear, but it does not replace a confirmed cause. It is still possible that the charm set interacts with the clone in some setups and not others. It is also possible that the improvement came from another changed variable during the swap. The source does not resolve those possibilities.

Still, for an affected player, this is the most actionable detail in the story. A charm swap is cheaper than abandoning Shadow Clone or rebuilding around a different damage source. The honest way to use it is as a test. Swap, observe, and do not assume the issue is gone after one clean session.

It is also worth noting what the source does not say. It does not provide drop locations, full charm stats, or a mechanical reason why one charm set would redirect clone damage. Those details are outside the fetched relay. This article does not fill them in. The verified point is only the reported suspicion and the reported normal behavior after swapping to Legacy of the Sightless.

Mercenaries and Splinter of Terror parallels

Per Duskforge relaying players, Rogue clones are not the only friendly source reported to reflect damage to the player. Hired Mercenaries attacks are also described as often tending to attack their owners. That parallel matters because it changes the shape of the story. The clone issue may not be isolated.

The source gives another specific example. There have been reports of Splinter of Terror fire paths killing the player who uses the Splinter. That is a different effect from a clone, but the outcome rhymes. A player deploys something meant to harm enemies, and the player dies from it.

Duskforge states the broader conclusion directly. It is definitely not an isolated problem. That sentence is about the pattern of friendly or player owned effects harming the owner, not proof that all these cases share one cause. Readers should preserve that distinction. A shared outcome does not prove a shared bug.

Why include the mercenary parallel at all. First, it helps affected players check more than one suspect. A Rogue who uses both a clone and a hired mercenary has at least two friendly sources worth watching. Second, it supports the workaround tone in the source. The relay suggests caution around mercenaries as well as clones.

The Splinter example adds a third check. Fire paths are positional and persistent in a way clone strikes are not, so a player might identify them more easily in a clip. If a Rogue sees death near their own Splinter fire path, that report belongs in the same broader conversation even if the mechanism differs.

Taken together, these parallels suggest players should avoid treating one fix as a cure for every self damage death. Removing the clone may address the clone reports. It may not address a mercenary or Splinter interaction. The source keeps those threads together for that reason.

Why Hardcore deaths raise the stakes

The source includes a short but serious consequence. A few Hardcore characters sadly died from these types of issues. In Hardcore play, death is permanent for that character. There is no respawn and retry on the same hero. A strange interaction is therefore not only annoying. It can end a long term character.

That consequence changes how players should read the workaround advice. In softcore play, a player might keep testing the suspected build and accept occasional deaths while gathering evidence. In Hardcore play, the same testing carries permanent loss. The rational response for Hardcore Rogues is greater caution until the behavior is clarified.

The relay does not name the dead characters, their levels, or their exact setups. This article does not invent those details. The verified point is only that Hardcore deaths are reported in connection with these types of friendly fire issues. That is enough to justify a stronger warning without overstating what is known.

Hardcore risk also explains why dummy reports matter again here. A Hardcore player cannot safely learn through repeated live deaths. A controlled observation, careful clip review, and conservative build choice are more appropriate. The source does not prescribe a Hardcore safe build. It only describes avoidance of the suspected pieces.

Readers in Hardcore should treat the charm swap lead with extra care. A report that clones seem normal with Legacy of the Sightless is encouraging, but seem normal is not a guarantee. For a permanent death mode, a single community test is not enough to declare a setup safe.

Reported response and workarounds

Per Duskforge relaying players, Blizzard has not answered yet. That status is dated to the source article of October 13 2026. It means that within the fetched relay, there is no official explanation, no confirmed fix, and no developer workaround to quote. Readers should check for newer statements beyond that date, but this article does not invent one.

The source also says there is no obvious fix outside of not picking up mercenaries and playing a build that does not involve Shadow Clone or Aspect of Imitated Imbuement. That is a blunt workaround. It tells players to avoid the suspected systems rather than offering a settings change or timing trick.

Naming Blizzard here is required for attribution, but the naming is kept in prose without a hyperlink. The Blizzard forum is one of the two report venues relayed by Duskforge. Blizzard as developer is the party players await a response from. Neither role needs an external link in this article because Sources contains the single external link back to the Duskforge relay.

The workaround has three parts when read carefully. First, do not pick up mercenaries. Second, avoid Shadow Clone builds. Third, avoid Aspect of Imitated Imbuement builds. Each part reduces exposure to a reported friendly fire source. None of them is described as a true fix. They are avoidance steps.

Duskforge closes with hope rather than certainty. The article says hopefully the issue can be fixed for next season, and Rogues can stop getting shot by their own clones. That line is both tone and timeline. It signals that players may need to play around the issue through the rest of the current season discussion if no midseason change arrives.

What affected players can check

This section stays inside the fetched facts while giving readers a practical order of checks. It is not a confirmed repair guide. It is a way to read the reports and apply them without adding new claims.

First, confirm the basic pattern. Was Shadow Clone active. Was Aspect of Imitated Imbuement equipped. Did death or heavy damage arrive with no enemy in sight. Those three questions match the core relay. If all three are true, the clone suspicion fits the reported pattern.

Second, consider the build context. Were you using Dance of Knives or Penetrating Shot with Poison alongside the clone and Aspect. Those are the named examples. Matching them does not prove cause, but it places the death inside the most discussed group.

Third, check the charm variable. Were you using Spellbound Steel Charm. If so, the relayed community suggestion is to try Legacy of the Sightless and observe whether clone behavior looks normal. Treat this as an experiment, not as proof of safety.

Fourth, check companion and effect variables. Was a hired mercenary active. Was Splinter of Terror in use with fire paths near the death location. The source groups those with the clone issue as part of a broader friendly damage pattern, so they belong in the same review.

Fifth, weigh character mode. A softcore Rogue may test more freely. A Hardcore Rogue should strongly consider avoiding the suspected combination until there is clearer guidance. The reported Hardcore deaths make that caution reasonable.

Sixth, watch for new information after October 13 2026. The no answer status can change. A future developer note, patch note, or follow up report could supersede this article. Until then, avoidance and careful observation are the only workarounds relayed in the source.

FAQ

Are Rogue Shadow Clones really killing their owners in Season 15?

Per Duskforge relaying players, yes, that is the reported behavior. Multiple Reddit and Blizzard forum reports over the last couple of weeks describe Shadow Clone attacks harming or killing the Rogue, including cases involving training dummies.

Is the exact cause known?

No. The exact cause is described as unclear. Shadow Clone and Aspect of Imitated Imbuement appear together repeatedly in reports, and a charm set is suspected, but the source does not confirm a root mechanism.

Which builds are mentioned most?

Dance of Knives and Penetrating Shot builds using Shadow Clone and Aspect of Imitated Imbuement are named, including Poison Dance of Knives and Poison Penetrating Shot. Those builds rely on the suspected combination, which explains why reports cluster there.

Does the Aspect text explain self damage?

No. The relayed Aspect function is that clones mimic Imbuements and gain 40 to 60 percent increased damage after an Imbuement Skill is cast. Nothing in that text points to self damage, and clone upgrades are likewise not described as supposed to cause self damage.

What workaround is reported?

The relayed workaround is avoidance. Do not pick up mercenaries and avoid builds using Shadow Clone or Aspect of Imitated Imbuement. A separate charm report suggests trying Legacy of the Sightless instead of Spellbound Steel Charm, with clones seeming normal in that limited test.

Has Blizzard responded?

Per the October 13 2026 Duskforge relay, Blizzard has not answered yet. There is no official fix quoted in the source, so players are left with avoidance and observation until a future update or statement appears.

Bottom Line

Per Duskforge relaying players, Season 15 Rogues have a credible friendly fire pattern to take seriously. Shadow Clone is reported as attacking owners, even around training dummies, in connection with Aspect of Imitated Imbuement, with Dance of Knives and Penetrating Shot Poison builds named most often. The exact cause remains unclear, a Spellbound Steel Charm trigger is suspected but unproven, mercenary and Splinter of Terror parallels broaden the concern, Hardcore deaths raise the stakes, and Blizzard has not answered yet. Until clearer guidance arrives, affected players should treat avoidance as the only relayed protection and treat the Legacy of the Sightless swap as a test rather than a confirmed fix.

Sources

Per Duskforge relaying Reddit and Blizzard forum reports, full details were taken only from the Duskforge article by Jaymo dated October 13 2026.

Duskforge: Diablo 4 Season 15 Rogue Shadow Clones Kill Their Owners