MekHQ generating missions with BV:0, aka.: No enemies or allies

[Scoppio]

Environment

MekHQ version 0.48.0 Mac OS 12.3.1 Java - java: 17.0.6-tem

Description

Playing AtB, with setup almost identical to the one in the docs.

An Objective Raid contract, every scenario that is generated has all enemy and ally forces set to BV: 0 In the campaign file that I am sending attached has the contract, you can reproduce the problem by simply advancing the day, so new missions are generated, they always are generated with the BV: 0.

In the megameklog.txt I can see the following errors logged:

21:59:37,972 ERROR [mekhq.campaign.mission.AtBScenario] {AWT-EventQueue-0} 
setStandardMissionForces(), line 726 : Entity for ally bot is null

21:59:37,984 ERROR [mekhq.campaign.mission.AtBScenario] {AWT-EventQueue-0} 
setStandardMissionForces(), line 726 : Entity for ally bot is null

Files

megameklog.txt Autosave-1-Ikora's Sons-30060601.cpnx.gz mekhqlog.txt

[Thom293]

I haven't opened it but see if you change the ally or enemy to another entity in the EDIT Mission pane. That might fix it so you can keep playing.

[Scoppio]

Hi @Thom293, I changed the enemy and the ally to other entities (Draconis to Pirates, and the ally federated suns to Lyran), changed the objective to planetary assault, deleted the old scenary and advanced the game until it created a new one automatically, generated another BV: 0 scenario

this was the log it generated

10:30:02,902 ERROR [mekhq.campaign.mission.AtBScenario] {AWT-EventQueue-0} 
setStandardMissionForces(), line 712 : Entity for player-controlled allies is null

I will create another campaign and see if this changes anything.

[Thom293]

I'm not at my computer. But leave DC as the enemy and change ally to Free Worlds League. Dont need to change contract type. And then do the rest of the stuff you did again.

What year is it in your campaign? Edit: oh looks like 3006.

[Scoppio]

But leave DC as the enemy and change ally to Free Worlds League. Dont need to change contract type. And then do the rest of the stuff you did again.

Tried that now with the first save, same result with BV:0 scenarios.

---

I also created a new campaign to test if its my current setup/installation or what, and it works, I don't know the difference between both, but it works in the new campaign. So, I understand its not such a "big" issue/bug but it would be very interesting to find out why the first is bugged (also, it took me 2 hours to make the entire setup of the first...)

[Thom293]

Sorry I wa thinking it may be the old Lyran/Davion?/FedCom thing, but it's the wrong year. I'm stumped. Sorry I could not help.

[Scoppio]

Looks like the problem may be the fact that I did not use the "Generated RATs"

[Duuvian]

mekhq-windows-0.49.13-SNAPSHOT MekHQ Nightly CI number 1078 Windows 10 Java Vendor: Eclipse Adoptium Java Version: 11.0.16.1

I had a similar issue with a single scenario.

Here is the note I took when it happened: A generated AtB stratcom scenario didn't grab a force from the toe and roll an opposing force. Assigning a force from the ToE sends it to the scenario, but does not update the scenario with an opposing force. Right click on scenario in the list, EDIT, then Generating a bot force supplies an opposing force. This allows the scenario to proceed, however without mission modifiers such as integrated allies as the contract specifies or forces from bases on the map.

Pleasurebots30230423.cpnx.gz mekhq.log