Original Post — Direct link

In a few weeks, we will be approaching the One Year Anniversary of this bug.

I would consider this bug as a “big” issue since it does not work with a lot of perks/mods on the game. This glitch is much bigger than the Caliburn’s Hand Bug or the Liar’s Handshake Bug since it affects the interaction with many Exotics.

It would be nice if the Destiny 2 Team or BNGHelp sees this post like how Ghaul wants to be seen by the Traveller.

Issue Explained Celestial Fire’s Scorch/Ignition is missing the property where it is credited as a Solar Melee Ability damage. This was “broken” since Season of the Haunted, the season where Solar 3.0 debuted.

Celestial Fire Melee damage consists of:

Base Damage (The three projectiles.) Scorch Damage (The burn applied by each projectile.) If the damage from Celestial Fire’s Scorch/Ignition kills the target instead of the base damage, it will not be considered a Solar Melee kill to activate any Melee-Related Weapon or Armor Perks/Mods, such as:

Sunbracers Exotic Armor Perk Necrotic Grips Exotic Armor Perk Felwinter’s Helm Exotic Armor Perk Winter’s Guile Exotic Perk Karnstein Armlets Exotic Armor Perk Impact Induction Armor Mod Focusing Strike Armor Mod Heavy Handed Armor Mod Hands-On Armor Mod Swashbuckler Weapon Perk Grave Robber Weapon Perk Golden Tricon (X2) Weapon Perk Pugilist (Handling Boost refresh on melee hits) Weapon Perk Any other Perk that is related to Melee hits/kills. With the exception of Celestial Fire, the Scorch/Ignition damage from all Solar Grenade Abilities, Solar Melee Abilities, and Weapons with Incandescent Perk is registered as their respective source damage. This allows the Scorch/Ignition of these Solar Abilities to activate weapon and armor perks if the scorch damages or kills the afflicted target.

If the target is afflicted with Ignition, the Solar Ability that applies the first Scorch stacks on the target will be credited as the source damage of that Ignition. Example: If I singed a target with a Knife Trick Melee first and throw a Solar Grenade to cause an Ignition, that Ignition damage will be considered Solar Melee damage.

Scorch lingers on a target for 4 seconds before decaying 10 stacks per second.

Using an Ability to singed a target with ~30 Scorch stacks or higher can activate the following Mods a second time after those Mod’s internal cooldown of 7 seconds between activation:

Impact Induction Focusing Strike Momentum Transfer Bolstering Detonation This feature is amazing and intended as the Scorch damage is an extension of their source ability damage.

Since Celestial Fire is bugged, the Armor Mods, such as Impact Induction and Focusing Strike will not activate a second time. You have to use Incinerator Snap.

So in theory, the continuous damage from the Solar Melee’s Scorch will always keep the Handling bonus from the Pugilist Perk active until the Scorch ends. But since Celestial Fire is bugged, this will not work.

Or if the Scorch from Celestial Fire kills the target, you will NOT get the bonus Super energy from the Hands-On Helmet Armor Mod.

Another strange bug in activities that Level Capped you, such as GMs, Legendary Campaign:

With Ember of Ashes, using Celestial Fire and a Fusion Grenade will not create an Ignition? The math adds 105 Scorch stacks:

  • Celestial Fire = 45 Scorch Stacks
  • Fusion Grenade = 60 Scorch Stacks
  • Celestial Fire + Fusion Grenade = 105 Scorch Stacks

But for some reason, using that same combo will work in non-Level Cap activities.

Cause Of The issue Celestial Fire originally did not apply Scorch when Solar 3.0 debuted during the start of Season of the Haunted.

After hearing the public outcry about how Solar 3.0 was not up to the community's expectations, Scorch being added to Celestial Fire was one of the hasty sandbox improvements implemented by Bungie. However, it was rushed and the poor developer who coded it forgot to add the same Scorch properties as the other Solar Melee abilities, such as Incinerator Snap.

External link →
about 1 year ago - /u/BNGHelp - Direct link

Thanks for the report. We're currently investigating this issue.