Profile of Protos Angelus

Relic has the opportunity to implement cloud-based shards of on-demand servers that spin up to accommodate players' physical location and then start matchmaking them from there. e.g. AWS regions for those who want to do more reading.

If they don't do this, then we're all still royally fukd when coh3 comes out.

Will Relic embrace modern day cloud networking and matchmaking for coh3? doubtful, because they're using the same coh2 engine and I saw a vid where a dev proudly said 'we started coh3 immediately using the coh2 engine' - and I thought, that's a big FU to your international players already.

Let's see if they do a big dev reveal post about their networking tech. Absence of that says it all.

Of course they will use COH2 engine. It's a well developed engine truth be told. If they iron it out and optimize it, I don't see why not. Also, the network part of the engine can be rewritten. Usually for these parts of the game, you implement different methods and strategies so that adding sh** to it is easier (similar to factory in Java, etc.).
I highly doubt everyone will connect to one server like in COH2. I'm pretty sure they will implement something new.

It's actually so overpowered that it got banned in competitive COH2 5years ago. That's why we don't see it in tourneys.
Oh wait no it didn't. Weird that the best TD in-game doesn't get played.

In 3v3 there is always a JP4 wall sooner or later on most maps. You won't play it in the tourney because a Panther is generally a better choice. Much more mobile and counters every tank, hard. JP4 is more difficult to use and a more defensive tank, used to solidify the position. In 1v1 there is no such thing as solidifying. In 2v2+ there most certainly is. In 3v3 it's most common.
With 60% penetration and a couple of seconds between shots, no tank wants to stand in the line of fire for too long. With a bit of luck on JP4 side, your tank goes bye-bye.
So yeah, it's OP in teamgames but not because of it's stats or whatever. JP4 should have lower armour IMHO since it has such low target size and becomes a 5-shot tank with veterancy. But the main strength of JP4 is in map design. Put 1-2 JP4s on a map like redball. Combine it with a stuka and a KT and you have an impenetrable fortress that will only ever be pushed back by 2 opponents combined. Such nonsense would not work on 1v1 maps and some 2v2

Not really. I belive it had different philosophy behind it to achive simular results we have right now.

At very least RNG in inf combat was less persistant, I belive that back in the day there wasnt any kind of "recieved" accuracy or if it was, then it was less impactfull.

There was less RNG in regards of how inf combat worked, for instance situation where 1 model was instantly sniped by voley fire was less common and so on.

You can play original soviet campaign to see what game was on release, because I belive non of the core balance changes changed unit stats.

I think you're right. USF campaign as well. Models drop left and right there and most of the stats are unchanged. Much different combat than the multiplayer/skirmish part. Most of it is broken/bugged as well.

The Scott (a backline artillery unit that take three shots from the Panther to kill) needs smoke because a Jackson can't kill the Panther in three shots?

Does the Panzerwerfer, Katyusha, Stuka, etc need smoke and enough health to survive three shots from an opposing tank, just in case an enemy tank tries to dive it? We wouldn't want there to be any way for someone to kill a backline unit, after all, even if you leave it out of position.

Katyusha and stuka and werfer are all alpha dmg units. They barrage, kill plenty of models in skilled hands and get the f*** back to base. Scott on the other hand needs to stay on the frontlines to be effective, and with 50 Autofire range, you won't be using it much except for the smoke barrage. Scott usually arrives the last, if it arrives at all (speaking for 3v3). With 50 autofire range, you won't be using it for barrages much because they are quite accurate, and against skilled opponents, you won't really kill paks or raketen or MGs. Will damage it a lot, but not kill. Most people I play against usually move the pak or MG after the first shell lands. It's not that hard in 3v3 as you're not fighting all over the map, but on a certain "VP lane". It takes 3-5 seconds to move the pak/mg to a safer spot to deny the scott barrage whilst not losing anything in terms of vision for shooting the pak (since the maps are lane-y and most sightblockers are destroyed in Scott timing).
I don't think I've ever had a scott survive if I use it to autofire against blobs (late game double paks kill it in 3 seconds). I even consider myself to be quite good at micro and using both reverse and hold fire, etc, but unless the vehicle has 99999 acceleration, you won't get out in time.
And for barrages. Again. Not really something I take to displace MGs or Paks because the barrage really is accurate. If you see where the first shell lands, you don't have to move the weapon team a lot to deny the scott barrage (eg, you see calliope or katy or werfer or stuka, you get the FU*K out because the AOE is huge).

The only real use for Scotts in late game is the smoke. Smoke is the saving grace for Scotts in teamgames. The smoke barrage is long range, has excellent spread and scatter and really blocks. You won't kill anything, but you will buy yourself some time to organize a defense/offense.

Again. This is for 3v3+. I can't talk for 1v1. I'm guessing the low AOE but highly accurate barrages are more useful there, as just damaging a unit is enough, and it's much harder to manage your army across all map, so a scott barrage will get a few hits more in, before the MG/pak/raketen... displace

Talking about the scott as a backline unit is not really transparent. It's not a fronline unit, but definitely not a backline one as well. Somewhere in between. A pak howi is a backline unit.

Scott needs a rework. All these push/pull changes won't really fix the core problem: it's overlap with pak howi. Right now they are both barraging units. Pak howi deals more damage and has better AOE (+ better veterancy) but is really really slow and easy to kill (the 5->6 models made it 1% more survivable). Scott is quite agile but has low dmg/AOE and a short autofire range.

|Plus|

Both suck vs blobs:
Pak howi because it's slow to rotate and fire, and after the last AOE nerf, doesn't punish as much. Also, the shells take quite long to land.
Scott because it has low AOE but high accuracy (you generally want scatter vs blobs for both shock effect and more dmg) and short autofire.

Why scott was not given an autofire mode that actually has decent AOE/dmg and a barrage that has a high scatter (as to not be good vs single MG/pak). And pak with a high scatter autofire but high dmg/AOE barrage (so it's good vs static, bad vs mobile).

Scott would also be made a 2 shot unit and target size reduced to 17 (currently it has 19 target size which I think is a bit too much; StugE which has more armour and HP and really is larger, has 17 target size).

So in the end you would have an autofire specialist Scott that could somewhat deal with blobs and a pak howi with a inaccurate autofire but deadly barrage. Scott would have lower target size but also 320 HP and a pak howi would also go back to being 5 man.

For mines its true, but you still have snares on your riflemensurvivability was just over-tuned.

Snares on rifles are downright useless. Low range, extra long animation. 80% of the time the snare will cancel due to the animation bugging out.
Snares on rifles and mines on RE are downright useless in most scenarios. Heck, I've had situations where a 222 dived on my AAHT and managed to kill it before the snares were fired from the riflemen. So a rotating AAHT couldn't fire the cannon due to the rotation and the animation took so long that the AAHT died. A couple of seconds later, 2 snares start flying.
Or what about the ever brilliant "snare model died". Heck, lost a whole squad not once due to the long animation where you try to snare a 50% hp P4, only to have the squad die because the snare takes too long.
Same with RE. The vehicle stun is short, and most of the time means nothing, especially on large maps in 3v3+. In 1v1 the RE stun mine can be utilized because when you react, the supporting units have less territory to traverse.