-
-
Notifications
You must be signed in to change notification settings - Fork 4
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
Missing option to Avoid subclass at level where not applicable [£25] #107
Comments
|
Can you provide SRD examples of subclasses that are selected at each of those levels? I want to check if every subclass has an advancement that occurs at the level at which it is chosen. If that is the case, then we can simply look for the lowest level advancement and make the subclass selectable in the Level Up plugin (at the appropriate level) for those that have it after level 1 |
Cleric "Divi9ne Domain" 1st Lv Druid "Druid Circle" 2nd Lv barbarian "Primal Path" 3rd Lv all are 2018 Rules Pre 2024 (because everyone considers 2024 to be 6e not 5e) (im also going to open a ticket, to request the seperation of class and subclass into seperate tabs) |
Thanks. I've inspected those. All of them conform to the rule that there is an advancement (ItemGrant) at the level at which they should be selected. So my logic stands. I've edited the OP with requirements as I understand them now. |
Also we are still missing an option to skip Subclass selections, Since some classes don't choose there Subclass till later.
or at the very least Don't make subclass selection mandatory....
this could be solved with a manual list in settings that allows us to match classes into lists of when they get subclasses as this usualy happens at eather level 1,2,3 or 4
The text was updated successfully, but these errors were encountered: