• Welcome to the Kancolle Wiki!
  • If you have any questions regarding site content, account registration, etc., please visit the KanColle Wiki Discord

Difference between revisions of "User:Fujihita"

From Kancolle Wiki
Jump to navigation Jump to search
>Fujihita
>Fujihita
(→‎Inazuma's diary: E2 strategies)
Line 41: Line 41:
  
 
In general, the event was one of the easier events—although, personally, not much can be said since it is our fleet's first KanColle event. There are a lot of says go into the second, E2, and the fourth map, E4, since they gave us the most troubles. E1 was a give-away map and E3 could be cleared easily, but not quite as farmable as E2 or E1.</div>
 
In general, the event was one of the easier events—although, personally, not much can be said since it is our fleet's first KanColle event. There are a lot of says go into the second, E2, and the fourth map, E4, since they gave us the most troubles. E1 was a give-away map and E3 could be cleared easily, but not quite as farmable as E2 or E1.</div>
 
+
<div style="margin-left:40px;">E1 Analyses and Strategies</div>
<div style="color:navyblue;background:lightgray;border:solid 1px lightgray;border-radius:10px;padding:10px;margin:20px;">[[Jun'you]] bringing 2x Ryuusei Kai and 2x Reppuu did nicely against the Abyssal light fleets in E1. Although there was a bit of an issue when it came to T-disadvantage at boss, the extra torpedo power went a long way, focusing shelling power on heavier ships and thus saving us from troubles.
+
<div style="color:navyblue;background:lightgray;border:solid 1px lightgray;border-radius:10px;padding:10px;margin:20px;">
 +
[[Jun'you]] bringing 2x Ryuusei Kai and 2x Reppuu did nicely against the Abyssal light fleets in E1. Although there was a bit of an issue when it came to T-disadvantage at boss, the extra torpedo power went a long way, focusing shelling power on heavier ships and thus saving us from troubles.
  
 
Weakest ship in the fleet was [[Satsuki]], level 30-, unmodernized. She went into the red a lot of times until we realized the "actual" effect of Searchlight in event was making the ship carrying it fall to lower priority on the Abyssal's hit list. Admiral decided to take his chances and put nothing but Star Shell, Searchlight and damecon on Satsuki. It worked and somehow, she was no longer targeted by the enemy fleets. Repair cost dropped to about 2-3 buckets per run on average.</div>
 
Weakest ship in the fleet was [[Satsuki]], level 30-, unmodernized. She went into the red a lot of times until we realized the "actual" effect of Searchlight in event was making the ship carrying it fall to lower priority on the Abyssal's hit list. Admiral decided to take his chances and put nothing but Star Shell, Searchlight and damecon on Satsuki. It worked and somehow, she was no longer targeted by the enemy fleets. Repair cost dropped to about 2-3 buckets per run on average.</div>
 
+
<div style="margin-left:40px;">E2 Analyses and Strategies</div>
<div style="color:navyblue;background:lightgray;border:solid 1px lightgray;border-radius:10px;padding:10px;margin:20px;">The strategy deployed in E2 was probably the most unorthodox ever, a fleet of Sendai flagship and 5 DDs: 1 elite, 3 combat-ready and 1 radar mule. A pattern emerged from our map clear runs and Admiral took note of a few things.
+
<div style="color:navyblue;background:lightgray;border:solid 1px lightgray;border-radius:10px;padding:10px;margin:20px;">The strategy deployed in E2 was probably the most unorthodox ever, a fleet of Sendai flagship and 5 DDs: 1 elite, 2 combat-ready and 2 radar/searchlight mule. A pattern emerged from our map clear runs and Admiral took note of a few things.
  
 
* First, [[Yukikaze]], or any night cut-in setup ships for the matter, usually gets targeted at boss and crippled before night battle.
 
* First, [[Yukikaze]], or any night cut-in setup ships for the matter, usually gets targeted at boss and crippled before night battle.
Line 55: Line 56:
  
 
*[[Akatsuki]] was set up with night cut-in equipment and was placed one slot before [[Yukikaze]]. As a result, she became the decoy, taking all the disabling hits from boss node in place of [[Yukikaze]].
 
*[[Akatsuki]] was set up with night cut-in equipment and was placed one slot before [[Yukikaze]]. As a result, she became the decoy, taking all the disabling hits from boss node in place of [[Yukikaze]].
 +
*[[Yayoi]] was a ship shield with damecon and 1x torpedo mount and 1x star shell. Her main attacking phase was the closing torpedo salvo.
 +
*[[Mochizuki]] with radar, searchlight and damecon rarely got targeted in pre-boss night battle and pre-boss shelling, the same warding strategy used in E1.
 +
 +
With these latest adjustments, the ships that get moderately/heavily damaged after E2 shifted from slot 2 [[Yukikaze]] (almost always), slot 3 [[Ayanami]], slot 6 [[Mochizuki]] to slot 3 [[Akatsuki]] (almost always), slot 4 [[Yayoi]] and slot 5 [[Mochizuki]] (at a lower frequency). With the help of carrier support expedition, full torpedo bomber planes sinking 2-3 ships consistently at low cost, the outcome is more S-rank victories, good enough to farm there for 4 days straight, and more tolerable repair timers (since weaker and lower-leveled ships are focused).
  
(more coming soon)
+
Bucket loss ranges from 1-3 buckets per run compares to 3-5 bucket loss in the original fleet composition.</div></div></div>
</div>
 
 
*New Mikawa Fleet sortie quest cleared (11 tries)
 
*New Mikawa Fleet sortie quest cleared (11 tries)
 
<div style="color:navyblue;background:lightgray;border:solid 1px lightgray;border-radius:10px;padding:10px;margin:20px;">Strategy involves a sacrificial ship carrying Type 0 Seaplanes, attempting to gain a successful recon check. Around 47-54 effective LoS is recommended.
 
<div style="color:navyblue;background:lightgray;border:solid 1px lightgray;border-radius:10px;padding:10px;margin:20px;">Strategy involves a sacrificial ship carrying Type 0 Seaplanes, attempting to gain a successful recon check. Around 47-54 effective LoS is recommended.

Revision as of 09:05, 12 December 2014

Combined fleet

We have a new Reppuu queen!

Cf c.png Highlight

In an amazing streak of luck, Carrier division 1, Fleet carrier Kaga has led the daily crafting team to unbelievable breakthrough, accomplishing a months worth of plane development in one morning.

Three Reppuu (Strong Gale) were finished within mere four attempts.

An honorable mention in the Combined Fleet board for the new Reppuu Queen is all but a small reward to the long list of achievements she had attained in crafting and in battle.

On an unrelated note, the previous title holder was Akagi.

Searchlight.png Hall of Fame

  • Akatsuki - excellent performance in E2, Fall 2014 Event E2

Destroyer division 6

Inazuma's diary

EmergencyRepair.png Craft
LandingCraft.png Ship
RedGunLight.pngSortie
  • World 5-2 cleared
  • Second Carrier Division sortie quest cleared (1 attempt)
  • Destroyer Division 30 (1st Gen.) sortie quest cleared (2 attempts)
Straight up night double attack setup for elite DDs, damecon on Mutsuki and Kisaragi along with boilers. Flagship carries Searchlight. Kirasagi sank at boss and expended a damecon but they managed S-rank victory and quest clear. Sparkling is not necessary for weaker DDs but it is recommended for stronger ones
A long list of newcomers in this event: Suzuya, Akizuki, Akigumo, Prinz Eugen, Nowaki, Hayashimo, Harusame, Ooyodo, Naganami, Asagumo, Maikaze, Taigei, extra Maruyu and extra Mikuma. In general, the event was one of the easier events—although, personally, not much can be said since it is our fleet's first KanColle event. There are a lot of says go into the second, E2, and the fourth map, E4, since they gave us the most troubles. E1 was a give-away map and E3 could be cleared easily, but not quite as farmable as E2 or E1.
E1 Analyses and Strategies

Jun'you bringing 2x Ryuusei Kai and 2x Reppuu did nicely against the Abyssal light fleets in E1. Although there was a bit of an issue when it came to T-disadvantage at boss, the extra torpedo power went a long way, focusing shelling power on heavier ships and thus saving us from troubles.

Weakest ship in the fleet was Satsuki, level 30-, unmodernized. She went into the red a lot of times until we realized the "actual" effect of Searchlight in event was making the ship carrying it fall to lower priority on the Abyssal's hit list. Admiral decided to take his chances and put nothing but Star Shell, Searchlight and damecon on Satsuki. It worked and somehow, she was no longer targeted by the enemy fleets. Repair cost dropped to about 2-3 buckets per run on average.
E2 Analyses and Strategies
The strategy deployed in E2 was probably the most unorthodox ever, a fleet of Sendai flagship and 5 DDs: 1 elite, 2 combat-ready and 2 radar/searchlight mule. A pattern emerged from our map clear runs and Admiral took note of a few things.
  • First, Yukikaze, or any night cut-in setup ships for the matter, usually gets targeted at boss and crippled before night battle.
  • Second, the rest of the map on and after last dance (referring to the last boss kill needed to clear a map) appeared to prefer damaged and weak ships, while at boss Tsu-class and Destroyer princess preferred disabling ships, preventing closing torpedo and night battling. The exception to this rule happened when a heavily damaged ship was brought into a boss fight. Ships at boss would then prefer targeting and sinking the heavily damaged ship.
  • Finally, evasion cannot stop the Abyssal fleet at boss node, either their accuracy is unbelievably high, or goddess luck is on their side.

When improving your own strategy doesn't help, adapting to your enemy strategy will, So Admiral devised a countermeasure according to the above:

  • Akatsuki was set up with night cut-in equipment and was placed one slot before Yukikaze. As a result, she became the decoy, taking all the disabling hits from boss node in place of Yukikaze.
  • Yayoi was a ship shield with damecon and 1x torpedo mount and 1x star shell. Her main attacking phase was the closing torpedo salvo.
  • Mochizuki with radar, searchlight and damecon rarely got targeted in pre-boss night battle and pre-boss shelling, the same warding strategy used in E1.

With these latest adjustments, the ships that get moderately/heavily damaged after E2 shifted from slot 2 Yukikaze (almost always), slot 3 Ayanami, slot 6 Mochizuki to slot 3 Akatsuki (almost always), slot 4 Yayoi and slot 5 Mochizuki (at a lower frequency). With the help of carrier support expedition, full torpedo bomber planes sinking 2-3 ships consistently at low cost, the outcome is more S-rank victories, good enough to farm there for 4 days straight, and more tolerable repair timers (since weaker and lower-leveled ships are focused).

Bucket loss ranges from 1-3 buckets per run compares to 3-5 bucket loss in the original fleet composition.
  • New Mikawa Fleet sortie quest cleared (11 tries)
Strategy involves a sacrificial ship carrying Type 0 Seaplanes, attempting to gain a successful recon check. Around 47-54 effective LoS is recommended.

The key point to achieve victory at boss node is to survive Wo-class's opening airstrike with minimal damage. A successful recon check significantly lessens the otherwise devastating bombing damage (with up to 3 ships in red) and gives bonus accuracy and in shelling phase. Cut-in setup with 2x main gun and 1x secondary gun on high luck ships to maximize night battle capability. Double attacks deal scratch damage to Ru-class and Wo-class.

Anti-air guns and radars do nothing against Wo-class's airstrike and the fleet doesn't have enough firepower to take care of boss this way.

Hibiki's bookshelf

FlareIcon.png
Exped Time Flag Fleet Drum Lvl
5 1:30 3 1CL 2DD 1XX
21 2:20 15 1CL 4DD Drum.png x3 30
37 2:45 50 1CL 5DD Drum.png x4 200
38 2:55 65 5DD 1XX Drum.png x8 250
11 5:00 6 2DD 2XX
12 8:00 4 2DD 2XX
36 9:00 30 2AV 1CL 1DD 2XX
15 12:00 8 2CV 2DD 2XX
16 15:00 10 1CL 2DD 3XX

Akatsuki's wardrobe

074 3.png

Admiral, we need a bigger dock for Yamato-san
Admiral, another Mikuma is here, kuma...um, nanodesu!
Admiral, poking Inazuma is no good, you know?
Me? Don't poke me either!

073 3.png