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

Accidental Fall from above from building collapse Incorrect damage to target #6388

Open
4 tasks done
mandalorewise01 opened this issue Jan 11, 2025 · 0 comments
Open
4 tasks done
Labels
Bug Severity: High Issues described as high severity as per the new issue form

Comments

@mandalorewise01
Copy link

mandalorewise01 commented Jan 11, 2025

Brief Description *

Accidental Fall Incorrect Damage

In attempting to test intentionally preforming an accidental fall from above, I noticed that the damage dealt to the target of the fall did not match the Total Warfare or the BMM damage formula. (page 57 BMM, matches the rule in TW)

The damage from the building collapsing to both units and the fall damage to the "attacker" are all correct, but the listed collision damage to the target wraith seems to stop at the pilot hit.

Uncertain if this is considered a "Major" or "Minor" feature, I'm leaning towards this being a major feature due to the rule being located within PSR rules.

3. Steps to Reproduce

  1. On the Desert airbase number 2 map, have two >40ton mechs capable of 4+ jump. (we used wraith TR1s with 4/4 pilots)
  2. The unit that lost Initiative walks/runs into a building on level 0 (in the test, We used hex 0903)
  3. The unit that won Initiative then jumps onto the roof of the building, triggering an immediate collapse.
  4. Succeed the Collision roll

Attach Files

logs.zip

Severity *

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

MegaMek Suite Version *

0.50.1

Operating System *

Platform: Windows 10 10.0 (amd64)

Java Version *

Java Vendor: Oracle Corporation Java Version: 17.0.9

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 Bug Severity: High Issues described as high severity as per the new issue form labels Jan 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Severity: High Issues described as high severity as per the new issue form
Projects
None yet
Development

No branches or pull requests

2 participants