MegaMek / megamek

MegaMek is a networked Java clone of BattleTech, a turn-based sci-fi boardgame for 2+ players. Fight using giant robots, tanks, and/or infantry on a hex-based map.
http://www.megamek.org
GNU General Public License v2.0
295 stars 282 forks source link

[0.48] - Bug Report - Initiative bug with small craft and ASF when winning initiative, in an aerospace-only combat #3510

Open UlyssesSockdrawer opened 2 years ago

UlyssesSockdrawer commented 2 years ago

Environment

MM Version: 0.48 OS: Windows 10 Java Version: OpenJDK 11

Description

Player has a small craft and an aerospace fighter on their side. Bot/opponent has a single aerospace fighter.

Player wins initiative and is forced to move both the small craft and ASF before the bot/opponent has to move.

image

Rules References: Total Warfare Page 76 for movement order for small craft vs. aerospace StratOps Page 50

Steps to reproduce:

Give one player an ASF and small craft Give opponent one ASF

Give player with ASF & small craft an init bonus to guarantee init win

Player will be forced to move both ASF and small craft first despite winning init (Delete the above lines)

Files

No save file available.

gsparks3 commented 1 year ago

Posting to add further notes: this affects space-map battles as well as atmospheric map. The effect seems to be that if you have N small craft, you will also have to move N fighters before any of the enemy's fighters move, regardless of whether you won or lost initiative. This causes extreme distortion of the initiative order if the number of small craft on one side is similar to the number of fighters on that side, up to having to move all of your fighters before any of the enemy fighters move.

Any type of aerospace unit other than small craft does not seem to have this effect.

However, as of my testing on version 0.49.13, this issue appears to have been resolved - a quick test on default settings did not show the issue. Just to be sure, since my previous testing on 0.48 had many non-default game options, I confirmed that the issue remains present in 0.48 when using default Game Options. Not sure exactly what changed to fix the issue.