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

Add 'proficiency' property to subclass object #258

Open
Freedzio opened this issue Sep 13, 2020 · 4 comments
Open

Add 'proficiency' property to subclass object #258

Freedzio opened this issue Sep 13, 2020 · 4 comments

Comments

@Freedzio
Copy link
Contributor

So

When you choose life domain for cleric, you get proficiency with heavy armor, but it is not specified in data itself, you just get a feature called "bonus proficiency", which itself is not too descriptive.

My suggestion is, maybe add proficiencies property to domain object? And add such property to aby subclass giving you proficiencies?

@Freedzio Freedzio changed the title Add 'proficiency' property to cleric life subdomain Add 'proficiency' property to subclass object Sep 13, 2020
@fergcb
Copy link
Member

fergcb commented Sep 13, 2020

A better solution imo would be to expand on the "Bonus Proficiency" feature, rather than the subclass itself. According to the SRD, the feature is what grants the proficiency, not the subclass.

Features in general could definitely do with being expanded to make them more computer friendly - e.g. using APIReferences, Choice structures, and so on.

@Freedzio
Copy link
Contributor Author

hmm, so proficiency property on feature object? This way, the data comes from feature, bot the subclass.

Also, I agree on the idea of expanding the features. For example, it would be nice if features like "Divine Domain' or "Bard College" had some list property to choose from (despite the fact there is only one subclass choice for every class). Sometimes, to get to actual data related to a feature is tricky

@fergcb
Copy link
Member

fergcb commented Sep 14, 2020

hmm, so proficiency property on feature object? This way, the data comes from feature, bot (sic) the subclass.

Yes, exactly this! It would be better representative of the SRD content, and just meshes better with the semantics of the API data's structure as a result.

@bagelbits
Copy link
Collaborator

This is similar to #187 as well.

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

No branches or pull requests

3 participants