C4 Inconsistancy (detonation timing)

[RickAvory]

I have noticed that the detonation time for C4 has been a bit odd for some time now. There will be times where you can set it off instantly and there will be times where there is a large cool down. After a lot of testing I’m not sure how to replicate this bug at all. Someone let me know if you can shed light about this issue.

EDIT: I actually figured out it’s because of the timing of when you press the trigger. If you press it at the wrong time there is a delay, however if you press it as soon as it’s primed it will instantly set off. Makes sense, guess it is not a bug

[Gurt]

"If you press it at the wrong time there is a delay, however if you press it as soon as it’s primed it will instantly set off." Exactly as we designed it. It requires a bit of timing to detonate it as early as possible.

[RickAvory]

"If you press it at the wrong time there is a delay, however if you press it as soon as it’s primed it will instantly set off." Exactly as we designed it. It requires a bit of timing to detonate it as early as possible.

It’s funny that I didn’t know this for the whole year it has been implemented. I was always wondering why it would sometimes explode instantly and other times super delayed. It is super straight forward now that I think about it.

[Tom Th3 Assasin]

"If you press it at the wrong time there is a delay, however if you press it as soon as it’s primed it will instantly set off." Exactly as we designed it. It requires a bit of timing to detonate it as early as possible.

It’s funny that I didn’t know this for the whole year it has been implemented.

if this is the case.then you should add this in one of the tips