Skip to content
This repository has been archived by the owner on Dec 10, 2017. It is now read-only.

Setup config.ini

Jump to bottom
Minyoung Choi edited this page Feb 21, 2016 · 26 revisions

The script will load config.ini in the main kancolle-auto folder for your user settings. This allows you to quickly switch between configs by renaming them and cycling them back in as config.ini and restarting the kancolle-auto.

The config file is split up into five sections: General, ScheduleSleep, Expedition, Combat, and Quests.

General

Program — The program/window name of your Kancolle container. Make this string match the name of your Kancolle window as close as possible. If you're playing within a browser, the browser name should suffice, unless you have multiple windows of the same browser window open. If you're using another Viewer program, input its name.

  • Examples: Google Chrome, Firefox, KanColleViewer!, KanColleTool Viewer, Electronic Observer, etc

RecoveryMethod — kancolle-auto will attempt to automatically refresh your Kancolle container if you encounter a catbomb. Five refresh methods are currently supported, and you should specify which method to be used depending on the viewer you use. Browser for all webbrowsers that uses F5 as a refresh page hotkey, KC3 for KC3Kai on Google Chrome, KCV for KanColleViewer, KCT for KanColleTool, and EO for Electronic Observer. Please use None if you're not using any of these browsers, or program your own in.

  • Valid values: Browser, KC3, KCV, KCT, EO, None

Paranoia — One of the anti-bot-detection methods incorporated into kancolle-auto is a random walk through menus. This setting allows you to specify the upper bound of sidesteps the random walk can take before reaching its final destination. Set to 0 if you think the random walk is unnecessary and want to disable it entirely (not recommended).

  • Valid values: any integer 0 and above

SleepModifier — If you're encountering frequent FindFailed errors it may be due to the sleep/wait timers not being optimized for your KanColle experience. Increasing this value will increase the length of all sleep/wait timers in the game, which may help reduce the frequency of such crashes.

  • Valid values: any integer above 0

ScheduledSleep

Enabled — Define whether or not you want kancolle-auto to sleep (not play the game) for a set period of time at a set time. It is highly recommended that you enable and use this feature, as an excessive number of expeditions has been known to cause frequent catbombs.

  • Valid values: True to enable schedule sleep, False to disable

StartTime1, StartTime2 — Define a 30 minutes time window for when Schedule Sleep should start, in military time.

  • *Example: StartTime1 of 0030 and StartTime2 of 0100 means that Schedule Sleep will begin sometime between 12:30AM and 1AM.
  • *Valid values: 0000 and 2359

SleepLength — Roughly how long Schedule Sleep should last, in hours (decimals are OK). Anywhere beween 0 to 10 minutes are added randomly to the actual timer.

  • *Example: 3.5 means that kancolle-auto will sleep for a period of time between 3 hours and 30 minutes and 3 hours and 40 minutes

Expeditions

Enabled — Define whether or not you want kancolle-auto to automatically run expeditions.

  • Valid values: True to enable automatic expeditions, False to disable

Fleet2, Fleet3, Fleet4 — Define which expedition a fleet should go to.

  • Supported expeditions: 1 ~ 32, 35 ~ 40

Combat

Enabled — Define whether or not you want kancolle-auto to automatically run sorties with your main fleet.

  • Valid values: True to enable automatic sortieing, False to disable

Area — Define which world you want to sortie to. For example, if you want to sortie to 1-5, the Area would be '1'. kancolle-auto currently supports all sorties up to 6-1, including Extra Operations, but *does not support choice/decision nodes!

  • Valid values: 1 ~ 6

Subarea — Define which map you want to sortie to. For example, if you want to sortie to 1-5, the Subarea would be '5'. kancolle-auto currently supports all sorties up to 6-1, including Extra Operations, but *does not support choice/decision nodes!

  • Valid values: 1 ~ 6

Nodes — Define how many combat nodes you want to run (resource/treasure/hazard nodes do not count as a node to kancolle-auto). You can set this to any number, and it might be wise to set it to something higher than the actual number of nodes you will run to be certain that you'll run through the entire map.

  • Examples: 1 if you're running 3-2-A (1st node only), 3 or above if you're running 2-3 (Orel Cruising; all nodes)

Formations — Define which formation to use at each combat node, separate by commas. If you specify less formations than the number of Nodes, kancolle-auto will automatically use line_ahead for the remaining nodes.

  • Valid values: line_ahead, double_line, diamond, echelon, line_abreast
  • Examples: line_ahead if you're running 3-2-A (1st node only), 'line_abreast, line_abreast, line_abreast, line_abreast` if you're running 1-5 (all submarine nodes)

NightBattles — Define whether or not to engage in night battle at each combat node, separated by commas. If you specify less values than the number of Nodes, kancolle-auto will automatically use True for the remaining nodes.

  • Valid values: True to engage in night battle, False to decline night battle
  • Examples: False if you're running 3-2-A, False,True,True,True,True or just False if you're running 2-3 (Orel Cruising; night battle at everything but 1st node)

RetreatLimit — Define how much your ships can be damaged before you retreat from the sortie. kancolle-auto will automatically retreat from sortie if one or more ships are at or below this threshold.

  • Valid values: 0 for light damage, 1 for moderate damage, 2 for critical damage

RepairLimit — Define how much your ships can be damaged before you repair them. kancolle-auto will automatically repair all ships at or below this threshold before sortieing again, regardless of whether or not you retreated previously.

  • Valid values: 0 for light damage, 1 for moderate damage, 2 for critical damage

RepairTimeLimit — Define the upper limit (in full hours) of the repair timer before kancolle-auto uses a bucket to repair the ship.

  • Examples: 0 if you want all repairs to use a bucket (useful if all ships are high leveled), 1 if you want buckets to be used if the repair timer is longer than 1 hour, 999 if you never want buckets to be used

CheckFatigue — Define whether or not kancolle-auto should check fatigue/morale of your ships before sortieing. If your ships are moderately fatigued (orange sadface) kancolle-auto will wait 12 minutes before attempting to sortie again. If your ships are heavily fatigued (red sadface) kancolle-auto will wait 24 minutes before attempting to sortie again. If disabled, kancolle-auto will disregard fleet morale when sortieing.

  • Valid values: True to enable morale/fatigue checking, False to disable

PortCheck — Define whether or not kancolle-auto should do a basic check your port (ship count) for vacancies before sortieing. Useful if you're trying to farm for a specific drop. If enabled and your port becomes full, kancolle-auto will not sortie and wait 15 minutes, allowing you to modernize/scrap to make room, before attempting to sortie again. Note: kancolle-auto only knows that your port is full when you are completely maxed out! If you have a vacancy of 1 ship, it will still sortie, even if the number of potential drops is greater than 1!

  • Valid values: True to enable port checking, False to disable
Clone this wiki locally