Supertester_Opinion

You don't give enough information for us to assess; what ship were you in? what position were you in? what CV were you facing? all these are important bits of info.

Coming from my own clan's perspective, 50 people per clan sounds a lot, but when the clan is singular in nature (and we do not want to make subclans), this isn't sufficient to sustain our personnel needs. For this reason, I suggest that WG allow 2 more expansions (at 5 members each) to allow clans a maximum of 60 slots for clanmembers. While this will not affect most clans, I think for larger clans that intend to stay singular like ours (REPOI), this is a very nice QoL change.

Generally there are 2 things about rework CVs that people don't understand: 1. They "farm for free" by design; no matter how hard you try to suggest buffs/nerfs/whatever, they will be the only class that is designed NOT to silence each other. 2. AA is only one factor of many when CV attacks are concerned. Relying purely on AA to stop CV attacks now would be akin to relying purely on TDS vs torps or relying on armor belts vs BB AP shells; if you misplay, you will still die horribly.

Proof that you don't need to have good stats to be a CC.

I got a bug where if a BB takes the superheavy AP skill (3 points), and its AP shell regular pens on DD hulls, the damage boost is NOT applied. I have two videos showing this in action in 0.10.1, but only 1 replay file (of the one vs Oland, 15:55 timestamp). Youtube Videos: Musashi vs Oland Salvo (1 AP shell hit, deals only 1480 damage instead of 1554) Musashi vs Grozovoi (deals 3034 with 2 shells which is 1 shell getting the bonus instead of 3108 damage where both shells should have gotten the bonus) Replay (only vs Oland available): 20210216_152445_PJSB509-Musashi_19_OC_prey.wowsreplay

Yes its completely possible if the player is good enough. Those stats wouldn't set off alarm bells for me (especially if he's doing a div).

While I DO agree with most of his concerns/points about CVs, I have to point out the following: You do NOT need to play CVs "at a high level" to be able to make good arguments about them. To me this just locks out potential good ideas/assessments from someone outside of the immediate CV community. The concerns outlined in the video are VERY clearly geared towards comp AND solo/flank style gameplay, the former of which the game isn't even balanced for, and the latter of which would normally get you killed in a CV game. I admit its not fun if you can't go full-on rambo, but if there's a CV in the game, you are given the choice NOT to push/flank mindlessly into said "crossfires" - take it.

