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

Missing option to Avoid subclass at level where not applicable [£25] #107

Open
4 tasks
Zarhog opened this issue Sep 28, 2024 · 4 comments
Open
4 tasks
Assignees
Labels
enhancement New feature or request seeking funding

Comments

@Zarhog
Copy link

Zarhog commented Sep 28, 2024

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

  1. Main AS: Find available subclasses for the main class, get advancements for all those by level, get min level with advancement
  2. If min-level of Subclass advancements = 1: the subclass select should be required
  3. If min-level of Subclass advancements > 1: the subclass select should be optional
  4. LevelUp plugin: if all have same min-level and that level matches the new level for this class, make it required.
@geoidesic geoidesic added enhancement New feature or request seeking funding labels Sep 28, 2024
@geoidesic
Copy link
Owner

geoidesic commented Sep 28, 2024

or at the very least Don't make subclass selection mandatory....

  1. This is easy to do. I wouldn't even charge for this, but what about people who want to be able to select it? Bear in mind that the level up feature does not provide the ability to select a subclass for an existing class, so then how would the subclass get selected?

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

  1. This is a bad idea because once again what we're trying to do is fix the dnd5e system, which will then make Actor Studio fragile. It's also a lot of work to do this probably [£100]. E.g. we know that 5e 2024 edition will make all subclass selections for all classes be at level 3.

  2. What is the problem with selecting it at level 1?

@geoidesic
Copy link
Owner

geoidesic commented Sep 28, 2024

this usualy happens at eather level 1,2,3 or 4

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

@Zarhog
Copy link
Author

Zarhog commented Oct 2, 2024

Cleric "Divi9ne Domain" 1st Lv
Sorcerer "Sorcerous Origin" 1st Lv

Druid "Druid Circle" 2nd Lv
Wizard "Arcane Tradition" 2nd Lv

barbarian "Primal Path" 3rd Lv
bard "Bard Collage" 3rd Lv
Fighter "Matrial Archetype" 3rd Lv
Monk "Monastic Tradition " 3rd Lv
Paladin "Sacred Oath" 3rd Lv
Rogue "Roguish Archetype" 3rd Lv
Gunglinger (Hevey arms) "gun slinger Trial" 3rd Lv

all are 2018 Rules Pre 2024 (because everyone considers 2024 to be 6e not 5e)
This is why i suggestted a list. but also the subclass need to be skipable untill it is aproporiate for that class.

(im also going to open a ticket, to request the seperation of class and subclass into seperate tabs)

@geoidesic
Copy link
Owner

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.

@geoidesic geoidesic changed the title Missing option to Avoid subclass at level where not aplicable. Missing option to Avoid subclass at level where not applicable [£30] Oct 3, 2024
@geoidesic geoidesic changed the title Missing option to Avoid subclass at level where not applicable [£30] Missing option to Avoid subclass at level where not applicable [£25] Oct 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request seeking funding
Projects
None yet
Development

No branches or pull requests

2 participants