The Fall 2016 event Announcement! The Third Fleet Operation Act is schedule to begin on November 18th, 2016 following the November 4th Update.
Currently the theme of the event is speculated to be based upon the "Third Fleet Operation Act", an operation to attempt to eliminate the US Carrier forces. This operation begins from the aftermath of the Doolittle Raid in which the Japan made an attempt to intercept and try to take out the USS Hornet, all the way to the Battle of the Coral Sea, which was the last major attempt at the operation before the Decisive Battle at Midway.
The KanColle staff have revealed that the event will be a normal scale operation which will consist of 5 maps" (3 Main + 2 Extra Operations), will require a large expansive fleet, and will require to have multiple fleets for harder difficulties. Additionally, it has been revealed that one of the new ships will be the American Aircraft Carrier Saratoga, and the recent KanColle Festival de Beaujolais Nouveau has revealed the face and voice of the French Seaplane Tender Commandant Teste.
The details regarding the event have revealed that the event will consist of some of the following operations:
Disclaimer: The following information is based upon a summary of World War II history and may not have any influence with the game itself. This is for historic reference only.
Post Doolittle Raid
Following the American's attack on the Japan's mainland on the Doolittle Raid (which resulted in several of Japan's main key structures taking major damage and Ryuuhou being damaged delaying her launch as a light carrier), Japan began to conduct a counter measure known as the "Third Fleet Operation plan" an operation to attempt to organize a fleet to take out the American Carrier forces which may threaten their operation to expand their growing boundaries across the Pacific Ocean.
The first attempt at this was to attempt to take out the USS Hornet following after the raid it conducted on the Japan Mainland. Japan would organize a fleet to attempt to intercept Hornet which consisted of:
The plan was to organize these ships to use for the operation and while most were able to participate in the operation, Standard Carriers Souryuu and Hiryuu were too far away to help assist as they were returning from the Indian Ocean Raid. The attempt to search and intercept the USS hornet would end up as a failure as they were unable to engage the American Carrier.
Information
New Ships
As of current, multiple ships have been confirmed to appear in the event which include:
Saratoga will be a reward from the the final stages of the event. [1]
The difficulty system first used in Spring 2015 Event returns: you can choose between Operation A (甲, Hard), Operation B (乙, Medium) or Operation C (丙, Easy).
Choosing A or B requires certain HQ Level (HQ Lv 35 for B / 80 for A in Spring 2015 Event).
An important note to all Admirals intending to clear the event on Hard difficulty - further (new) conditions now apply:
When switching difficulty from any other difficulty to Hard, the map's debuff mechanism (where applicable) will be reset.
Switching between any other difficulties will not reset the debuff mechanism.
If you are playing on Hard difficulty, it is necessary to preserve the strongest elements of your fleet for the final map.
Based on data that has been data-mined so far (refer to image below), it is believed that the final map utilises a separate fleet-lock on Hard mode. Do take this into account before committing any ships to the main operation.
The armor-reducing system of the Summer 2015 Event's final map, where certain nodes had to be killed to reduce boss armor, is likely to return, but in a simplified version (see above for new changes regarding this).
Operation A (甲, Hard) and Operation B (乙, Medium) will require you to have mutiple fleets ready, which suggests fleet locking (again, see above).
The initial maps will focus on transport operations (Lighter ships, such as CLs and DDs likely), while the later maps will focus on heavy ships (CVs and BBs).
Event Maps
Quick Info Table
Classification
Map
Name
Combined Fleet?
Land-Based Air Squadron?
Color of Tag
Tag Condition & Deployment Restriction
Difficulty Restrictions
Notes
Main Operation
E-1
The Maritime Transport Operation
No
No
Blue
Tagging: Ships not already color-tagged will be tagged with the color associated with the map when deployed. This tag exists on all difficulties and is not reset on remodel, etc. As per above, it is currently believed that E-5 will have an orange ship lock exclusive to Hard Mode; details to follow. Deployment Restriction: Normal or Hard: Must have either the same-colored tag or no tag. Easy: No restrictions.
No restrictions. All difficulties OK
Transportation Operation (?)
E-2
The Mainland Air Defense Battle
No
Yes
Green
In order to play these maps on hard, you must complete the previous map* on either normal or hard. (e.g., to do E-4 on hard, you must complete E-3 on normal or hard.)
Surface Battling involving Anti-Air and fighting a Carrier Task force (?)
4DD CL CAV/ CVL is the recommended composition. This routes via either A-BDEHL or A-CFHL to reach the boss node
The north route appears to be significantly easier than the south route
Using 3DD 1CL 1CVL 1FBB reaches the boss, but passes through node D
Some planes are needed to get enough LOS to reach the boss node.
Keep in mind that 0-slot seaplanes still contribute LOS (e.g. Yuubari)
Preliminary reports indicate that Kinu Kai Ni may contribute extra to reducing the transport bar; in addition to her high ASW, this makes her an excellent ship for this map.
Show/Hide Nodes and Enemy Encounters
Nodes and Enemy Encounters
Node
Pattern
Xp
Node Info
Form
A Active Branching
Pattern 1
Active Branching
B 任務部隊 偵察潜水艦 II群 Recon Task Group Submarine Group II
STF is not nearly as recommended due to the air strength of the enemy composition, but for easier difficulties it can be doable. 2 BB, 3 CA, 1 CV, / 1 CL, 2 CLT, 3DD.
Reports suggest there may be unique historic fleet composition which requires you to have 5-7 ships
The following ships are expected to work in terms of routing the shortest possible route: