8000 Potentially eroneous +4 modifier to repair/salvage - seemingly incorrect calculation of available/required astech hours · Issue #2996 · MegaMek/mekhq · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Potentially eroneous +4 modifier to repair/salvage - seemingly incorrect calculation of available/required astech hours #2996

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

Closed
OrbMonky opened this issue Dec 9, 2021 · 0 comments · Fixed by #6590
Labels
Needs Investigation This issue needs investigation and/or triage. Outdated Test against current Milestone or the latest Nightly Build Parts/Repair/Refit

Comments

@OrbMonky
Copy link
OrbMonky commented Dec 9, 2021

Environment

Windows 10
49.5
jdk-11.0.11.9-hots

Description

Specific quantities of armor seem to cause an incorrect 'shorthanded' modifier, despite plenty of available astechs. Problem is persistent through days and even if no other repairs are in progress. In this example the hangar has an Eagle which has a 36 point armor section being salvaged, but it shows 'shorthanded' regardless of the amount of astech hours available and overtime is not, and has not been used in this campaign. This issue seems to occur on large quantities of armor like 36, so it seems at first glance to be a large job that is simply too exhaustive of resources, but it doesn't change even when set to rush job 1/8 time (in this particular case that's a mere 23 minutes of work given the rest of the scenario). This also persists indefinitely going forward, the only resolution seems to be to artificially upgrade the location (transport bay to factory) or GM repair.

Files

Helena's Valkyries30261101.cpnx.gz
Helena's Valkyries.zip
mekhqlog.txt

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs Investigation This issue needs investigation and/or triage. Outdated Test against current Milestone or the latest Nightly Build Parts/Repair/Refit
3 participants
0