Bug: Fire Bolt OC fails to properly raise temperature on enemies under Conductive Thermals OC
Bug #999
Fire Bolt OC fails to properly raise temperature on enemies under Conductive Thermals OC
| Status: | Open |
| Priority: |
Medium |
| Added by: |
|
| Assigned to: |
Unassigned
|
| Due date: | |
| Reported for: |
Steps to Reproduce
- Get a scout with "Conductive Thermals" Overclock on Plasma Carbine, and "Fire Bolt" Overclock on Boltshark
- Target either a Glyphid Praetorian or Glyphid Oppressor, best if lone, then splash a good amount of plasma bullet on it
- Shoot the target with one or two fire bolt
- Target's temperture would start rising, but disperse once reach a certain point, unable to enter "On fire" status effect
- The whole "heating then disperse" action would restart multiple times, until the bolt dies out or plasma effect wears off
Explanation
When large enemies such as Praetorian or Oppressor are under the effect of Conductive Thermals OC, the Fire Bolt OC can not raise their temperature meter properly.
When a fire bolt is attached to the body of the aforementioned bugs, the temperature meter would rise to a certain value, then refresh to zero. The whole heating process would then start all over again, unable to give the "on fire" status effect on its own. Eventually, either the bolt dies out, or any exterior temperature source (such as nearby burning bugs) starts the on-fire effect properly.
If the bolt is on the ground, the same phenomenon occurs, partially raised, then dies down instantly. I also tried it on solo, still the same.
I recall this phenomenon would also appear on other enemies, but these two had the most noticeable gameplay impact, especially in the frost biome.
From what I've observed, Fire Bolt and Conductive Thermals are behaving weirdly with each other. Other than this heat-disappear issue, there are also times when you expect your target to heat up faster after a good splash, but it ends up rising slowly.
Watchers
Screenshots
None
Log Files
None
Device
No device information
You don't have permission to comment on this issue.