KP#13: Poor Optimisation Result (Lock)

Reported
18 Jan 2020, v1.5.2 (Derwish77)
Description
The following command line leads to a poor optimisation result: “-Camp=JuHolz#11 -Objective=Lock -Attack=*BSK;*GSS;Tav“. It leads to 188BSK;Tav ==> [140-182,5-280]s Dauer, [1.140-1.346,2-1.428,8]PLV, PlrDd [150-177,1-188]BSK;[0-0,4-1]Tav, [2.780-3.797,7-3.990]EP, EnmDd 70Sa;[15-61,3-70]Re;[0-0,6-1]RLL , i.e. a fight that is guaranteed to last 140s. But actually the following simulation shows there is a better configuration: “-Mode=Simulate -Camp=JuHolz#11 -Attack=150BSK;10GSS;Tav” with 150BSK;10GSS;Tav ==> 99% Siege, 1.099,02PLVMix, [180-200,0-220]s Dauer, [1.033,6-1.099,0-1.298]PLV, [3.710-3.988,8-3.990]EP, PlrDd [136-144,3-150]BSK;[0-0,2-10]GSS;[0-0,0-1]Tav, EnmDd [62-70,0-70]Sa;70Re;[0-1,0-1]RLL , so that’s 180s guaranteed duration. Original post in the German forum thread.
Analysis
To be done. This reads very similar to KP#3. KP#3 and its solution however do not apply to Lock optimisations.
Solution
To be found.
Scheduled
To be scheduled.