Double Line formation chosen instead of Vanguard

[perryhuynh]

Environment details

• kcauto version (version on first line of CHANGELOG.md): 6.0.0
• Viewer/browser: Chromium
• Operating system and/or VM: Xubuntu 16.04

Issue variability

Consistent

Issue

Upon arriving at a combat node the script chooses double line although vanguard is specified

Log

[2018-09-08 17:58:25] Beginning combat sortie.
[2018-09-08 17:58:43] Fleet at Node #1
[2018-09-08 17:58:43] Custom formation specified for node #1.
[2018-09-08 17:58:43] Engaging the enemy in vanguard formation.
[2018-09-08 17:58:44] Engaging the enemy in vanguard formation.
[2018-09-08 17:58:45] Engaging the enemy in double line formation.
[log] CLICK on L(949,400)@S(0)[0,0 1920x1080] (531 msec)
[2018-09-08 17:59:26] No night battle specified for node #1.
[2018-09-08 17:59:26] Declining night battle.
[log] CLICK on L(517,481)@S(0)[0,0 1920x1080] (537 msec)
[2018-09-08 17:59:39] Fleet 1 damage counts: 0 heavy / 0 moderate / 0 minor
[2018-09-08 17:59:50] Continuing sortie.
[log] CLICK on L(514,483)@S(0)[0,0 1920x1080] (546 msec)
[2018-09-08 18:00:10] Fleet at Node #2
[2018-09-08 18:00:10] Custom formation specified for node #2.
[2018-09-08 18:00:10] Engaging the enemy in vanguard formation.
[2018-09-08 18:00:11] Engaging the enemy in vanguard formation.
[2018-09-08 18:00:12] Engaging the enemy in double line formation.
[log] CLICK on L(949,400)@S(0)[0,0 1920x1080] (528 msec)

Config

[Combat]
Enabled: True
Engine: legacy
Fleets:
Map: E-1
FleetMode:
RetreatNodes: 3
NodeSelects:
Formations: 1:vanguard, 2:vanguard, 3:line_abreast
NightBattles:
RetreatLimit: heavy
RepairLimit: minor
RepairTimeLimit: 0100
LBASGroups:
LBASGroup1Nodes:
LBASGroup2Nodes:
LBASGroup3Nodes:
MiscOptions: CheckFatigue

[mrmin123]

Vanguard and combined fleet formations were never updated after phase 2. I'll need screenshots to update, until then they are not supported.

…

On Sat, Sep 8, 2018, 18:41 Perry Huynh ***@***.***> wrote: Environment details - kcauto version (version on first line of CHANGELOG.md): 6.0.0 - Viewer/browser: Chromium - Operating system and/or VM: Xubuntu 16.04 Issue variability Consistent Issue Upon arriving at a combat node the script chooses double line although vanguard is specified Log [2018-09-08 17:58:25] Beginning combat sortie. [2018-09-08 17:58:43] Fleet at Node #1 [2018-09-08 17:58:43] Custom formation specified for node #1. [2018-09-08 17:58:43] Engaging the enemy in vanguard formation. [2018-09-08 17:58:44] Engaging the enemy in vanguard formation. [2018-09-08 17:58:45] Engaging the enemy in double line formation. [log] CLICK on ***@***.***(0)[0,0 1920x1080] (531 msec) [2018-09-08 17:59:26] No night battle specified for node #1. [2018-09-08 17:59:26] Declining night battle. [log] CLICK on ***@***.***(0)[0,0 1920x1080] (537 msec) [2018-09-08 17:59:39] Fleet 1 damage counts: 0 heavy / 0 moderate / 0 minor [2018-09-08 17:59:50] Continuing sortie. [log] CLICK on ***@***.***(0)[0,0 1920x1080] (546 msec) [2018-09-08 18:00:10] Fleet at Node #2 [2018-09-08 18:00:10] Custom formation specified for node #2. [2018-09-08 18:00:10] Engaging the enemy in vanguard formation. [2018-09-08 18:00:11] Engaging the enemy in vanguard formation. [2018-09-08 18:00:12] Engaging the enemy in double line formation. [log] CLICK on ***@***.***(0)[0,0 1920x1080] (528 msec) Config [Combat] Enabled: True Engine: legacy Fleets: Map: E-1 FleetMode: RetreatNodes: 3 NodeSelects: Formations: 1:vanguard, 2:vanguard, 3:line_abreast NightBattles: RetreatLimit: heavy RepairLimit: minor RepairTimeLimit: 0100 LBASGroups: LBASGroup1Nodes: LBASGroup2Nodes: LBASGroup3Nodes: MiscOptions: CheckFatigue — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#241>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEIF0hJizoi9mXh6iAq_FEhgDJSQiXQUks5uZHGqgaJpZM4WgGhV> .

[perryhuynh]

I created my own vanguard asset

from this

And it seems to be working fine