|
Overkenshin -> BUG: Supply (6/8/2020 7:32:06 AM)
|
There seems to be a very serious supply/ammo bug in LSA which has currently not been reported. It doesnt seem to be present on the main list of outstanding issues compiled by Tejszd.
BGs that have their line of supply between the BG as the deppot blocked by a contested map STILL recieve supply and ammo points each turn (signified by the + signs), even if there is no path of VLs through the contested map. The map being contested at all is enough for supply replenshment to still be received. This makes it virtually impossible to cut the supply of an enemy group. All the enemy needs to turn is move in to contest the map in between for a single turn, and supply for the supposedly cut off group is reestablshed
This is in direct contradiction to what is written in the manual about supply (see attachment).
[img]https://i.ibb.co/377Mgqm/LSA-supply-bug-capture-1.png[/img]
Please review the images below:
The allied battle group moves around the german and cuts the line of supply to the german major depot. This works as it should and supply and ammo get the X X signs.
But when the german group moves to contest the map in between, even after the battle is finished and they do NOT have a path of VLs through the map or the exit to the supply depot map, they still receive supply + +
image 1: Shows start locations on the strat map. German BG starts on major depot
image 2: German BG has moved into Elst and Allied BG moves around them into Driel, cutting supply
image 3: German BG moves back into Driel attacking into into the allied occupied map, Supply is reestablished even before the battle
image 4: Battle map deployment shots NO link of VLs throug the map to the depot
image 5: Battle completed, supply still intact
[img]https://i.ibb.co/zPQQR80/LSA-1.png[/img] [img]https://i.ibb.co/XDLRD1p/LSA-3.png[/img] [img]https://i.ibb.co/FhLtDPv/LSA-4.png[/img] [img]https://i.ibb.co/j5k0DD5/LSA-5.png[/img] [img]https://i.ibb.co/m4C945v/LSA-6.png[/img]
Here is a link to a previous thread, where mickxe5 reports the bug and sibsequently realises it has been fixed as of ver .53
https://www.matrixgames.com/forums/tm.asp?m=4086682
But I am reproducing this bug in version 6.00.01
I would like to urge Matrix to see if they can reproduce this bug in the current version.
|
|
|
|
