Skip to content
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

Issue when Resolving Scenarios with the Bad Intel modifier #1631

Closed
CrimsonThunderSB opened this issue Apr 4, 2020 · 4 comments · Fixed by #1777
Closed

Issue when Resolving Scenarios with the Bad Intel modifier #1631

CrimsonThunderSB opened this issue Apr 4, 2020 · 4 comments · Fixed by #1777

Comments

@CrimsonThunderSB
Copy link

0.47.5

For some reason, when I resolve a scenario (even when manually doing so without an actual battle), when I have a House or a Liaison unit attached to the unit, every time I have selected the bad intel modifier whether its the air or the ground modifier, the objective always counts as failed, even if its completely unscathed. This is a bit annoying as this has severely hurt my contract score for the mission I am currently on as much as a -4 contract score penalty...which I really don't need to have happen....if you need the modifier file, please let me know.

image

image

@Windchild292
Copy link
Contributor

A save file could prove useful.

@CrimsonThunderSB
Copy link
Author

Stormbringing Destroyers Bugged.zip
sorry about that...there is the file...though I don't think I saw any errors in the log file...but its a bit annoying, it occurred shortly after changing everything over to the new version,. This is even occurring when I have the template modifier with enemy artillery activated, if you even try to solve the battle scenario manually with no battle file selected, the attached unit here (being the phoenix hawk, but will occur with any mech), the objective of preserving the attached unit seems to automatically fail, even with no battle damage, and this causes the contract score to decrease by 4. I am not sure what happened.

@CrimsonThunderSB
Copy link
Author

@Windchild292 I am also trying to see where its coming from, and it looks like it may be coming from the scenario generator when you try to regenerate forces when creating the scenario...possibly

@Windchild292 Windchild292 self-assigned this Apr 29, 2020
@Windchild292
Copy link
Contributor

I've recreated this, and I think it is related to the scenario editor. I'm going to take a look into fixing this now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment