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

[Issue] Pilot Hit Failed Roll causing auto crash? #6435

Open
4 tasks done
RaozSpaz opened this issue Jan 24, 2025 · 0 comments
Open
4 tasks done

[Issue] Pilot Hit Failed Roll causing auto crash? #6435

RaozSpaz opened this issue Jan 24, 2025 · 0 comments

Comments

@RaozSpaz
Copy link

Brief Description *

Image

Image

Image

The whole series of events of this situation played out REALLY weird.
The pilot was hit [as shown in the second image] but the roll was done up at the top and somehow led to an automatic crash.
Which then down at the bottom where the hit actually happened it doesn't even show the roll or the relative info. And when the VTOL drops altitude, its already registered as on the ground because it apparently crashed?
As I said there is a lot going on here but Ill just get into what is wrong.

As per PG 197 of the TW whenever a Pilot of a VTOL is hit they must make a piloting roll [much like the one shown in the images] or drop one elevation [as shown in the second image].
What is wrong though is that this somehow caused the VTOL to crash, despite being at Elevation 5 prior to the attack and the terrain beneath it being Level 0 [as shown in the third image].
Although the drop in elevation can lead to a crash, the VTOL was nowhere near close enough to the ground to have been able to crash into it from the failed piloting roll.

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 *

50.03 Nightly

Operating System *

Windows 10

Java Version *

17.0.12

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
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant