8000 [Issue] Force generator not characterizing C3 master systems correctly · Issue #7234 · MegaMek/megamek · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

[Issue] Force generator not characterizing C3 master systems co 9DB5 rrectly #7234

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
4 tasks done
SuperStucco opened this issue Jun 10, 2025 · 0 comments
Open
4 tasks done

[Issue] Force generator not characterizing C3 master systems correctly #7234

SuperStucco opened this issue Jun 10, 2025 · 0 comments

Comments

@SuperStucco
Copy link
Collaborator

Brief Description *

When units are loaded into ModelRecord objects for use in randomly selecting units, they are characterized along a range of factors, such as Clan/mixed tech or IS-only, how well they perform at anti-aircraft and anti-infantry, and so on. One of these factors is what C3 equipment it includes, so units can be identified as having C3 master/slave unit and whether that unit is standard or boosted type.

Identification of C3 masters is currently failing. This is done at ModelRecord line 545 (standard C3 master) and line 552 (boosted C3 master).

if (eq.hasFlag(WeaponType.F_C3M)) { ... } else if (eq.hasFlag(WeaponType.F_C3MBS)) {

Stepping through code fails to drop into this if-block, so the eq.hasFlag(...) method is not detecting if equipment is a C3 master/boosted master. This prevents deliberate selection of C3 master carrying units in random unit selection.

3. Steps to Reproduce

No response

Attach Files

No response

Severity *

High (Major Disruption): A major feature is broken or incorrect, but a workaround exists.

MegaMek Suite Version *

MegaMek v0.50.07 (latest)

Operating System *

Windows 10 10.0

Java Version *

Eclipse Adoptium 17.0.11

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@SuperStucco
0