Trying to make a subclass ability have a number of charges equal to half your proficiency bonus (1 from levels 1-8, 2 from 9-16 and 3 from 17-20). Would anyone know how I can script this?
That reason doesn't really hold much water when you're talking about a feature specifically designed to create features and systems that are explicitly not official. Oh well.
But the system is not specifically designed to create things that are not official. What you think of as ”the homebrewer,” is really just the system the Devs created for themselves to implement the official content, they just let us use a limited version of it. It isn’t programmed to do anything the Devs don’t need it to do. Heck, it isn’t even programmed to do everything the Devs need it to do either.
Regardless of if the official content uses the same mechanism to help generate the official content published by Wizards, it's marketed, presented and used by the community as a homebrew content generation tool.
I'm not saying that they should have thought of this by now, or that the feature should already exist, but that there's no functional reason to actually restrict it to reflect only official content mechanisms and metric calculations. This feature could be implemented, and if it had enough support, saying "well it's not official" as the only reason they wouldn't implement it sounds ludicrous when discussing a system the community uses to generate unofficial content.
Like I said "Oh well". It's unlikely to get that level of support for this feature and that's the actual reason it won't be implemented, which is fair, no doubt they have enough to think about with One D&D! It's just such a shame because a simple change to the multiplication input validation (and perhaps the persistence layer if it doesn't support floating point) would solve the problem.
Trying to make a subclass ability have a number of charges equal to half your proficiency bonus (1 from levels 1-8, 2 from 9-16 and 3 from 17-20). Would anyone know how I can script this?
You cannot. The closes you can get is an Action which grants the correct number of limited uses at the correct levels and hope they don’t multiclass.
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting
This is very frustrating. Simply adding support for 0.5 uses in conjunction with proficiency multiplication would solve this issue easily...
2022 and this is still an issue.
Since nothing official uses half proficiency as a metric, DDB won’t implement it.
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting
That reason doesn't really hold much water when you're talking about a feature specifically designed to create features and systems that are explicitly not official. Oh well.
But the system is not specifically designed to create things that are not official. What you think of as ”the homebrewer,” is really just the system the Devs created for themselves to implement the official content, they just let us use a limited version of it. It isn’t programmed to do anything the Devs don’t need it to do. Heck, it isn’t even programmed to do everything the Devs need it to do either.
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting
Regardless of if the official content uses the same mechanism to help generate the official content published by Wizards, it's marketed, presented and used by the community as a homebrew content generation tool.
I'm not saying that they should have thought of this by now, or that the feature should already exist, but that there's no functional reason to actually restrict it to reflect only official content mechanisms and metric calculations. This feature could be implemented, and if it had enough support, saying "well it's not official" as the only reason they wouldn't implement it sounds ludicrous when discussing a system the community uses to generate unofficial content.
Like I said "Oh well". It's unlikely to get that level of support for this feature and that's the actual reason it won't be implemented, which is fair, no doubt they have enough to think about with One D&D! It's just such a shame because a simple change to the multiplication input validation (and perhaps the persistence layer if it doesn't support floating point) would solve the problem.
Oh, don’t get me wrong, I would absolutely love it if they added this. I was just explaining why they don’t do it.
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting