Benser33

Perhaps.

Perhaps reduce the Fen Yang HE penetration to 1/5th instead of 1/6th?

The only perma camo available for all of the black ships is the "black" permacamo.

No you cannot. They have their own permacamo which is identical in stats but different in apperance to the regular counterparts. You can make the black permacamo look like the regular counterparts permacamo by disabling the decorative camo category with the additional content menu on the right side of the port, but the B default camo cannot swap between the standard and alternatve colour schemes that Type 10 can.

If you are active on the PTS for multiple, consecutive seasons then your PTS account gets automatically synced with your live account (as long as your PTS and live account use the same email address) at the start of some seasons.

This is not correct. Firstly, the post you link relates to the Italian cruisers, not the Italian battleships. These ships were never affected by the large calibre shell protection of DDs because they do not fire large calibre shells. There was a 10% damage to DD protection applied to all SAP shells and this was removed from all SAP shells. Secondly, the post also makes no mention of the large calibre protection rule at all. This point was covered during the original ITA BB reveal stream. https://clips.twitch.tv/QuaintFuriousRabbitArsonNoSexy No change has been made to SAP since then that affected the DD protection exemption. Unless you are a supertester and can confirm otherwise...

Every reset will earn you 10,200 points by regrinding the line back to tier 10, unless you reset a CV line which will only earn you 8k. Your first reset every 3 months is worth double, so if you reset a non-CV you would earn 20,400 points by completing that regrind. You can check the timer on the double bonus at the bottom of the tech tree; You can reset as many times as you want to earn the points needed for ships like Ohio or Slava, but the double bonus is only available for one reset every three months.

Yes but currently DDs have no protection from SAP. So, either the change for Khaba and Haru is a typo, Khaba and Haru will be the only DDs to be protected or they are extending DD large calibre shell protection to include SAP as well as AP. Since WG have said previously there were not going to include SAP shells in the DD large calibre shell protection this new change now contradicts that.

Finally reversing the exception for Khaba and Haru. But it is curious that SAP is included in the comment when the current rule for SAP is to ignore this protection, to the best of my knowledge.

X will unlock your target, press it again will lock onto whatever is hopefully nearest to where you aimed.

I agree that there should be a keybind to toggle target designation on your currently locked target, especially when you want to designate a target for secondaries and have to spend 5-6s finding where your mouser cursor is because its 2mm in size at 4K or trying to click on something that you could shoot but cant see because of terrain. Alternatively, or additionally, making the cursor bigger with the UI scale would be nice... There are mods in Aslains modpack that make the cursor a different shape/color and also apps like https://dragonrisegames.com/yolomouse/about

But you only need to know 13mm, 16mm, 19mm, 25mm, 27mm, 30mm and 32mm, and even then as a cruiser the only one that is really relevant at high tier are whether you have 27mm or not. Every other armor thickness is standard for their class and tier, exceptions to armor thickness are all enough to become unovermatchable (RU cruiser 50mm plates, Atagos 41mm deck, Alaskas 36mm deck, Goliaths 40mm deck, Venezias 40mm icebreaker, Hippers 40mm icebreaker, etc) with the only exception that needs to be considered is the one that causes some cruisers (US CAs and German CAs) to have 27mm plating that can ricochet 380mm guns. BBs do the majority of overmatching, very few cruisers can overmatch, so just remember what BBs can do. 203mm can overmatch 13mm 305mm can overmatch 16mm 356mm can overmatch 19mm 380mm can overmatch 25mm 406mm can overmatch 27mm 457mm can overmatch 30mm and the only guns that can overmatch 32mm are the 460mm guns of musashi and yamato and the 510mm guns of shikishima. At tier 8-10, with the exception of added plating like bomb/HE decks and icebreakers your cruiser will either have 25mm plating or 27mm plating (unless its a super light cruiser like an RN CL, Smolensk or Colbert which all get overmatched by everything bigger than 220mm). Ships with >=406mm guns dont care either way, they overmatch you regardless. Ships with <=356mm guns dont care either way, they can't overmatch you regardless.. Only 380mm gun users care whether theyre shooting AP at a bow on cruiser that has 27mm armor. At tier 7 and below its rare that a cruiser has enough armor to avoid being overmatched by anything other than other cruisers or very low tier BBs, some cruisers are thin enough to be overmatched by 203mm cruiser AP.

