Aotearas

If anything those people should get special MM only against equally penalized guys. Iirc a couple other multiplayer games did similar stuff with cheaters. Instead of banning them they simply restricted their accounts to only play on servers with other such convicted cheaters, get a taste of their own medicine. Always found that practice to be poetic justice and something that might do well being the industry standard.

Yo @havaduck, is that you?

Not that this would have any direct relationship with WoWs, but if the upcoming X4 Foundations plays anything like like X3 Reunion/Terran Conflict/Albion Prelude (and thus nothing like that other interlude that we absolutely didn't have, why are you asking?) you'd have a hard time prying me off my PC for anything else anyway. Can barely wait:

Your tagging of @MrConway didn't appear to have worked, so here you go. Also, open a ticket to support anyway. Their website says they don't deal with this, but other WG staff have regularily said that opening a ticket with evidence (replay, which you have) will have them look at it and take measures.

'Zombieland Saga' eh? Can't say it was on my target radar so far as I read it was a bit generic, but I guess I'll try it out and see. Also, I probably don't have to say this given the recent hype (or outrage, depending on who you may ask) I can wholeheartedly recommend 'Goblin Slayer'. Definately a very nice series though mild spoiler warning, it doesn't stay quite as grimdark as the first two episodes would imply, it mellows down a bit towards a more standard adventure'y atmosphere (though happy to say it never quite loses the edge). Bonus points if you actually play DnD, it makes the setting so much more enjoyable! In other news, I'm pretty disappointed with 'Tensei Shitara Slime Datta Ken'. After a pretty humourous start and a quite interesting setting (being reincarnated as a lowly slime monster in a fantasy world) it just goes downhill from there. I had hoped the premise would build on the happenstance of him being a lowly slime, but the protagonist turns out even more of a Mary Sue than the original "Sword Art Online" protagonist. Still a nice enough show to watch if you're bored waiting for better stuff, but oh boy what a let-down for what had such a promising idea ... Btw, I like to think I've watched a great deal of anime over my years, so if anyone wants recommendations on say a particular genre, I might help point something out you'd also like, so give me a shout if you want.

This has to be one of the worst analogies I've read in a while, unless you specifically meant to undermine your own argument.

What where they thinking? Easy ...

To be perfectly fair here, getting game balance nailed like that is absurdly hard to begin with and gets harder with every new flavour of gameplay being introduced that blurs the lines between a clearcut rock, paper, scissors balance framework. Considering that WoWs has DD lines that are better at countering cruisers than BBs, some that are better at countering DDs, cruisers that are better at countering BBs than DDs, etc. pp getting a self regulating meta to work is utopian. Plus let's not forget that a self-regulating meta also depends on the playerbase at large being able to tell which works and which doesn't, then react accordingly. I wouldn't trust this playerbase to do that if they had written instructions. Which is why setting certain limits to stop getting the meta lopsiding anywhere in the first place would be the reasonable thing to do.

I would assume he's referring to the vaunted patent.

How about we leave NA madness where it belongs. To make sure build a firewall to keep those trojans away. Bet we can make WG pay for it too.

Considering it's pretty hard to find anything specific if it's years ago and I hardly believe any CS operator would know anything about such stuff or even be allowed to say anything if they knew (if anything it's much more likely they just tell you what you appear to want to hear so they can close the ticket) I'd much prefer if you could at the very least specify exactly what you mean by that so I can narrow down any search queries.

Citation needed.

Haven't counted, plus I was mostly grinding the event maps since the start of Fallen Wings rather than 3-4, but I would guess from the top of my head it was roughly one and a half weeks worth of daily grind to get both, so pretty damn lucky. Would've even been a good deal less if I hadn't gotten a duplicate Akagi on my second SSR drop.

With that my farming on 3-4 is done. Whoop whoop! I just realized ... the tier 2 pedo part in the screenshot!

Considering spotting damage (and potential damage tanking for the same matter) results in entirely negligible rewards anyway the little difference that would make is quite possible worth less than the time you spend posting this thread. It's sad really because if such teamplay actions actually were properly rewarded, this would be a serious concern, but alas ...

Hit the nail on the head. Cruisers need to get close to DDs to counter them. In most cases they will get spotted by said DD a good distance sooner and suddenly you've got five BBs just licking their lips going "om nom nom" and it's realistically impossible for a cruiser player to play any sort of effective DD denial and try to keep track of that much alpha strike potential coming from several angles. It's perfectly possible to keep track of one BB and go evasive when it fires, minimizing the damage a great deal. With sufficient awareness you can also do that for two BBs from two different angles. It's when you have more than that to look for plus everything else you're doing at the moment that it becomes a suicide mission and why most players refuse to do it, leaving DDs to their own devices against enemy DDs most of the time. But that's nothing new really, ever since the BB population exploded and 5 BB per team MM became the norm, followed by disgruntled cruiser players simply switching to DDs to hardcounter BBs leaving precious little cruiser players left for MM that the game de facto turned into a two class meta, forcing WG to make do-it-all cruisers so that the few still playing them have at least some chance to make themselves felt ... WG should've capped BB and DD numbers per team at reasonable ratios a long time ago. They didn't and have been riding the downwards spiral ever since.

Only relevant word here is "begin". You'd be surprised how many "unwinnable" games can turn around and how easy it appears for "already won" game games to be thrown. Oh yeah, because one DD potato is such a crippling loss ... If a single ship is so critical that it cripples an entire flank or even game, then you had another whole bunch potatoes just sitting around twirling their thumbs. No single ship is that important, not even a CV in most cases, unless you play the rest into their hands aswell. A flank can hold perfectly fine even if the only DD on that side of theirs got sunk. A potato CV getting outplayed hard by a super-unicum still doesn't make a bundle of ships sharing AA bubbles that much more easy to drop and you'd be surprised how few places on a map you need to physically hold and how that enables a team to turn into two groups of AA porcupines that are only negligibly less difficult to drop with or without fighter support and even worse to try and push into with ships. It's when a flank suddenly loses their heads and goes into full run-away mode giving the enemy all the map space they want that turns into a critical threat. It's when ships think they must go get that one isolated cap far away from reach of any meaningful friendly AA that not having fighter cover makes them a prime target for a CV drop that you start hemorrhaging ships by hands of the enemy CV. Once more, in the most simplest of terms: in a teambased multiplayer winning and losing is a team effort. So many situations are salvageable, even losing a good chunk or even all your DDs at the start isn't an automatic loss because the enemy team can still fail to properly capitalize and make plenty mistakes on their own for your team to exploit in return to even the odds. Seen that happen often enough and yes, that also includes solo play when I didn't have a division of super-unicums to help turn the tide against an enemy team of average joes. So if everyone could just stop that nonsensical rhetoric about "it's when DDs ..." or "CVs ..." to assign blame and realize that a good deal more has to go wrong for you to lose (or conversely, the enemy has to thoroughly capitalize on the situation to keep the snowball rolling), that'd be great. Roflstomps would be a great deal rarer if the average player knew what teamplay is and how to use it to minimize situational disadvantages rather than just see a situation that's not going into his favour and then basically call it quits right there and then as people appear to do so frequently whilst grumbling about everyone else.

Funny how so many people go here and blame a specific ship class for not doing this or that (DDs not capping/spotting, CVs not roflstomping the other CV, yadda yadda). You guys want to know how often I tread the lines between ship detection and their radar range for minutes on end, only so that literally no one in the team ever takes a shot at the spotted high value target? How often I announced an radar so people can pop the smoked up DD in the cap only for them to just continue farming damage on a battleship in the distance? Or how often I tank in a BB only for the remainder half of my team on my side of the map sitting behind me at range because they're scared of getting hit because the enemy also happens to have a BB on that side? Roflstomps have precious little to do with individual errors. Roflstomps are the result of force multipliers, teamwork in other words. The team that focus fires enemy DDs at the start is going to roflstomp the one that doesn't. The team that properly focuses radar ships when they can will roflstomp the one that doesn't. The team who knows how to zone an enemy CV will roflstomp the one where everyone goes their own merry way and then blames the CV for not covering every single ship with fighters 24/7. Or just the team that knows where to be on the map rather than lemmingtrain along the mapborders completely giving up map control. Because people forget that this is a 12vs12 teambased multiplayer and instead play just for themselves and expecting every else to do the "dangerous" work, that's the reason for roflstomps. The rare cases where MM puts all the superunicums on one side and only communist red potatoes on the other or RNG giving the enemy team all the lucky rolls and screwing over all the other team are entirely negligible compared to that.

Consider me triggered.

*looks at @El2aZeR's drop RNG* *looks at mine* Hue hue hue

F EA for killing CnC, people don't even know the glory that was that franchise. And to think that I was alpha testing the then new CnC until EA just axed it for no good reason ... the nonsense reason they gave was that apparently "this wasn't the what the community wanted", which is such obvious BS it still enrages me today considering that the entire alpha test forum was full with positive feedback and the only thing they needed to do was make a singleplayer campaign for it. Even the recently alluded-to remake revival of the franchise just gets me salty. But I'm digressing, have some Frank Klepacki (the guy who made most of the iconic CnC soundtrack): Ah, listening to that music makes me happier again.

Well, don't have a good stopwatch at hand so that's the only thing I can use ad-hoc. I've tested in autopilot mode though and with the AI shooting BB guns the moment they're off cooldown the reload timings at least should be accurate. Anyhow, I've send an email to Azur Lane customer support with my findings and necessary data for comparisions so we'll see if they say anything about that. Though if the in-game clock is real shitty, that might be the issue, but in that case I'd have to wonder how anyone could mess up a simple clock that hard ... Ah screw it, let's see if I can make a recording with OBS to show my ingame timings. Nope, recording with OBS apparently impossible with Bluestacks, ... well shucks. UPDATE: Here's screenshots of the ingame timings instead. First set is WITH HSFCR (base reload is 20,88 seconds). First volley of the encounter: Second volley of the encounter: Now the same encounter WITHOUT HSFCR (base reload still 20,88 seconds, only took the HSFCR off). First volley of the encounter: Second volley of the encounter: Third and fourth volley of the encounter: For comparision, port stats: So yeah, something's iffy AF and definately not working as it should. Pretty sure Hood's skill reload buff doesn't apply to herself so that shouldn't effect the observation. Would be interesting however if this was a localized issue, because if this were a bug associated with the equipment (or rather with the Precision Lock-On skill I'd wager) it would effect everyone using the module, not just me. I'd recommend others here test it out if possible to see if you can confirm that you have no such issues with the HSFCR.

Except I've been watching the ingame clock aswell and with the port reload at ~20 seconds, ingame first volley also fires after ~20 seconds (not the ~17 seconds it should with a 15% reload buff). Second volley also fires after ~20 seconds. Interestingly: taking the HSFCR off, first volley fires after ~23 seconds (despite my port reload still saying ~20 seconds so that equals a 15% reload debuff ...) and the second volley fired after ~20 seconds (!!!).

I have the fleeting feeling the HSFCR isn't quite working as it should. Says 15% off the cooldown for the first maingun volley. My Hood has a reload of ~20 seconds with its current setup. That means with the skill provided by the HSFCR the first volley should fire after ~17 seconds, then every usual ~20 seconds. Except that I've been paying attention to that and my first volley still only comes after ~20 seconds ... Just checked in port to make sure and the reload time doesn't change with the HSFCR equipped or not so it's not a bug where the skill's reload buff just happens to be applied to the reload timer flat. So yeah, it's definately not working at all.