I think it would be useful to have a limited use editor for any given feature of a homebrew subclass, especially one that offers multiple actions or options. The actions or options all need to count as a use of the same feature.
The best example of a kind of feature that works in this way is Channel Divinity, but it would be useful for many other homebrews for any class or subclass.
As it stands, you can only set limited use for one action within a feature, rather than for any use of any action/ability that is granted as part of a subclass feature.
So, say that a Feature only allows 2 uses per rest, but there are 3 potential actions: Action A, B and C. Currently, the only way to limit uses is to individually limit the uses of Action A, B and C to only 2 uses. But if you did that, they'd each show up as having 2 uses each, so you'd have 6 uses of a Feature that's only supposed to be used twice per rest.
My work around for this, in terms of keeping track, is to list the whole Feature as an action alongside the others, and set limited use only for that one "action." But it's kind of confusing to anyone looking at the character sheet who isn't aware of this specific workaround and its purpose. And that kind of problem interferes with one of the best things about D&D Beyond, which is the ability to quickly share character sheets between players/DMs, and/or edit, share and collaborate on homebrew creations.
For some insight into the kind of homebrews that need this most; I’m making a Theurgy wizard subclass with its own homebrew domain. The nature of this UA subclass in general demands homebrewery, which is fun, but I’m running into this problem with building Channel Divinity from scratch. I imagine that other homebrewers would similarly benefit from the ability to limit the uses of a feature and its actions as whole.
I agree. The workaround I have been using is to make one action for the number of uses, and to make Options for A, B, and C as part of the same subclass feature and have them all “granted.” Then I attach the additional actions for the things themselves to the options. At least that way a, b, and c stay individual on the sheet, but everything gets attached to the action with the number of uses because they are all part of the same feature. It’s not the most intuitive thing in the world, and it’s not perfect, but it does work.
I think it would be useful to have a limited use editor for any given feature of a homebrew subclass, especially one that offers multiple actions or options. The actions or options all need to count as a use of the same feature.
The best example of a kind of feature that works in this way is Channel Divinity, but it would be useful for many other homebrews for any class or subclass.
As it stands, you can only set limited use for one action within a feature, rather than for any use of any action/ability that is granted as part of a subclass feature.
So, say that a Feature only allows 2 uses per rest, but there are 3 potential actions: Action A, B and C. Currently, the only way to limit uses is to individually limit the uses of Action A, B and C to only 2 uses. But if you did that, they'd each show up as having 2 uses each, so you'd have 6 uses of a Feature that's only supposed to be used twice per rest.
My work around for this, in terms of keeping track, is to list the whole Feature as an action alongside the others, and set limited use only for that one "action." But it's kind of confusing to anyone looking at the character sheet who isn't aware of this specific workaround and its purpose. And that kind of problem interferes with one of the best things about D&D Beyond, which is the ability to quickly share character sheets between players/DMs, and/or edit, share and collaborate on homebrew creations.
For some insight into the kind of homebrews that need this most; I’m making a Theurgy wizard subclass with its own homebrew domain. The nature of this UA subclass in general demands homebrewery, which is fun, but I’m running into this problem with building Channel Divinity from scratch. I imagine that other homebrewers would similarly benefit from the ability to limit the uses of a feature and its actions as whole.
Yeah, there are some official features and items that need this too, so I'm sure it is on their to-do list.
I agree. The workaround I have been using is to make one action for the number of uses, and to make Options for A, B, and C as part of the same subclass feature and have them all “granted.” Then I attach the additional actions for the things themselves to the options. At least that way a, b, and c stay individual on the sheet, but everything gets attached to the action with the number of uses because they are all part of the same feature. It’s not the most intuitive thing in the world, and it’s not perfect, but it does work.
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting