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
Right now, identically named skills cannot be unambiguously referred to. Add a 'Parent Skill/Child Skill' optional syntax to avoid this. This will allow for items that give bonuses to "Riding/Horse" as distinct from "Animal Handling/Horse".
The text was updated successfully, but these errors were encountered:
So, it exists now as part of the CulturePrototype class, but not as anything more general. Musings on how it should handle things. Maybe wildcards should be allowed, or maybe not. I would tend toward not, since it could add complications without any clear benefit.
For example, would "Riding/" mean "Give a bonus to every skill until the riding class", or "Give a bonus to the first skill under the riding class"? The first is the more natural interpretation, but could be handled by giving a bonus directly to the "Riding" category. In addition, when saving, the bonus would need to be remembered as "Riding/" instead of as a bonus to a set of skills, since otherwise new skills wouldn't receive the bonus. In addition, new skills would need to be checked for matching of previously matched wildcards.
If/when it is made more general, only CulturePrototypes will be allowed to use wildcards or $PREV.
Right now, identically named skills cannot be unambiguously referred to. Add a 'Parent Skill/Child Skill' optional syntax to avoid this. This will allow for items that give bonuses to "Riding/Horse" as distinct from "Animal Handling/Horse".
The text was updated successfully, but these errors were encountered: