The Cold Hard Truth About Fraggers Nade...

[INF3RN0]

It might also be interesting if getting shot while cooking a grenade either caused the grenade to drop or explode. I do think the cooking mechanic combined with the large AoE is the biggest problem. We need some kind of global counter.

[Violator]

A perk to enable the cricket bat to slog nades would be fun :).

[Chux]

[QUOTE=INF3RN0;527519]It might also be interesting if getting shot while cooking a grenade either caused the grenade to drop or explode. I do think the cooking mechanic combined with the large AoE is the biggest problem. We need some kind of global counter.[/QUOTE]Someone already mentioned it before, making the nade explode if shot would be fun The nade should drop only if you get killed while cooking.

[Humbugsen]

It might also be interesting if getting shot while cooking a grenade either caused the grenade to drop or explode. I do think the cooking mechanic combined with the large AoE is the biggest problem. We need some kind of global counter.

yeah, make it a high risk, high reward tool.
Or make it a dodgeable skillshot by decreasing travelspeed.
please

[Ashog]

The AOE of nades is pretty ****ing huge; you don’t need numbers to justify that.

You always need numbers. Until then it’s all subjective.

[Ashog]

Not cooking, the penalty you get for not throwing a nade after starting the cook.

Well, should have said so then.
tbh I never used nade cancel anyways, always throw nade regardless if primed.

[Glottis-3D]

[QUOTE=Ashog;527590]Well, should have said so then.
tbh I never used nade cancel anyways, always throw nade regardless if primed.[/QUOTE]

you always throw nades, even regardless if cooldown isnt done yet!

[BioSnark]

It might also be interesting if getting shot while cooking a grenade either caused the grenade to drop or explode. I do think the cooking mechanic combined with the large AoE is the biggest problem. We need some kind of global counter.

This seems a bit of an extreme penalty although it may be justified. I’d rather the penalty be significant throw accuracy reduction so it fumbles the throw but doesn’t kill the fragger and their team (assuming friendly fire).

[INF3RN0]

This seems a bit of an extreme penalty although it may be justified. I’d rather the penalty be significant throw accuracy reduction so it fumbles the throw but doesn’t kill the fragger and their team (assuming friendly fire).

A mine will kill the proxy throwing it as well.

[sunshinefats]

This seems a bit of an extreme penalty although it may be justified. I’d rather the penalty be significant throw accuracy reduction so it fumbles the throw but doesn’t kill the fragger and their team (assuming friendly fire).

I could deal with this, as it seems somewhat reasonable. Having your nade kill you or drop seems a bit excessive to me too.

[montheponies]

Still think this is overstated. But if something has to happen i’d be happiest with slowing down the nade throw and adding to it’s arc. Adding a second to the cooking time wouldnt fuss me too much, making the switch speed slightly longer seems reasonable as well.

Reducing the AOE, or main cooking mechanic shouldnt be considered at all. It’s a weapon, nothing worse than having a hobbled element - just think back to the difference between the PF in RTCW v W:ET.

Happy to try other ‘counters’ - eg. shooting the nade in his hand to blow him/associated team mates (if FF is on), however should come with the Brink like capability for him to shoot the nade in mid-flight as compensation.