You know how racial traits have the additional “Hide on Details Page” checkbox? Image all the things that might be super useful for on subclass features too; and not just theoretically, but practically. To be clear, this isn’t a “please add this to the homebrewer” requests. This is a “I had an idea to make implementing various things from WotC in a way both as practical and RAW as snippets are” suggestion.
Having one version of a trait for form and another for function, or using shadow traits as a workaround to options, etc., must be useful or you wouldn’t have implemented it. Right? Subclass features could also benefit from this checkbox. As one example, you could finally fix Mage Hand Legerdemain to automatically grant the right spell, and add the Legerdemain description to the spell as a Cherry on top. Have the displayed version of Spellcasting for the Arcane Trickster reflect the RAW difference in the table as compared to Eldritch Knight, but have the character sheet actually use the same table as the EK and just grant the Spell separately. And that’s just one example. Just add an nbsp to the feature name to have it not reference the version tied to the feature name. Right?
You already know how to do it, since you already did it with racial traits. So expanding it to subclass features would have to be simpler by comparison. Right? And it could solve soo—oo many problems. Right?
However, if not… if any of those “right?s” were really “wrongs,” could someone please spare a moment to explain why/how to me in relative layman’s terms. That would be appreciated.
Thank you for taking the time to read this suggestion, I hope it helps.
Heya there Dev type folks at DDB,
You know how racial traits have the additional “Hide on Details Page” checkbox? Image all the things that might be super useful for on subclass features too; and not just theoretically, but practically. To be clear, this isn’t a “please add this to the homebrewer” requests. This is a “I had an idea to make implementing various things from WotC in a way both as practical and RAW as snippets are” suggestion.
Having one version of a trait for form and another for function, or using shadow traits as a workaround to options, etc., must be useful or you wouldn’t have implemented it. Right? Subclass features could also benefit from this checkbox. As one example, you could finally fix Mage Hand Legerdemain to automatically grant the right spell, and add the Legerdemain description to the spell as a Cherry on top. Have the displayed version of Spellcasting for the Arcane Trickster reflect the RAW difference in the table as compared to Eldritch Knight, but have the character sheet actually use the same table as the EK and just grant the Spell separately. And that’s just one example. Just add an nbsp to the feature name to have it not reference the version tied to the feature name. Right?
You already know how to do it, since you already did it with racial traits. So expanding it to subclass features would have to be simpler by comparison. Right? And it could solve soo—oo many problems. Right?
However, if not… if any of those “right?s” were really “wrongs,” could someone please spare a moment to explain why/how to me in relative layman’s terms. That would be appreciated.
Thank you for taking the time to read this suggestion, I hope it helps.
Sincerely,
🦄
Sposta
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting