You must be signed in to perform this action.
Bug: Agitating Spark Burn Effect Not Spreading Correctly After Initial Application
128 °C
Bug #1687

Agitating Spark Burn Effect Not Spreading Correctly After Initial Application

Status: New
Priority:
High
Added by:
lovelyshiny
on December 13, '25
Assigned to:
Unassigned
Due date:
Reported for:
0.1.0 Auto
Roblox Id:
1283671248
Roblox Username:
ShinyMewTwoyxzALT
Slot:
Not set

Steps to Reproduce

No steps to reproduce

Explanation

  • Agitating spark as we all know spreads burn effect to eligible targets, including yourself. This means attacking an already burning enemy should spread the burn to you. If there is no eligible target to spread the burn, the burn remains on the opponent and agitating spark goes on a 1 second cooldown instead of a 3 second cooldown. This is not a bug, just an overview of what is expected to happen with agitating spark (confirmed to be intentional)

  • However, after taking a closer look, when the burn is spread again after the initial application of it from the original move, it no longer spreads correctly (does not apply the burn effect to anyone, even with an indicator that shows it's been spread). After attacking a burning enemy, the burn effect is to be cleansed off the opponent and is supposed to applied back onto the user (OR ANY ELIGIBLE CHARACTERS AROUND), but the effect actually doesn't apply back to the eligible characters (shows indicator), making it seem like the burn just disappears. (All done with no burn immunity)

  • This is also proven not to be this feature: 'if a burn life has been applied to a user it cannot be re-applied to them again'. This was tested via applying burn from far away so it does not spread to the user which means the user hasn't been exposed to that burn lifetime yet. Then we check with agitating spark and hit the burning enemy, which again shows the burn indicator being spread (with the cd being 3 seconds aka the user is eligible to be burned), ending up in the burn effect not applying to the user.

This is all thoroughly explained in the video below in case you don't want to read all of this (it gets confusing.)

https://youtu.be/xuY7tFI8mBY

Watchers

Screenshots
Video Clips

None

Log Files

None

Device

No device information

[ #1 ] 21 days ago by
[ #2 ] 21 days ago by

These are all posts about agitating spark removing burn on hit which is an intentional feature, this bug report is compeltely different

[ #3 ] 21 days ago by

trust me aswqe, i would know if im reporting something which is already known.

[ #4 ] 21 days ago by

I know the explanation is long lmao but the video will explain it easily TLDR, burn effect is not being applied back to the user correctly even with indicator

[ #5 ] 21 days ago by

couldnt be me

[ #6 ] 21 days ago by

agitating spark

[ #7 ] 21 days ago by

Im sure yugi2003_ would understand this

[ #8 ] 21 days ago by

So is the emporer flames burn "consumption" mechanic proccing without emporer flames

[ #9 ] 21 days ago by

except everyone has emperor flames and it only does that with agitating spark spread flames

[ #10 ] 21 days ago by

doesnt consume, just doesnt even apply the burn

[ #11 ] 21 days ago by

is it supposed to apply it on urself

[ #12 ] 21 days ago by

yes

[ #13 ] 21 days ago by

but it consumes it

[ #14 ] 21 days ago by

yes it consumes the burn on the opponent to spread it to you

[ #15 ] 21 days ago by

I proved this in the video by showing the agitating spark cooldown is 3 seconds as well as a trail indicator of flames moving towards me

[ #16 ] 21 days ago by

when agitating spark goes on a 3 second cooldown, it means there is an eligible target to spread the flames to, which in this case was the user

[ #17 ] 21 days ago by

1 sec cooldown means no eligible target, flame not consumed on opponent

[ #18 ] 21 days ago by

so the burn is supposed to go from the target to u after u m1 the target but it disappears as if u have emperor flames

[ #19 ] 21 days ago by

you can see it like that, yes

[ #20 ] 20 days ago by

yugi2003_ wsp, could we get confirmation on this rq if possible

[ #21 ] 20 days ago by

busy rn

[ #22 ] 19 days ago by

yugi2003_ available to confirm this? <:destroyman:1092579322537201755>

You need to join this project to comment on issues. Join Project