-
Notifications
You must be signed in to change notification settings - Fork 232
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
Centralize trait configuration #1885
Comments
arbron
added a commit
to arbron/dnd5e
that referenced
this issue
Oct 21, 2022
arbron
added a commit
to arbron/dnd5e
that referenced
this issue
Oct 21, 2022
…eTraitSelector into single app
arbron
added a commit
to arbron/dnd5e
that referenced
this issue
Oct 21, 2022
…eTraitSelector into single app
arbron
added a commit
to arbron/dnd5e
that referenced
this issue
Dec 21, 2022
arbron
added a commit
to arbron/dnd5e
that referenced
this issue
Dec 21, 2022
…eTraitSelector into single app
arbron
added a commit
to arbron/dnd5e
that referenced
this issue
Dec 29, 2022
arbron
added a commit
to arbron/dnd5e
that referenced
this issue
Dec 29, 2022
…eTraitSelector into single app
arbron
added a commit
to arbron/dnd5e
that referenced
this issue
Jan 2, 2023
arbron
added a commit
to arbron/dnd5e
that referenced
this issue
Jan 2, 2023
…eTraitSelector into single app
arbron
added a commit
to arbron/dnd5e
that referenced
this issue
Jan 2, 2023
arbron
added a commit
to arbron/dnd5e
that referenced
this issue
Jan 2, 2023
arbron
added a commit
to arbron/dnd5e
that referenced
this issue
Jan 2, 2023
…eTraitSelector into single app
arbron
added a commit
to arbron/dnd5e
that referenced
this issue
Jan 2, 2023
arbron
added a commit
to arbron/dnd5e
that referenced
this issue
Jan 2, 2023
Fyorl
pushed a commit
that referenced
this issue
Jan 2, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently there is a bunch of logic for handling actor traits (weapon/armor/tool proficiencies, damage resistances, languages, etc.) that is spread throughout the code (some in
ProficiencySelector
, some in the actor document, some in the actor sheet application, some in templates) which makes it hard to reason about or modify the behavior of any individual trait. Centralizing this information in a config object would be great and a major boon for implementing #1405.There should also be a merging of
TraitSelector
,ProficiencySelector
, andDamageTraitSelector
into a single application that is able to use this trait configuration data itself rather than requiring the choices list to be defined on the actor sheet.The text was updated successfully, but these errors were encountered: