You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One of the compatibility issues that comes along with various mods is that they still need to be aware of each other for different aspects. This is very much highlighted with Warlock Subclasses each having their own spell lists, so a mod that might add a new 'base' spell needs to consider all the other mods out there. This made me wonder if we could potentially use introduce something like this mock up.
(Excuse the rough mock up, but an idea came to me so I thought I'd quickly mock it out before I lost it.)
The idea being the subclass section would do the following:
Use the ClassDescription UUID to add the subclass to the BaseClass like normal.
Insert the SpellList entries into "BaseClass"."SubclassHandle".Spells."One/Two/Etc"
Follow the same with Features.
Insert the Levels entries into "BaseClass"."SubclassHandle".Levels."One/Two/Etc"
We could then also add a new Dictionary array under each class called All as a way of holding multiple UUIDs, which is formed from every subclass.
The list section is just a quick mock-up referencing dictionaries, with the idea being the Selectors/Lists/Boosts/Bools/etc would not be run until after the Dictionaries had finished.
I'm not sure of any of the feasibility due to my lack of experience in this particular language, but I'm hopeful my general programming transferable knowledge is at least pointing in the right direction.
The text was updated successfully, but these errors were encountered:
One of the compatibility issues that comes along with various mods is that they still need to be aware of each other for different aspects. This is very much highlighted with Warlock Subclasses each having their own spell lists, so a mod that might add a new 'base' spell needs to consider all the other mods out there. This made me wonder if we could potentially use introduce something like this mock up.
(Excuse the rough mock up, but an idea came to me so I thought I'd quickly mock it out before I lost it.)
The idea being the
subclass
section would do the following:ClassDescription
UUID to add the subclass to theBaseClass
like normal.SpellList
entries into"BaseClass"."SubclassHandle".Spells."One/Two/Etc"
Features
.Levels
entries into"BaseClass"."SubclassHandle".Levels."One/Two/Etc"
We could then also add a new Dictionary array under each class called
All
as a way of holding multiple UUIDs, which is formed from every subclass.The
list
section is just a quick mock-up referencing dictionaries, with the idea being the Selectors/Lists/Boosts/Bools/etc would not be run until after the Dictionaries had finished.I'm not sure of any of the feasibility due to my lack of experience in this particular language, but I'm hopeful my general programming transferable knowledge is at least pointing in the right direction.
The text was updated successfully, but these errors were encountered: