https://github.com/matthewoden/treat-wounds

pf2e treat wounds tracker. Quickly handles aid and treat wounds checks.
https://github.com/matthewoden/treat-wounds

Last synced: about 1 month ago
JSON representation

pf2e treat wounds tracker. Quickly handles aid and treat wounds checks.

• Host: GitHub
• URL: https://github.com/matthewoden/treat-wounds
• Owner: matthewoden
• Created: 2024-06-02T20:13:27.000Z (7 months ago)
• Default Branch: main
• Last Pushed: 2024-06-10T03:53:58.000Z (7 months ago)
• Last Synced: 2024-06-10T04:43:44.280Z (7 months ago)
• Language: TypeScript
• Homepage: https://treatwounds.netlify.app
• Size: 74.2 KB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# Treat Wounds

Try it out at: https://treatwounds.netlify.app

A quick and dirty solution for Treat Wounds taking a lot of table-time in PF2E.

Supports:

- Various sources of bonuses have a static bonus field

- Rolling aid checks for another party member, and calculate that into their bonus

  - Aid checks can treat failure as a success in settings.

- Feat: Risky Surgery - success as a critical success, a bonus to your medicine roll, and damage is listed seperately, so you can see amount healed, harmed, and the net.

- Feat: Magic hands - roll d10s instead of d8s.

- Feat: Mortal Heaing - treat success as a critical success.

- Dedication: Medic - additional healing when you treat wounds based on your target dc

- A log out outputs, to help you track healing over time.

- local persistence via browser storage. (cross-device storage not supported)

These were the features that were needed to support my goal for this experience (outlined below)

## Goals

Most of the time, treat wounds is the exact same procedure, over and over and the values are relatively static (making the process a bit tedious).

The experience for the UI should basically allow a player to configure how they treat wounds once, and then click "roll" as

many times as needed, and see all they need to tell the other player. If the other player has their own perks and quirks around treat wounds, that's their responsibility to manage.

## Contributing

Contributions are welcome -- I'm a dad, so I don't have a ton of free time to review changes. I won't be offended if you fork and deploy your own version.

## Not planned for support:

- any feats/abilities that are other-player-oriented. For example, if the rules say "when someone treats your wounds"? Then that player can manage their one-off bonuses.

   - Supporting these will add options will only add clutter to the UI, and add a new kind of tedium as players select the right options per player from roll to roll. (We'd need to store per-player settings or something. Out of scope for now.)

- transposable compliance/right hand blood. I could be convinced otherwise, but I'd need to know the use case where you frequently choose to hurt yourself.