Should assault grens start on cool down?

New topic

New Reply

Posts: 609

As a jaded ostheer fan I’ve been having some fun recently with assault gren starts and upsetting the normal dynamic of my 2v2 matches by getting my first squad right in soviet/us faces and spoiling their complacency as they spam cap early or try con rushes on cqc maps. The unit seems balanced to me - wilts under focused fire but I am wondering if it shouldn’t come 30s later or so to avoid chewing up and forcing off the field their first unit (nearly) every time

Also sprint seems a little too good like the duration is too long- allows you to cross maps with great speed rather than just as a combat buff

Playercard of Array

1v1: P	2v2: P	3v3: P	4v4: P
1v1: P	2v2: P	3v3: P	4v4: P
1v1: P	2v2: P	3v3: P	4v4: P
1v1: P	2v2: P	3v3: P	4v4: P

Multi Quote

Posts: 13496 | Subs: 1

CP0 infatry should simply become build-able and not call ins.

Currently their timing is greatly affect by the map design.

Posts: 3260

It's a similar problem to Assault Engineers: you can get two out very quickly.

Starting them on cooldown is probably the cleanest fix, and is consistent with the route taken with USF infantry.

Posts: 2066

Yeah I second having them have a build time.

Posts: 5279

25 Jun 2019, 12:24 PMLago

It's a similar problem to Assault Engineers: you can get two out very quickly.

Starting them on cooldown is probably the cleanest fix, and is consistent with the route taken with USF infantry.

Tbh I think all Infantry, 0cp and onward, would be better balanced as t0 built infantry so that they are built instead of an instant call in. Makes them less panic infantry and instead requires foresight and planning. This is a TACTICAL rts after all...

Posts: 110

Having assgrens as a call in is not a problem in any situation as assault engies as USF.
If somebody has problem of unexpected quick assgren/assengie deployment, it better should be like that. Any close-combat infantry, which is not schock-troops, should have breathing space since using them is kinda risky already.

Posts: 301

Make them buildable at the HQ so they compete with the mg42. Either go full agression or an early push and then consolidate with a 42.

Posts: 1164

Making them buildable wouldnt slow them down THAT much, because the build time is not that different to the added walk time from edge of map vs from your structure on many maps.

Posts: 13496 | Subs: 1

25 Jun 2019, 18:06 PMBrick Top

Making them buildable wouldnt slow them down THAT much, because the build time is not that different to the added walk time from edge of map vs from your structure on many maps.

1) built time can be adjusted
2) walk time is map depended in some they arrive allot faster

Posts: 3053

25 Jun 2019, 12:13 PMVipper

CP0 infatry should simply become build-able and not call ins.

Currently their timing is greatly affect by the map design.

Playercard of LoopDloop

1v1: P	2v2: P	3v3: P	4v4: P
1v1: P	2v2: P	3v3: P	4v4: P
1v1: P	2v2: P	3v3: P	4v4: P
1v1: P	2v2: P	3v3: P	4v4: P

Multi Quote

Posts: 1487

They should be 1cp. Thats all

Playercard of eqdw

1v1: None	2v2: None	3v3: None	4v4: None
1v1: None	2v2: None	3v3: None	4v4: None
1v1: P	2v2: P	3v3: None	4v4: P
1v1: P	2v2: P	3v3: None	4v4: P

SteamId is set to private for user id aaa. Set it to public if you want to link to your playercard via your user id.

Multi Quote

Posts: 591 | Subs: 1

Having them come at the same CP point as Cav Rifles seems appropriate. Cav do get more long term flexibility but they're basically the same unit on arrival.