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
I am using MekHQ Version 45.4 on a Windows 10 laptop with Java 1.8.0_201.
Description
I have a contract that starts on the 17th. I have on the 16th set up the minimum 3, including 1 scout Lance ready to go. When moving to the 17th, I receive 3 contract breaches automatically. The Phoenix Hawk 3M sometimes gets damaged, I initially thought it was that, but excluded it from one test and it still happened. Attached are the Images from the 16th and 17th on one test where the PXH-3M was not damaged. Also attached are the CPNX file, Factions+Hints.xml, and a zip of the custom units being used in the Campaign so far.
I think the issue is that your force is deployed for the old C2-Diversion Raid on the 16th. Then the 17th arrives, and the contract checks for breaches before redeploying your units to the right contract, so when the contract is checking, your units are not yet assigned to it and there are the breaches.
I'll investigate how to change the order of operations so we first assign units to the contract and then check for breaches.
Environment
I am using MekHQ Version 45.4 on a Windows 10 laptop with Java 1.8.0_201.
Description
I have a contract that starts on the 17th. I have on the 16th set up the minimum 3, including 1 scout Lance ready to go. When moving to the 17th, I receive 3 contract breaches automatically. The Phoenix Hawk 3M sometimes gets damaged, I initially thought it was that, but excluded it from one test and it still happened. Attached are the Images from the 16th and 17th on one test where the PXH-3M was not damaged. Also attached are the CPNX file, Factions+Hints.xml, and a zip of the custom units being used in the Campaign so far.
Files
Dwarbithian Commandos30531016.zip
Dwarbithian Technologies.zip
2000_KellerSchultz_planets.zip
factionhints.zip
factions.zip
The text was updated successfully, but these errors were encountered: