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

[0.50.02] Weekly stock check says wrong number of parts that have insufficient stock levels #5687

Open
4 tasks done
Dark-Hobbit opened this issue Jan 7, 2025 · 0 comments
Labels
Severity: Low Issues described as low severity as per the new issue form

Comments

@Dark-Hobbit
Copy link

Brief Description *

When the autoLogistics module does a weekly check for parts that are under target stock percentage, it shows the wrong number in report. I think the number of missing part types stated (449 in this case) is actually the total number of parts that the module checked, and not how many it ended up putting orders for (11 in this case).

Screenshot

3. Steps to Reproduce

  1. Put default stock percentage at the level where it can find some parts to resupply.
  2. Wait for weekly tick on Monday.
  3. Compare the report number with actual orders.

Attach Files

Siberian Shamans30400406.cpnx.gz
customs.zip

Severity *

Low (Minor/Nuisance): Minor glitches or cosmetic issues that don't affect gameplay and occur rarely.

MekHQ Suite Version *

0.50.02

Operating System *

Windows 11

Java Version *

Eclipse Adoptium 17.0.13

Final Verification

  • I confirm this is a single, unique issue that hasn't been reported before
  • I have included all necessary information and files to help reproduce this issue
  • I have asked on MegaMek Discord about this issue
  • I have confirmed this issue is being opened on the correct repository: MegaMek, MegaMekLab, or MekHQ
@HammerGS HammerGS added the Severity: Low Issues described as low severity as per the new issue form label Jan 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Severity: Low Issues described as low severity as per the new issue form
Projects
None yet
Development

No branches or pull requests

2 participants