About: Spring 2016 Event/E-6   Sponge Permalink

An Entity of Type : dbkwik:resource/xoykDFxJFBgF02W_HRnEzw==, within Data Space : 134.155.108.49:8890 associated with source dataset(s)

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.

AttributesValues
rdf:type
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.
dbkwik:kancolle/pr...iPageUsesTemplate
Label
Value
  • Events/Mechanics
  • Normal:
  • Easy:
  • Hard:
  • Easy: 5 kills
  • Easy: 2800
  • Hard: 5400
  • Normal/Hard: 6 kills
  • Normal: 4800
Romaji
  • Yūgun hakuchi Dakkan sakusen
Kanji
  • 友軍泊地奪還作戦
Title
  • Friendly anchorage Recapturing Strategy File:Spring 2016 Event Ship Tag Task Force.png
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.
Alternative Linked Data Views: ODE     Raw Data in: CXML | CSV | RDF ( N-Triples N3/Turtle JSON XML ) | OData ( Atom JSON ) | Microdata ( JSON HTML) | JSON-LD    About   
This material is Open Knowledge   W3C Semantic Web Technology [RDF Data] Valid XHTML + RDFa
OpenLink Virtuoso version 07.20.3217, on Linux (x86_64-pc-linux-gnu), Standard Edition
Data on this page belongs to its respective rights holders.
Virtuoso Faceted Browser Copyright © 2009-2012 OpenLink Software