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

Advancement Type: Hit Points #1402

Closed
arbron opened this issue Jan 15, 2022 · 2 comments
Closed

Advancement Type: Hit Points #1402

arbron opened this issue Jan 15, 2022 · 2 comments

Comments

@arbron
Copy link
Collaborator

arbron commented Jan 15, 2022

A Hit Points advancement type would keep track of hit point choices for each level of a class. This advancement can only be added to "class" items and each class can only have a single advancement of this type.

This advancement would be a major step towards #406 and would replicated the functionality of !144.

Level Up Interface

When a player levels up they should be presented with the option to either roll a hit dice or take the average value.

Configuration

No configuration is required for this type. The hit dice can be taken directly from the existing class data.

Value

The value object would contain keys for each level that the player has gained in this class. The values would either be the value rolled on the die (Constitution modifier would not be included), "avg" indicating that the average value was taken, or "max" indicating that the maximum die value was used. This "max" value should be reserved for the first level of the original class.

{
  1: "max",
  2: 3,
  3: 5,
  4: 2
}

Future Directions

Potential configuration options could be provided to give an additional bonus to HP for each level of the class.

@arbron
Copy link
Collaborator Author

arbron commented Feb 25, 2022

Originally in GitLab by @iaguastalli

using true for both first level maximum and average sounds a little confusing, would it make sense to use a constant there e.g MAX and AVG ?

@arbron
Copy link
Collaborator Author

arbron commented Mar 30, 2022

Resolved with !498

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

1 participant