[1.24] Error with AV classification/Problem with floatplanes

[janxol]

I was randomly experimenting with floatplane-equipped aviation cruisers/battleships such as Ise and Tone and I believe I found a bug with ship classification. I recall designing such vessels before, but now the game won't seem to allow it.

As per manual:

 KEs cannot be equipped with floatplanes.
 CLs may carry no more than 4 floatplanes.
 CA and larger warships have no limit on the number of floatplanes that may be carried.
 AMC may carry up to two floatplanes.
 AV may carry any number of floatplanes.
 CVs and CVLs may not carry floatplanes.

The rule i have highlighted appears to be either incorrect or not working.

The test design was a Tone-inspired CA with three turrets all-forward, two catapults aft, hangar and 12 flotaplanes. The game decided this ship was an AV and I couldn't get it to classify as CA, even though I should've been able to, since there are supposed to be no limitations on CA and larger ships.

Aut-reclassified to AV, design is now illegal because of superfiring turrets/too large guns. When I try to verify the design the game says "ship outside of parameters for AV. Would you like to reclassify?" When I press yes, the ship is reclassified from AV to AV and the game again complains that it's illegal.

Using an Ise-style BB equipped with 22 floatplanes also results in game deciding its an AV and then reclassifying from AV to AV.

While I can technically "force it" to be an AV even if its not a legal one, the ship graphic becomes borked. As per manual it should be possible to build CA, BB and BC with any amount of floatplanes.

[janxol]

Tested in 1.24. The issue is also present.

[janxol]

Not sure if it was seen, or skipped under the radar, but this issue is currently preventing any sort of hybrid floatplane carrier or aviation cruiser, which in turn annoys one of my inner admirals, so I am just going to bump it in case it wasn't noticed.
Bump.

[williammiller]

I'll add this to our internal issue list for checking and resolution.

Thanks.

[janxol]

Some possible additional information: I have experienced the bug in 1.23 and 1.24, but other people on discord have confirmed that it works fine in 1.19 and 1.20. I am unsure whether the issue was intorduced between these versions or if its my particular install that is for some reason borked. I doubt it, since I tested without mods, but theres always that possibility, as I am unsure if other people experienced the issue with 1.24.