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

Formal API for damage dealt by moves #55

Open
Auroratide opened this issue Jan 30, 2023 · 1 comment
Open

Formal API for damage dealt by moves #55

Auroratide opened this issue Jan 30, 2023 · 1 comment
Labels
moves the moves section

Comments

@Auroratide
Copy link
Owner

Right now, move damage is baked into the text of moves. It would be nice if move damage were incorporated into the api structure, as this would allow the trainer section to automatically show the damage to do and automatically apply STAB.

Questions:

  • What if damage is not monotype?
  • What if damage is modified by some other condition?
@Auroratide Auroratide added the moves the moves section label Jan 30, 2023
@Auroratide
Copy link
Owner Author

It's possible this api could be better generalized to account for saves and other effects.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
moves the moves section
Projects
None yet
Development

No branches or pull requests

1 participant