Unique Commander Andrew Cunningham talent activates, but does not result in the described tangible effect. Tested on Implacable in coop; For Lightning Strike talent, Upon obtaining 2 flood ribbons, aircraft speed is supposed to go up by 5% across the board, but for rockets (which have a base speed of 180 kt) and TBs (172 kt base speed, this remained the case even after obtaining the 2 floods. Replay attached below: 20201120_191914_PBSA108-Implacable_14_Atlantic.wowsreplay

The only way to make these people "understand" their mistakes is to sanction them (and their clients) hard enough that they WILL lose out, materially speaking. Namely, account bans.

1. Description: Manfred researchable dive bombs normally deal 26400 if all 3 bombs citadel the target, but in 1 instance, it dealt 31185 (on the receiving end). 2. Reproduction steps: - Play kremlin - Get AP bombed by a Manfred von Richthofen 3. Result: - Enemy squad (in attached replay at ~15:00 mark) deals 31185 damage with 3 citadels 4. Expected Result: - Enemy squad should only deal 26400 damage if all 3 bombs citadel. 5. Technical Details: -Replay attached, Kremlin was bombed for that damage at around the 15:00 mark (5 min after gamestart), and another squad immediately did 26400 damage (which was correct behaviour). -Bug occured at approx. 2pm UTC, October 7 2020 (ASIA clan battles primetime). 20201008_010229_PRSB110-Sovetskaya-Rossiya_44_Path_warrior.wowsreplay

Preface: I believe in NOT being prejudiced against certain groups when it comes to rule enforcement. To me, justice should be served solely based on the circumstances and be blind to everything else. Just in case people want to accuse me of being “racist”. You know who you are. I’ll say it right here: I don’t think WG is taking clan battles violations seriously enough. Why? Read below. Recently, WG have posted threads detailing actions they took against clans that violated EULA in clan battles, like on ASIA, EU, and NA. Now, obviously, I am happy that they’re actually doing something considering the under-the-table manner of these dealings, but at the same time, I am also unhappy that they weren’t hit harder considering they were basically RMTing (these kinds of services are NOT free). These people just moved on to their subclans or made new clans, and kept playing as usual. Nothing changed. Now, to be absolutely fair, this is not the first time WG have acted on this sort of thing; In seasons 1 and 2, the exact same thing happened on RU as you can see here and here. Heck, UMR-R got the same treatment last season. So, by that logic, you would think that the same violations have been dealt with the same punishments. Indeed, they have. At least they are consistent, but too lenient in my opinion. However, 2 of the clans in question (PWP on NA and VOR on EU) decided to take it 1 step further; VOR EU changed their clantag to [_TWA_] ([TWA] is a top EU clan) before it got disbanded, and PWP made an entirely new clan after disbandment… with the tag [WGCNM] and the name "WG Never Mind the Slander and Liber" . Before anyone asks, its to do with intimate relations with one’s mother…. and her death. Clearly, both of these clans are upset that they got caught breaking EULA… While the _TWA_ rename was in bad taste, they didn’t break any rules (that I am aware of), so of course nothing else happened to them. However, the PWP members that founded the [WGCNM] clan only had to contend with the clan being disbanded, with no further sanctions on their accounts. Again, consistent with previous clan names that violated rules, but too lenient in this circumstance since they expressed discontent at being caught breaking EULA… *by breaking EULA*. Imagine if you trashtalked a mod that just issued you a gameban. That’s what they have done…. And by the looks of it, they have gotten away with it without any significant consequences (2500 doubloons is nothing to these people) So, we now have a situation where repeated, large scale clan battles violations have occurred, and with no apparent escalation in enforcement. Even worse, some who were caught decided to violate EULA by trashtaking WG using their new clantag/name and they also didn’t get any escalated account sanctions. This, to me, is inconsistent with literally every other rule violation in this game. Let me give some examples: You trashtalk in chat, you get chatbanned (restricted from chat) You rig/grief others mechanically, you get gamebanned (restricted from games, may apply to entire account or just randoms/ranked if you TK/AFK) You break forum rules, you get forum restrictions. And now, when you break clan battle rules…. You don’t even get banned from clan battles or joining clans. They only got their steel refunded. No account bans, nothing else. And as of a few days ago, WG announced the mercenaries system which allows clanless/different-clanned people to play in clan battles for another clan. This is, from a player perspective, the perfect breeding ground for RMT services and exactly the kinds of violations that these clans were caught for in the past. So, what is WG going to do when this sort of thing happens again? Just disband their clan and take away their steel, letting these kinds of players just play clan battles like nothing happened? I sure hope not and that WG will at least ban them from at least 1 future season of clan battles if they're caught doing this sort of shenanigans. In closing, I am disappointed with how WG has handled the clan battles violations (especially with the PWP -> WGCNM rename) as it shows that they are unwilling to escalate sanctions related to repeated clan (battle) violations. I know you are capable of doing more WG, you said it yourselves in the very posts! Show us you mean business when it comes to these players. Otherwise, the enforcement doesn’t seem very convincing at all and is merely a slap on the wrist.

Yeah, given that they have commited the same offense 2 seasons in a row, surely this warrants a heavier penalty.... WG, this is your chance to draw the line...

With that ping nothing will save you I'm afraid. Rework CVs require low ping specifically because of how time-sensitive the drops are (its basically near impossible to perform good drops on moving targets with high ping).

Description: It is consistently reproduceable to lose control of the entire CV system as a CV player when setting waypoints on yourself mid-flight. Reproduction steps: Enter battle in a CV Move CV forward by pressing W Take off a squad of your choice While mid-flight, try to stop CV by setting waypoint on yourself Result: Game becomes unresponsive, both CV hull and squad cannot be controlled, mouse cursor permanently on "observation mode". Expected Result: Waypoint is set and no issues arise at all, being able to control CV/squad again. Technical details: Occured around 5:55 pm UTC +8, and around 6:05 UTC (training room reproduction which required force quit, no replay on that). Replays attached. 20191010_175957_PJSA106-Ryujo_42_Neighbors.wowsreplay python.log

1. Description: Aircraft in a CV strike squad suddenly explodes and loses all HP when in range of AA guns/flak 2. Reproduction steps: Not known, does not happen consistently. But aircraft are typically subject to this bug within long range AA. 3. Result Aircraft within the squad explode suddenly and lose all their HP without ever coming into contact with flak as intended. 4. Expected Result: Aircraft only takes damage from continuous DPS or flak puffs that they fly through. 5. Technical details: Replay provided for review purposes, python log not available as its not my own game. 20190528_201250_PJSA110-Hakuryu_16_OC_bees_to_honey.wowsreplay Twitch clip of bug: