Profile of ShadowLinkX37

speedtest

5G is garbage when attempting to pass through solid objects. If your router/modem is in another room it'll cause packet loss or higher latency. As suggested by aera, try 2.4 if nothing else or try ethernet which is the prefered.

first few minutes:

Your teammate on your side (OST) lost 4 squads in 4 minutes. Don't care what you do, against anyone applying pressure you basically lose your side. Not your fault. Good on the OKW though for rotating and securing 2 wipes out of that bad situation though.

Flametrack micro initially was poor. Rotating a lot so it wasn't using both flame projectors etc.

8:55: First major mistake I saw was when opponents captain smokes your allies MG42 to steal the decrewed 42. You had flametrack there ready to defend but responded slowly with attack ground and only after he was basically on the gun taking it. Should've either recrewed it before him with your repairing pio or just sprayed the 42 and captain before he could get to the gun.

10 seconds later: Ok so they actually didn't get the MG but it gets decrewed closer to their lines and just sits there for minutes. Take it or destroy it because you don't want allied MG42s.

13:00: Flame track eventually destroys opponents building, this should've been done as soon as the 50cal gets pushed away.

Planting schu-mines with HT. Personally I'd rather have the S-mines since they're more cost efficient and the tellers are better vs tanks by a mile. But mines are mines and they work so they're alright.

14:00: Teammate in forest has a p4 and you have no AT. Should have some for of AT by this point or you could get run off the field. Yes teammate has schrecks and stole an AT gun, but that's all you've got for 3 players in the city.

15:00 as I just said, 2 tanks just appeared and you have 1000 mp, T2 up and not building an AT gun. Waiting on panther. You can get away with it probably, could lose some ground though.

17:30 Panther diving for minimal reward. Had you gotten snared or hit a mine you would've probably died.

18:00 I like the werfer decision, was thinking exactly that. Hopefully does more than your teammates stuka

21:50 I saw that werfer attempt.

22:40 So at this point you're down 300vps at 135. Now given the game goes far longer I will assume there's a decent holdout or turnaround coming. Ideally though you're not giving up triple caps this much though. I see the forest player kinda got battered out of the forest, but OKW was supporting you two after your teammate basically flopped the opening and as you can see that has a detremental effect on the teams ability to hold territory and vps. Not exactly your fault, but at some point somone needs to step up and contest another VP if you're devoting 2.5 players and struggling to hold 1 vp.

23:00 also this is the 2nd time p47s have been used. Don't care who it is, someone needs anti-air to counter it. You can't wait 60 seconds for the duration to run out every time they click a button, especially when you see 3 different players using paths.

25:45: decent push. Got a jackson, TA pushed through (teammate). P47 called, no AA and lost the werfer as a result.

29:00ish Lost KT and panther for 2x jacksons. Not worth it. I've noticed this a lot for you is that you seem to want to continue moving forward through an area even showing your rear armor as opposed to reversing. I suggest reversing in most cases unless there's a clear faster way out by continuing forward. It 100% guaranteed your panthers death at this point. Maybe it wouldn't have gotten out anyways but it definitely wasn't going to with a sherman behind it.

Also just a tip for this map: I believe the KT is near impossible to dislodge from the city VP when properly supported. I would've liked to see the KT over there as opposed to mid getting destroyed by 2 jacksons. Yes it wasn't your KT but to give the tip to your teammates next time if it arises.

33:15: Only reason you guys haven't lost by this point is the forest player seemed to have stolen a 105 sherman and kicked out their opponent. Bunkered up nice (toxic) and maintains that VP.

OKW lost 2 stukas a few minutes ago. Tellers may have stopped that jackson but more importantly I'd say you need that werfer again. Not necessarily because OKW lost a stuka but because you need to stop the infantry, blobs, and the AT guns.

35:00: You're currently getting extremely lucky not losing anything to the triple p47s. No AA from anyone yet.

42:00: Ok so your team just got slammed by probably 6 jacksons and lost probably 80% of your armor teamwide. You're making 2 more pgrens. I would say you either need pscrecks for defense in a bad situation or you need fausts from grens. I'd say grens are the way to go for the entire game. Pgrens are nice, but I find they fall off a bit much and no snares makes me sad.

43:25: Again teammate loses KT, has AA again. I think an issue here is that none of you can counter the 60 range TD hordes. Need a heavy TD or more OKW JP4s, but 1 OKW can't counter 4 USF players making jacksons.

So beyond this point team just got rolled by jacksons. 3x panther doesn't really do much here. Not exactly the wrong choice since there was either this or stugs if you wanted armor. Think the play probably would've been take the city and mine up before the jacksons could amass and push back. Biggest issues on your end was micro, specifically armor micro, and then just macro and decision making. Needed AA for most of the match, pgrens weren't the call imo. Needed pios to cap and probably repair/sweep. Only so much you can do when teammates losing heavies every 5 minutes. Commander choice was subpar imo, but if you want to use a commander that's the cost I guess.

Hope this helped.

Not a bug. Ostwind got a rear pen shot in while it was out of control. Pretty lucky tbh considering the angle was like 20 degrees.

That's what I get for not even looking at the graph and assuming it was right to begin with. Yes serelia is very wrong. It would probably look closer to the JLI "light recon g43", a flat dps line more or less.

Can you fix it mods? its not working, impossible to add or change livestream. . .

It's a coding issue. Blacks need to resolve it, and that happens when they get around to it I guess...