You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Print-out for a mech sheet using the Mourning Cloak chassis doesn't include details for the "Blinkspace Jump" full action. It includes details of the Passive which grants that action, but not the action itself.
To Reproduce
Steps to reproduce the behavior:
Go to a character with a mech in the hangar using the Mourning Cloak chassis
Click on "Pilot Options", then "Print", select the Mourning Cloak mech under "Include Mech", then "Print"
Scroll down to the mech details on the sheet
See "BLINKSPACE JUMP (PASSIVE)" under the Core System heading, which does not include details of the full action granted.
Expected behavior
Details of the Full Action granted should be present on the print-out.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
OS: MacOS Sonoma 14.6.1
Browser: Chrome
Version: Chrome 128.0.6613.120
Smartphone (please complete the following information):
Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]
Additional context
Thanks for the amazing tool! This isn't a big problem for our group, but I thought it would be worth flagging.
The text was updated successfully, but these errors were encountered:
Describe the bug
Print-out for a mech sheet using the Mourning Cloak chassis doesn't include details for the "Blinkspace Jump" full action. It includes details of the Passive which grants that action, but not the action itself.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Details of the Full Action granted should be present on the print-out.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
Thanks for the amazing tool! This isn't a big problem for our group, but I thought it would be worth flagging.
The text was updated successfully, but these errors were encountered: