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

[BUG] NPC overheating doesn't act as intended #486

Closed
Argonius-Angelus opened this issue Nov 29, 2022 · 0 comments
Closed

[BUG] NPC overheating doesn't act as intended #486

Argonius-Angelus opened this issue Nov 29, 2022 · 0 comments
Labels
automation Involves built-in automation bug Something isn't working

Comments

@Argonius-Angelus
Copy link

Argonius-Angelus commented Nov 29, 2022

Describe the bug
I was recommended by Eranziel to post this here. When invoking the stress function for 1 Stress NPCs, it correctly marks the result as the NPC becoming exposed. However, it still decrements the Stress value to 0 and marks the result as "Irreversible Meltdown", even if the description says that the NPC is Exposed.

To Reproduce

  1. Use Triggler or some other automation for Stress rolling (the built-in request for stress rolls also works).
  2. Overheat any NPC with only 1 Stress.
  3. Watch as the chat output says "0/1 Stress: Irreversible Meltdown" followed by "Your mech is EXPOSED".

Expected behavior
It should not decrement the Stress of a 1 Stress NPC, and also not state it is an "Irreversible Meltdown".

Screenshots
image

Platform (please complete the following information):

  • OS: Windows 11
  • Standalone Foundry app
  • Foundry version v9.269
  • Lancer system version 1.2.0

Additional context
Add any other context about the problem here.

Discord contact info
If you are willing to answer questions regarding this bug report on Discord, or if you want to be notified when it is fixed, please leave your Discord ID here.
[REDACTED]#0001

@Argonius-Angelus Argonius-Angelus added bug Something isn't working triage To be assessed by maintainer labels Nov 29, 2022
@Eranziel Eranziel added automation Involves built-in automation and removed triage To be assessed by maintainer labels Dec 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automation Involves built-in automation bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants