8000 [Issue] OPFOR in Stratcon missions uses ammo types not existing in the time period of the campaign · Issue #6833 · MegaMek/mekhq · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

[Issue] OPFOR in Stratcon missions uses ammo types not existing in the time period of the campaign #6833

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.

Sign up for GitHub

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

Jump to bottom
Open
5 tasks done
Gantolandon opened this issue Apr 30, 2025 · 0 comments
Open
5 tasks done

[Issue] OPFOR in Stratcon missions uses ammo types not existing in the time period of the campaign #6833

Gantolandon opened this issue Apr 30, 2025 · 0 comments
Labels
Bug MM/MML-origin MHQ Issues Severity: Low Issues described as low severity as per the new issue form

Comments

@Gantolandon
Copy link

Brief Description *

Tandem Charge ammo was introduced to the Inner Sphere after the Clan Invasion. It shouldn't be available in 3014; it certainly isn't when I try to order it. Unfortunately, OPFOR still mounts it on their mechs, and it happens pretty often.

It wouldn't be that bad if it weren't the ammo that's almost guaranteed to cause through-armor criticals.

3. Steps to Reproduce

  1. Load the provided save.
  2. Start the "Frontline Disruption" mission.
  3. Check the SRM ammo used by the enemy Battlemaster.

Attach Files

Undine's Stormwatch Blackguards30150425.cpnx.gz

logs.zip

Severity *

Medium (Gameplay Limitation): Non-core functionality is impaired, providing a suboptimal but playable experience.

MekHQ Suite Version *

0.50.05

Operating System *

Windows 10 10.0 (amd64)

Java Version *

Eclipse Adoptium 17.0.14

Final Verification

  • I confirm this is a single, unique issue that hasn't been reported before
  • I have filled and provided all necessary information above
  • I have included any and all logs, custom units, and CPNX (save) files
  • 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
@Scoppio Scoppio added Bug Severity: Low Issues described as low severity as per the new issue form MM/MML-origin MHQ Issues labels May 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Bug MM/MML-origin MHQ Issues Severity: Low Issues described as low severity as per the new issue form
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Gantolandon @Scoppio
0