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

Deathsave console bug #2067

Open
5 tasks
tanyxp opened this issue Jan 3, 2022 · 0 comments
Open
5 tasks

Deathsave console bug #2067

tanyxp opened this issue Jan 3, 2022 · 0 comments
Assignees

Comments

@tanyxp
Copy link
Member

tanyxp commented Jan 3, 2022

Module(s) Effected

Player Tools - Deathsaves

Expected (Proposed) Behavior

No console error thrown from deathsaves code.

Actual Behavior

When a player loses all their HP (0 or below), this error will be thrown on the browser console:

deathsave.js?71a3:74 
Uncaught (in promise) TypeError: this.noMaxHpLeft is not a function
    at StatsDeathSaveViewModel._callee8$ (deathsave.js?71a3:74)
    at tryCatch (runtime.js?c1c3:62)
    at Generator.invoke [as _invoke] (runtime.js?c1c3:296)
    at Generator.prototype.<computed> [as next] (runtime.js?c1c3:114)
    at step (deathsave.js?71a3:11)
    at eval (deathsave.js?71a3:11)
    at new Promise (<anonymous>)
    at StatsDeathSaveViewModel.eval (deathsave.js?71a3:11)
    at StatsDeathSaveViewModel.noMaxHpDeath (deathsave.js?71a3:83)
    at Function.notifySubscribers (knockout-latest.js?43ec:38)

Steps to reproduce (if any)

  • Open console log
  • Select Player character
  • Take enough damage to fall to 0 or below HP
  • Look at console log

Tasks to complete (if multiple)

  • Fix error causing error
@Sonictherocketman Sonictherocketman self-assigned this Jan 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants