-
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
Advancement Type: Subclass #1407
Comments
Originally in GitLab by @playest What would you think if any feature could have a "trigger" when a certain level is reached in a certain class?
Which would give us the ability to have a tree of features that are giving other features to fill the character sheet with all the right value. Obviously we would need a UI for all of that. |
That is basically what the new advancement system is. |
… class to which it was added
… class to which it was added
Introduces a new subclass advancement! This advancement doesn't do anything on its own other than indicate the level at which the class takes a subclass due to limitations in the advancement system. When a player reaches the level of the subclass advancement, their features tab adds a "Add Subclass" button where the subclass icon will eventually appear. Clicking this opens the compendium browser with the subclass list locked to the current class's identifier. While this doesn't fully implement what was originally desired from the subclass advancement, this workflow should work pretty well to fill in a major gap in the system's level-up workflow. Closes #1017 Closes #1407
[#1407] Add Subclass advancement & selection interface on sheet
This advancement allows the player to select their subclass at a certain level. This can only be added to
"class"
items and each class can only have a single advancement of this type. Much of this advancement would be the same as the Item Choice advancement (#1401) and could probably be an extension of that one.This would resolve #1017.
Level Up Interface
The player would be presented with a list of available subclasses as well as have a drop area for adding an unlisted subclass. They can choose a single subclass before continuing.
The advancement would ensure that any item added is of a new
subclass
type created by #1080.Configuration
This configuration object would contain a
pool
of item UUIDs and an option to disable the drop area.Value
The value object would contain the origin UUID of the subclass added and the ID of the object added to the actor.
Future Directions
If a system for scanning compendiums for items of specific types is implemented, this could be used to automatically build a list of available subclasses that would be presented to the player.
The text was updated successfully, but these errors were encountered: