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

Planetary Acquisition can infinite loop under certain conditions #1447

Closed
sixlettervariables opened this issue Feb 2, 2020 · 3 comments · Fixed by #1451
Closed

Planetary Acquisition can infinite loop under certain conditions #1447

sixlettervariables opened this issue Feb 2, 2020 · 3 comments · Fixed by #1451

Comments

@sixlettervariables
Copy link
Contributor

Updated information: It appears an issue with Planetary acquisition in Campaign Options is the root of this bug. While solved on a short term basis, leaving this for future attempts to resolve the underlying problem for others. (Turning Planetary acquisition off solved all the problems, my suspicion is it's related to purchasing in general, but I'm not a coder anymore, and I have no clue.)

Edit note: Other issue about internal to MHQ MML in unoffical tech level not showing battlearmor bays in Transport bays remains.

Originally posted by @MageOhki in #1444 (comment)

@servo01
Copy link

servo01 commented Feb 2, 2020

ANY part acquisition roll is causing my fresh install of 47.3 to lock completely. - Even with planetary acquisition turned off.

sixlettervariables added a commit to sixlettervariables/mekhq that referenced this issue Feb 2, 2020
@sixlettervariables
Copy link
Contributor Author

Fixed that as well @servo01, thanks for the heads up.

sixlettervariables added a commit that referenced this issue Feb 3, 2020
…cquisition-infinite-loop

Bug: Don't infinite loop in acquisition logic #1447
@sixlettervariables
Copy link
Contributor Author

Fixed in #1448.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants