Item - Not a Magic Item - Please do not submit magical items that are not actually magical items. If your items are meant to replicate Blessings / Curses / Feats / Class features, you are welcome to use these privately, but they will not be allowed as published magical items.
This course of action will not lead DDB development team not far away... instead to greet for a missing feature workaround that would have been useful for thousands of players, You hide behind non-sense rules-of-thumb.
Then, what You obtained? I now resubmit the same items, calling them Barbarian Spirit (Lesser), Barbarian Spirit, Barbarian Spirit (Greater), using the Wondrous Item (Amulet) Group, and worked around the aforementioned rules.
TY for being able to demonstrate, again, your total absence of awareness of users needs.
Rollback Post to RevisionRollBack
Beyond the Woods (HB) - DM Curse of Strahd - DM Out of the Abyss - DM Tomb of Annihilation - DM Playing and Mastering D&D since 1984.
that would have been me that rejected your published homebrew.
Whilst the publishing of homebrew on D&D Beyond is (thankfully) not reliant on manual moderation of a queue any more, I regularly review recently published homebrew to ensure it meets rules that the automatic filters can't pick up.
In this case, we have a simple rule for magic items that they must actually be magical items - this is so that users browsing homebrew magical items don't find all sorts of things masquerading as magical items.
It was during such a review that I rejected your homebrew, as "Rage (9th to 15th level)" was clearly not the name of a magical item (there are various keywords I search on for review). I would also like to be clear that this was nothing to do with you posting on the forums about your homebrew.
I understand that you're creating these as a workaround for the character sheet not yet having the ability to toggle on/off features such as the Barbarian's rage and have them apply to attacks on the character sheet. This is a feature that is on the roadmap, but I fully understand the frustration with it not being available now.
It's unfortunate that the situation means that you believe that the D&D Beyond team demonstrate an absence of awareness of users needs - the development of D&D Beyond has been very much shaped by feedback from the community over what is important, moreover we're all DMs and players of the game ourselves, involved in D&D Beyond because we love D&D as a game.
Please can you let us know what you feel should be done better?
I understand You and most of the moderators and developers are gamers like me and all of us, but the evidence is before our eyes.
None of the critical requests, like "having a basic feature of a class be enabled in one click" has a clear and well-explained roadmap.
Roadmaps, in a development team, are not improvised, so a document containing the upcoming production listing and dates of release should be available to someone, at least for the development team that has to code that.
What I see is that basic and crucial features are not publicly prioritized to grant us a view of upcoming changes. For example, the lack of a working container flag of any kind to existing objects reveals a very low attitude to play, because everything should have been considered a container since its initial coded-object first draft.
Being a developer team leader myself, I see a lot of mistakes that have been made in the initial design of DDB, due primarily to poor understanding of game mechanics and existing tools features.
I don't know if it is Hasbro/WotC that's driving these choices, but I do hope that the team that codes releases of compendium contents and DDB features implementations are two distinct teams: otherwise, we will have to wait a century to see a decent character management sheet fully functional.
If the team is one and works concurrently on supplement transcoding and mechanics development, priority will never be given to the latter.
I see a lot of inexperience mistakes in developing tools for a community. The simple fact that the available for coding in snippet environment variables are less than ten {{proficiency | modifier:stat | savedc:stat | classlevel | etc...}}, and operators {{@min/max | #signed/unsigned | @roundup/down | etc...}} little more than five, says enough about none of them had ever developed anything others may customize.
Stop coding yourself...!!! Give us some serious tools to develop homebrew content and your developing times will halves in less than 6 months... the most of us gamers are nerds, at least one third being developers themselves. Let us participate in the process of creating a never-seen-before tool for Character Management, and stop postponing answers about upcoming releases.
Show us the roadmap. We do may contribute drive you in the correct direction. Style must come after substance. Give us a motivation to stay. I'm really starting to discourage in front of so many useless secrets and failures.
Notice: This post may appear excessively critic, but is intended to be a heavy stab in the neck of your DDB Head of Development. They must wake up and reroute. The stars are shining in front of them, but they mistook Marsfor Ursa Major.
Just my 2 cents.
Rollback Post to RevisionRollBack
Beyond the Woods (HB) - DM Curse of Strahd - DM Out of the Abyss - DM Tomb of Annihilation - DM Playing and Mastering D&D since 1984.
Hey, no need to apologise - BadEye has always said that the team want feedback and that means the bad as well as the good.
When it's thought through feedback that is well articulated, like your post, that's really valuable.
As a moderator, I am not part of the product team, but I do know that the people involved REALLY want to be able to get all these features into D&D Beyond.
Any further reply on the reasons why they have taken certain directions will need to come from staff, as again, I don't have that info - sorry I can't shed light on that.
Many thanks, Stormknight. I see you got the picture. There are so many little things to do and have to be prioritized before any other feature.
@BadEye: show us the roadmap.
Anyway, many thanks for the work done since then, but it isn't enough. We don't need another mobile app restyling... We need to stop manually adding things that are basically standard class features.
And, we definitely need everything could be a container (items, magic items, creatures). A flag to set it a container is enough, then a pop-up list in every object tooltip to chose from what has the flag is enough, together with an open field for weight contents multiplier (0 - Bag of Holding) and maximum weight the container can accommodate.
We need trade goods as well (trade bars, gems, jewelry, transportations), services (hirelings, sages, spell casting, temple healing, inns and taverns costs and lodging) and deity (at least the ones presented on PHB and supplements).
Start giving us some of those, and the route should be found again.
I shared right now three fake wondrous items that emulate the Barbarian Rage features if equipped.
There are three of them, one for each level range where it applies.
To find them, must pass a DC 15 Intelligence (Investigation) skill check, or simply look for a Homebrew Rage magic item (wondrous item type).
Feedback is welcome.
Beyond the Woods (HB) - DM
Curse of Strahd - DM
Out of the Abyss - DM
Tomb of Annihilation - DM
Playing and Mastering D&D since 1984.
This course of action will not lead DDB development team not far away... instead to greet for a missing feature workaround that would have been useful for thousands of players, You hide behind non-sense rules-of-thumb.
Then, what You obtained? I now resubmit the same items, calling them Barbarian Spirit (Lesser), Barbarian Spirit, Barbarian Spirit (Greater), using the Wondrous Item (Amulet) Group, and worked around the aforementioned rules.
TY for being able to demonstrate, again, your total absence of awareness of users needs.
Beyond the Woods (HB) - DM
Curse of Strahd - DM
Out of the Abyss - DM
Tomb of Annihilation - DM
Playing and Mastering D&D since 1984.
Hi there PaleMage,
that would have been me that rejected your published homebrew.
Whilst the publishing of homebrew on D&D Beyond is (thankfully) not reliant on manual moderation of a queue any more, I regularly review recently published homebrew to ensure it meets rules that the automatic filters can't pick up.
In this case, we have a simple rule for magic items that they must actually be magical items - this is so that users browsing homebrew magical items don't find all sorts of things masquerading as magical items.
It was during such a review that I rejected your homebrew, as "Rage (9th to 15th level)" was clearly not the name of a magical item (there are various keywords I search on for review). I would also like to be clear that this was nothing to do with you posting on the forums about your homebrew.
I understand that you're creating these as a workaround for the character sheet not yet having the ability to toggle on/off features such as the Barbarian's rage and have them apply to attacks on the character sheet. This is a feature that is on the roadmap, but I fully understand the frustration with it not being available now.
It's unfortunate that the situation means that you believe that the D&D Beyond team demonstrate an absence of awareness of users needs - the development of D&D Beyond has been very much shaped by feedback from the community over what is important, moreover we're all DMs and players of the game ourselves, involved in D&D Beyond because we love D&D as a game.
Please can you let us know what you feel should be done better?
Pun-loving nerd | Faith Elisabeth Lilley | She/Her/Hers | Profile art by Becca Golins
If you need help with homebrew, please post on the homebrew forums, where multiple staff and moderators can read your post and help you!
"We got this, no problem! I'll take the twenty on the left - you guys handle the one on the right!"🔊
Hi Stormknight.
I understand You and most of the moderators and developers are gamers like me and all of us, but the evidence is before our eyes.
None of the critical requests, like "having a basic feature of a class be enabled in one click" has a clear and well-explained roadmap.
Roadmaps, in a development team, are not improvised, so a document containing the upcoming production listing and dates of release should be available to someone, at least for the development team that has to code that.
What I see is that basic and crucial features are not publicly prioritized to grant us a view of upcoming changes. For example, the lack of a working container flag of any kind to existing objects reveals a very low attitude to play, because everything should have been considered a container since its initial coded-object first draft.
Being a developer team leader myself, I see a lot of mistakes that have been made in the initial design of DDB, due primarily to poor understanding of game mechanics and existing tools features.
I don't know if it is Hasbro/WotC that's driving these choices, but I do hope that the team that codes releases of compendium contents and DDB features implementations are two distinct teams: otherwise, we will have to wait a century to see a decent character management sheet fully functional.
If the team is one and works concurrently on supplement transcoding and mechanics development, priority will never be given to the latter.
I see a lot of inexperience mistakes in developing tools for a community. The simple fact that the available for coding in snippet environment variables are less than ten {{proficiency | modifier:stat | savedc:stat | classlevel | etc...}}, and operators {{@min/max | #signed/unsigned | @roundup/down | etc...}} little more than five, says enough about none of them had ever developed anything others may customize.
Stop coding yourself...!!! Give us some serious tools to develop homebrew content and your developing times will halves in less than 6 months... the most of us gamers are nerds, at least one third being developers themselves. Let us participate in the process of creating a never-seen-before tool for Character Management, and stop postponing answers about upcoming releases.
Show us the roadmap. We do may contribute drive you in the correct direction. Style must come after substance. Give us a motivation to stay. I'm really starting to discourage in front of so many useless secrets and failures.
Notice: This post may appear excessively critic, but is intended to be a heavy stab in the neck of your DDB Head of Development. They must wake up and reroute. The stars are shining in front of them, but they mistook Mars for Ursa Major.
Just my 2 cents.
Beyond the Woods (HB) - DM
Curse of Strahd - DM
Out of the Abyss - DM
Tomb of Annihilation - DM
Playing and Mastering D&D since 1984.
Hey, no need to apologise - BadEye has always said that the team want feedback and that means the bad as well as the good.
When it's thought through feedback that is well articulated, like your post, that's really valuable.
As a moderator, I am not part of the product team, but I do know that the people involved REALLY want to be able to get all these features into D&D Beyond.
Any further reply on the reasons why they have taken certain directions will need to come from staff, as again, I don't have that info - sorry I can't shed light on that.
Pun-loving nerd | Faith Elisabeth Lilley | She/Her/Hers | Profile art by Becca Golins
If you need help with homebrew, please post on the homebrew forums, where multiple staff and moderators can read your post and help you!
"We got this, no problem! I'll take the twenty on the left - you guys handle the one on the right!"🔊
Many thanks, Stormknight. I see you got the picture. There are so many little things to do and have to be prioritized before any other feature.
@BadEye: show us the roadmap.
Anyway, many thanks for the work done since then, but it isn't enough. We don't need another mobile app restyling... We need to stop manually adding things that are basically standard class features.
And, we definitely need everything could be a container (items, magic items, creatures). A flag to set it a container is enough, then a pop-up list in every object tooltip to chose from what has the flag is enough, together with an open field for weight contents multiplier (0 - Bag of Holding) and maximum weight the container can accommodate.
We need trade goods as well (trade bars, gems, jewelry, transportations), services (hirelings, sages, spell casting, temple healing, inns and taverns costs and lodging) and deity (at least the ones presented on PHB and supplements).
Start giving us some of those, and the route should be found again.
Just my 2 cents.
Beyond the Woods (HB) - DM
Curse of Strahd - DM
Out of the Abyss - DM
Tomb of Annihilation - DM
Playing and Mastering D&D since 1984.