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] In low gravity a PSR is indicated but not actually rolled if a unit uses more than normal MP to flee the board #6482

Open
4 tasks done
GiovanniBertuccio opened this issue Feb 1, 2025 · 0 comments

Comments

@GiovanniBertuccio
Copy link

Brief Description *

A unit that uses more MP than normally allowed to flee the board is not required to roll the PSR for internal damage normally required for doing that. This happens with sprinting on or off.

I believe the happens because RAW TO page 55 (one-book version) the unit makes the PSR at the end of the movement phase and I suspect in MM it no longer exists. TO page 55: "If a unit spends more MP than its normal Running (or Flanking) MP during a turn (as in the example above of the unit moving on a world with .75 G), the player must make a Piloting Skill Roll at the end of the phase in which the Running MP was exceeded".

This doesn't matter for pick-up games, but for campaign games it creates a zero-risk way to flee the board using extra MP, and the PSR and damage should probably be incurred even though the unit has fled.

3. Steps to Reproduce

In the attached saved move the Assassin to the edge of the board and note the indicators that a PSR will be required in the movement highlights and the button to finish movement.
Select Flee.
Confirm fleeing.
No PSR will be rolled even though one was indicated.

Attach Files

flee_with_no_psr_example.sav.gz

Severity *

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

MegaMek Suite Version *

v0.50.03-SNAPSHOT Build Date: 2025-01-14T03:17:55.982487281

Operating System *

Windows 10

Java Version *

Java Vendor: Eclipse Adoptium Java Version: 17.0.13

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