Reply to thread

Message

<blockquote data-quote="TwoSix" data-source="post: 8365395" data-attributes="member: 205">Yea, but that's not really true that they have NO idea how it will expand.&nbsp; You know anything in a distinct list should be assumed to modifiable and extensible.&nbsp; Classes, subclasses, races, backgrounds, weapons, armor, equipment, magic items, spells, spells known, spells prepared, spell slots, tools, skills, languages, feats, class features, abilities.Any calculations should be done from derived values instead of fixed values.&nbsp; That's a little more difficult, of course, as you might need to sweep in new values from new kinds of sources.&nbsp; But there are a finite amount of calculations that need to be made on the character sheet, so that's doable.Almost certainly the hardest case to prepare for is if they added a new method of acquiring spells and spell progression, or just a new layer of effects in general (like if the added a new class of martial maneuvers to all martial classes).&nbsp; That's a whole extra layer, and would probably be a pain in the butt.I mean, probably the biggest technical challenges they've had from new material is Tasha's class variants, since they had to turn those from a fixed value into a selection.&nbsp; But that goes back to designing those features to be toggleable to being with.&nbsp; Every class feature in a class should have been designed to be like an ASI, where you can select from an option menu.Something like the Strixhaven subclasses I probably would have facepalmed at a little, since they break the general one-to-many assumption I would have had about the class-subclass relationship.&nbsp; But even that's not impossible to fix, since you can simply enter a new subclass for each class-subclass combination.&nbsp; (Lorehold-Bard and Lorehold-Wizard are different entries.)&nbsp; The tricky part would actually be coding that a Lorehold-Bard couldn't multiclass into a Lorehold-Wizard, so I don't think there's been any previous restrictions on subclass combinations while multiclassing.&nbsp; That would be a legitimate &quot;come on, now&quot; moment if I was developing that.&nbsp; That's new tables and a lot of new logic in the front end.</blockquote>

[QUOTE="TwoSix, post: 8365395, member: 205"] Yea, but that's not really true that they have NO idea how it will expand. You know anything in a distinct list should be assumed to modifiable and extensible. Classes, subclasses, races, backgrounds, weapons, armor, equipment, magic items, spells, spells known, spells prepared, spell slots, tools, skills, languages, feats, class features, abilities. Any calculations should be done from derived values instead of fixed values. That's a little more difficult, of course, as you might need to sweep in new values from new kinds of sources. But there are a finite amount of calculations that need to be made on the character sheet, so that's doable. Almost certainly the hardest case to prepare for is if they added a new method of acquiring spells and spell progression, or just a new layer of effects in general (like if the added a new class of martial maneuvers to all martial classes). That's a whole extra layer, and would probably be a pain in the butt. I mean, probably the biggest technical challenges they've had from new material is Tasha's class variants, since they had to turn those from a fixed value into a selection. But that goes back to designing those features to be toggleable to being with. Every class feature in a class should have been designed to be like an ASI, where you can select from an option menu. Something like the Strixhaven subclasses I probably would have facepalmed at a little, since they break the general one-to-many assumption I would have had about the class-subclass relationship. But even that's not impossible to fix, since you can simply enter a new subclass for each class-subclass combination. (Lorehold-Bard and Lorehold-Wizard are different entries.) The tricky part would actually be coding that a Lorehold-Bard couldn't multiclass into a Lorehold-Wizard, so I don't think there's been any previous restrictions on subclass combinations while multiclassing. That would be a legitimate "come on, now" moment if I was developing that. That's new tables and a lot of new logic in the front end. [/QUOTE]

Verification