8000 [Issue] Aging Reputation Effects · Issue #7087 · MegaMek/mekhq · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

[Issue] Aging Reputation Effects #7087

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

Open
5 tasks done
SirChaos1 opened this issue May 22, 2025 · 0 comments
Open
5 tasks done

[Issue] Aging Reputation Effects #7087

SirChaos1 opened this issue May 22, 2025 · 0 comments

Comments

@SirChaos1
Copy link

Brief Description *

With aging effects enabled, personnel in Clan campaigns receive a +150 reputation bonus at age 31, and another at age 51, rather than the penalties outlined in documentation.
I don´t know if this is RAW, but the reputation effect affects all personnel, when it should probably only affect combat personnel, or even just only trueborn combat personnel (and honestly, in most clans freeborn combat personnel should probably be getting a blanket reputation penalty regardless of age).

Also, it appears that bonuses to skills from the early age milestones are capped at +1, whereas the documentation suggests that, for example, personnel in the 31-40 age bracket should be getting +1 each from both attributes in skills that are tied to any two skills that are not Dexterity or Charisma (like Administration).

Lastly, the documentation states that, at age 101, characters lose 15 Charisma - I assume that this is a typo and it is supposed to be 1.5?

3. Steps to Reproduce

Start a campaign with a Clan faction, enable aging effects, and generate personnel aged 31+.

Attach Files

No response

Severity *

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

MekHQ Suite Version *

0.50.06

Operating System *

Windows 10

Java Version *

17.0.11

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
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

No branches or pull requests

1 participant
0