-
Notifications
You must be signed in to change notification settings - Fork 177
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
0.49-DEV-StratCon - Saving and reloading game causes hostile contacts in AtB Campaign State to become nonresponsive #2517
Labels
Bug
Needs Investigation
This issue needs investigation and/or triage.
StratCon
Bugs relating strictly to StratCon
Milestone
Comments
Error from log:
|
Looks like the issue is that, under independent command, the dynamic AtB scenario underlying the StratCon scenario doesn't get registered with the campaign until after you commit the primary force to it. |
Fixed with 0c8de94 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Bug
Needs Investigation
This issue needs investigation and/or triage.
StratCon
Bugs relating strictly to StratCon
Environment
StratCon alpha test build (MekHQ CI with Gradle #1168: Pull request #2144)
Windows 10
OpenJDK 11.0.10
Midnight comes again
Game is saved, time for slumber
Hostile contacts broke
Description
Possibly related to #2512?
In my current save, if you advance the day, generate new hostile contacts on the AtB Campaign State tab, save the game, and reload the save, the generated hostile contacts become non-interactive (can't click on the hex, can't right click, etc). Initiating the scenario before the save/reload functions as expected and generates a scenario in the Briefing Room. I noticed also that though previously newly generated hostile contacts would show in the Command Center, the contacts generated in my save game don't show any notification.
Tangentially related, while trying to reproduce the bug so I could write this report, I was somehow able to create a scenario with a resolution date of 1 day in the past, which MekHQ wouldn't let me initiate. I wasn't able to reproduce the bug, but if I do I'll write up a separate report for it.
Files
Included both pre and post bug saves (8/23 and 8/24 respectively)
Campaign Info.zip
mekhqlog.txt
The text was updated successfully, but these errors were encountered: