This HTML5 document contains 29 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

Subject Item

n2:

rdf:type

n9:

rdfs:label

Spring 2016 Event/E-6

rdfs:comment

Using 4 carriers starts at start point 1. * Fast fleet will route A → C. * Slow fleet routes A → B → C. * C → F → H is guaranteed routing. * H → N is more likely to occur when there is no Fast Battleship in Escort fleet. * H → K → M → N is more likely to occur otherwise. * Offroute condition for K → P unknown. Using 2 carriers starts at start point 2. Using 3 carriers starts at start point 3.

n11:wikiPageUsesTemplate

n12: n13: n15: n16: n18: n19: n20: n21: n22:

n3:

Reward Kills required n17: Mechanics

n4:

Normal: 4800 Normal/Hard: 6 kills n7: Easy: 2800 Easy: 5 kills Hard: Hard: 5400 Normal: Easy:

n6:

Yūgun hakuchi Dakkan sakusen

n10:

友軍泊地奪還作戦

n5:

Friendly anchorage Recapturing Strategy File:Spring 2016 Event Ship Tag Task Force.png

n14:abstract

Using 4 carriers starts at start point 1. * Fast fleet will route A → C. * Slow fleet routes A → B → C. * C → F → H is guaranteed routing. * H → N is more likely to occur when there is no Fast Battleship in Escort fleet. * H → K → M → N is more likely to occur otherwise. * Offroute condition for K → P unknown. Using 2 carriers starts at start point 2. * D → G → F → H normally occurs. * LOS check? G → F, upon failing G → O. * H → N is more likely to occur when there is no Fast Battleship in Escort fleet. * H → K → M → N is more likely to occur otherwise. * Offroute condition for K → P unknown. Using 3 carriers starts at start point 3. * E → I → K → M normally occurs. * Offroute condition for K → P unknown. * Having only two carriers in your fleet can guarantee M → N routing. To achieve the condition of having only two carriers in your fleet while still starting at point 3, you can send a carrier back home via FCF escort before the node. * There might be a higher chance to go M → N if there is 1CVL+2CV/CVB rather than 3CV/CVB (Requires Confirmation). * M → L is more likely to occur when there is Fast Battleship in Escort fleet. * In KC3 prior to Version 30.1.0, node L is displayed as N. Players who experiences this are recommended to perform a data backup before upgrading KC3 to latest version. * M → L → J → N is more likely to occur otherwise. * Offroute condition for J → O unknown.