One issue with this would be when an armor thickness actual overmatch calibre doesnt clearly correlate with common calibers. Like how 32mm armor can actually be overmatched at 457.6mm calibre, so 457mm guns cant do it, but it could still lead to confusion. What you need to know is what common calibers you will face that could overmatch it, so it's more useful to say "you get overmatched by 380mm guns but not by 356mm guns" than to say that you ricochet 357.5mm shells. Also, this would only tell you what caliber can overmatch you, you'd still have to remember what ships carry those guns. Theres a short list of common thresholds involved in armor thickness that relate to HE penetration formulas and AP overmatching. You can remember the common armor thresholds that relate to ships based on their class and tier, and then learn the exceptions. You still need to learn what armor and guns your enemies carry, as well as your own, to not only effectively damage them but also to trade your HP with them positively so you survive and they don't.

None of them are available via the tech tree, you can only see them there because of a tech tree mod. Despite what the tech tree implies, event ships cant be obtained outside of the halloween/april fools/other events, if they can be obtained at all. From the top row, Valkyrie, Gale and Heracles are parts of the 2020 Halloween event The Big Hunt. The ships can only be used in that game mode, Valkyrie is obtained automatically, the other two are obtained via mission chains. This game mode is available right now, called Key Battle. From the second row, Ghoul, Razorworm, Steel Rat, Scarab, Octopus, Leviathan and Varg were part of the 2018 Halloween event Twilight Battle Part 2. None of them are obtainable now. From the third row, Steel Lancet, Angler, Mutantovks, Rust Nightfall, Octodroid, Fossil, Maverick, Scorpioid and Crocosaur were all part of the 2019 Halloween even The Raid for the Filth. None of them are obtainable now. If you like the looks of the ships, the visuals can be purchased, but only during the time the Halloween events are live. They are no longer on sale this year.

As a further point of reference, the explosion radius on Thunderers HE shells is 3.25 These parameters are available on https://gamemodels3d.com/games/worldofwarships/

I have no idea if it is intended, it may be because AP bomb strikes dont occur as frequently as AP shell hits do, so the capability to reset with near strikes was added, I think that the exposion radius is quite small. AP rockets all have an explosion radius of 2.

I do not know how the exact size is calculated from this value, especially considering the virtualised scale is not known. But you can see all AP bombs have an explosion radius roughly equal to a 1000lb bomb. AP shells have no explosion radius.

HE bombs have a variable explosion size based on their size. US CVs for example Langley 500lb bomb 1.58 Ranger 1000lb bomb 2.28 Lexington 1000lb bomb 2.28 Midways 2000lb bomb 2.83 UK CVs Hermes 40lb bomb 0.35 Furious 250lb bomb 0.96 Implacable 250lb bomb 0.8 Audacious 500lb bomb 1.42 AP bombs do not cause damage to things inside their explosion radius but they still have an explosion radius of 2, exactly the same for every bomb and being in this space still can cause a reset, it just doesnt cause damage.

It's called Mainz.

Sounds like CVs get FDR style attack, with rockets firing more sequentially over a longer priod rather than essentially being instant meaning less likelihood of getting multiple hits on a small target. The third point I dont understand, why give the defender markers for where rockets will hit? Are we going to get surface markers we can dodge when we get shot at as well?

Skip bombing was used by the US Army Air Corp who utilised B-17s before it was adopted by the 5th Air Force who adopted the tactic in the far east theatre using B-25s and A-20s outfitted for the task. Can't find many sources, plenty of articles on the subject however. https://warfarehistorynetwork.com/2020/03/13/wwii-pioneers-of-skip-bombing/ It was deemed much safer for A-20s who had forward firing cannons so theres more evidence of that application. EDIT: Actually here's some intel on the subject;

It means that if they buff or nerf Yamato they will buff or nerf ARP Yamato at the same time.

But AA mounts on the A turret would stop the B turret from being able to depress for short range fire...

First I've heard of any of the issues you've listed, if you're having issues with the current update you should make a thread under the relevant forum category; https://forum.worldofwarships.eu/forum/484-current-update/ At a glance, doesn't look like people are reporting similar issues to you, here, there or under the 9.10 PT build forums.

We've had a few updates released since you first made this thread, if you're getting this issue every update you may want to consider reinstalling WGC. The issue should usually be resolved by logging out and back in to WGC (because the launcher passes authentication information to the client, when the client doesn't get that info it just hangs on the Waiting for Authentication screen). If you've tried reinstalling and still get the issue then you'll either need to provide support with a WGCheck report to see if they can identify the issue or investigate a further technical cause outside of the game itself, such as a permissions issue or storage fault.