[Issue] Enemy DropShip will not generate for Deep Raid Mission (Nightly 1855) · Issue #6956 · MegaMek/mekhq · GitHub
More Web Proxy on the site http://driver.im/
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The enemy drop ship for the Deep Raid scenario will not deploy. I will also note that I have had a continuing issue on nightly builds before this and 50.05 that Allied Dropships will not be generated for Isolated Dropship missions, however regenerating those scenarios allows the dropship to generate. This scenario, even when regenerated, will not generate a dropship
3. Steps to Reproduce
Generate a Deep raid scenario, however, currently not reproduced at this time.
I'm unable to replicate the issue locally, but I do notice you have the option enabled that means your DropShips can be drawn into scenarios.
Can I confirm that you haven't reset the deployment for this scenario? Usually an empty DropShip force like this means that one of your DropShips was drawn into the scenario. However, if you reset deployment that DropShip will be removed leaving you with just the empty force.
Brief Description *
The enemy drop ship for the Deep Raid scenario will not deploy. I will also note that I have had a continuing issue on nightly builds before this and 50.05 that Allied Dropships will not be generated for Isolated Dropship missions, however regenerating those scenarios allows the dropship to generate. This scenario, even when regenerated, will not generate a dropship
3. Steps to Reproduce
Generate a Deep raid scenario, however, currently not reproduced at this time.
Attach Files
customs.zip
logs.zip
CPNX.zip
Severity *
High (Major Disruption): A major feature is broken or incorrect, but a workaround exists.
MekHQ Suite Version *
v0.50.06-nightly-2025-05-11
Operating System *
Java Version *
Final Verification
The text was updated successfully, but these errors were encountered: