Shock Troops - Grenade cooldown

New topic

New Reply

Posts: 82

Hi there,

just returning from a MP game in which I experienced a strange situation where a shock troop unit was able to activate its frag grenades ridiculously fast, around 5sec apart.

Bug or feature?

Posts: 528 | Subs: 1

Does it even matter if its bug or feature? The sandbag blocking is bug banned in tournaments and yet its not fixed and you can abuse it in automatch. If something is in game you have to deal with it, even if its game breaking bug.

Posts: 13496 | Subs: 1

yes it does matter

Posts: 2885

It is a bug, but you can't really ban for its usage as there is no way to tell when the cooldown should actually finish. On the other hand current implementation of sandbags is fully intended so it is not a bug, even if some tourney organisers don't like the way it works.

Posts: 3166 | Subs: 6

13 Jan 2019, 19:35 PMferwiner

On the other hand current implementation of sandbags is fully intended

It's not working as intended, it's just not really fixable.

As for the Shocks cooldown it's a bug and it will hopefully be fixed in the next balance update.

Posts: 3602 | Subs: 1

13 Jan 2019, 19:45 PMSander93

It's not working as intended, it's just not really fixable.

As for the Shocks cooldown it's a bug and it will hopefully be fixed in the next balance update.

Posts: 2458 | Subs: 1

It´s a bug. It is however intended that smoke and frag grenade don´t share a cool down but even that is pretty stupid now that Shocks have good DPS until. It should just be like it was before the patch, shared cooldown on smoke and frag.

Posts: 493

5 sec between frag nades or 5 sec between smoke and frag?

Shock Troops
...
-Grenades no longer share a cooldown.

Posts: 2885

13 Jan 2019, 19:45 PMSander93

It's not working as intended, it's just not really fixable.

As for the Shocks cooldown it's a bug and it will hopefully be fixed in the next balance update.

A bug is when software behaves differently than a person who created it expected it to behave. In this case the people who created the solution knew perfectly well that it works like it does and they knew about all the consequences of that. They could have dreamed that if they had more power to change the game it could work differently, but they knew it is impossible so they designed it with technical shortcomings in mind. Which means they intended for it to work that way and thus it is not a bug.

Posts: 3166 | Subs: 6

Whatever, engine limitation then if you're so keen on semantics. It is not working as intended, otherwise Relic wouldn't have banned it from their own tournament. As it currently stands Relic does not want it in the game, but it can not be fixed.

ARGUABLE EXPLOIT AND BUGS RULINGS
All players taking part in any stage of The Anniversary Classic must be familiar with the following rules regarding certain scenarios or exploits.

"Ghosting" with sandbags, wire, tank traps, or any other object is NOT allowed.

http://www.companyofheroes.com/blog/2018/10/24/rules-anniversary-classic