Hi Team, Warlocks are still unable to take Agonizing Blast more than once in the new 2024 Class Character Sheet despite the new rules saying this is allowed: Prerequisite: Level 2+ Warlock, a Warlock Cantrip That Deals Damage Choose one of your known Warlock cantrips that deals damage. You can add your Charisma modifier to that spell’s damage rolls. Repeatable. You can gain this invocation more than once. Each time you do so, choose a different eligible cantrip.
I'd like to think if enough people show they care about something they'd like to see improved then the dev team could change their mind - especially since as the person above pointed out, we are paying for the product and where else should that money go if not into improving the products we'd like improved :)
Actually, Devs rarely visit forums for this purpose. The main issue threads are tracked and watched by mods. When a new issue arises a mod may flag the thread as bug to indicate it has been raised to devs and when resolved the mod return to the thread to update it and change the flag to resolved. They should not do this for multiple threads of the same thing as this only creates more work. The book main issues thread are tracked by mods and other site staff and more closely monitored. This keeps the source of feedback consolidated which makes it easier to track, to gauge interest, to consider prioritisation at a glance. Creating multiple new threads only serves to scatter the feedback to multiple places not watched, making it harder to track, and possibly create more work for mods. Since the issue has been raised there's nothing a mod can do so creating more duplicate threads with nothing to actually add just pushes down the new threads about new things. This just means it's more effort for mods to see the new things and perform their moderator duties.
So, actually it doesn't increase visibility - it actually makes it more difficult for devs and mods.
--
Speaking of prioritisation: if a bug has an easy user-side fix like this one, it will be low priority. You can easily use ad hoc customisation or homebrew tools to workaround this issue. . New content takes priority, and there's been a lot lately, and actual problematic bugs take priority, bugs that have no user-workaround for have priority, site security updates have priority, and so on. They are a small team with a huge workload that encompasses far more than fixing bugs you find inconvenient.
As for: "we are paying for the product and where else should that money go if not into improving the products we'd like improved :)"
Adding new content to compendium with cross-linking.
Keeping security protocols on server up to date to ensure compliant with data security regulations.
Expanding data storage.
Server and site maintenance.
HR
Legal team
Marketing
Finance team - internal (auditing, taxes, banking) and external (customer-focused)
Management (CEO, secretaries, assistants, group leaders, etc)
Maps VTT development and updates.
Other tool development and updates.
E-Merchant Services
Site hosting and domain registration.
Etc. Etc. The list is just very long.
Running a business is more complicated than you seem to think and while money should go into improving the service it is important to note the money must go for other things too, there is a limited amount. There's only so much a dev team can work on so it becomes a matter of priority. Do they prioritise the latest book release and the new things and new bugs that can cause and potentially cause big crashes if not done properly, or the small little thing users can fix themselves in all of a few minutes or less? Yeah, they'll fix the big things so the site will keep running. No amount of duplicate threads will change that.
Click ✨ HERE ✨ For My Youtube Videos featuring Guides, Tips & Tricks for using D&D Beyond. Need help with Homebrew? Check out ✨ thisFAQ/Guide thread ✨ by IamSposta.
I dunno, that seems like a really long way to say an issue that affect every warlock player now needs to rely on difficult workarounds because they're a big company.
Sure, I agree. But it's still a pretty widely affecting issue that I personally think should be resolved.
Thanks for your opinion:)
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Hi Team,
Warlocks are still unable to take Agonizing Blast more than once in the new 2024 Class Character Sheet despite the new rules saying this is allowed:
Prerequisite: Level 2+ Warlock, a Warlock Cantrip That Deals Damage
Choose one of your known Warlock cantrips that deals damage. You can add your Charisma modifier to that spell’s damage rolls.
Repeatable. You can gain this invocation more than once. Each time you do so, choose a different eligible cantrip.
Yes, this is known. It's a limitation of the framework of the site. There are no known plans to redo the code of the site.
Please remember to check for existing threads on a subject.
DM, player & homebrewer(Current homebrew project is an unofficial conversion of SBURB/SGRUB from Homestuck into DND 5e)
Once made Maxwell's Silver Hammer come down upon Strahd's head to make sure he was dead.
Always study & sharpen philosophical razors. They save a lot of trouble.
that kind of sounds like a product we both buy and subscribe to isnt working properly or as advertised with no plans to fix it.
I'd like to think if enough people show they care about something they'd like to see improved then the dev team could change their mind - especially since as the person above pointed out, we are paying for the product and where else should that money go if not into improving the products we'd like improved :)
Then reply in the main thread on this after searching to make sure there aren't, what, 10 duplicates that have come & gone.
I want this fixed just so the duplicate threads go away.
DM, player & homebrewer(Current homebrew project is an unofficial conversion of SBURB/SGRUB from Homestuck into DND 5e)
Once made Maxwell's Silver Hammer come down upon Strahd's head to make sure he was dead.
Always study & sharpen philosophical razors. They save a lot of trouble.
Yeah you get the point :)
The duplicate threads are more visible haha
Appreciate your engagement 😀 ✌️
Actually, Devs rarely visit forums for this purpose. The main issue threads are tracked and watched by mods. When a new issue arises a mod may flag the thread as bug to indicate it has been raised to devs and when resolved the mod return to the thread to update it and change the flag to resolved. They should not do this for multiple threads of the same thing as this only creates more work. The book main issues thread are tracked by mods and other site staff and more closely monitored. This keeps the source of feedback consolidated which makes it easier to track, to gauge interest, to consider prioritisation at a glance. Creating multiple new threads only serves to scatter the feedback to multiple places not watched, making it harder to track, and possibly create more work for mods. Since the issue has been raised there's nothing a mod can do so creating more duplicate threads with nothing to actually add just pushes down the new threads about new things. This just means it's more effort for mods to see the new things and perform their moderator duties.
So, actually it doesn't increase visibility - it actually makes it more difficult for devs and mods.
--
Speaking of prioritisation: if a bug has an easy user-side fix like this one, it will be low priority. You can easily use ad hoc customisation or homebrew tools to workaround this issue. . New content takes priority, and there's been a lot lately, and actual problematic bugs take priority, bugs that have no user-workaround for have priority, site security updates have priority, and so on. They are a small team with a huge workload that encompasses far more than fixing bugs you find inconvenient.
As for: "we are paying for the product and where else should that money go if not into improving the products we'd like improved :)"
Running a business is more complicated than you seem to think and while money should go into improving the service it is important to note the money must go for other things too, there is a limited amount. There's only so much a dev team can work on so it becomes a matter of priority. Do they prioritise the latest book release and the new things and new bugs that can cause and potentially cause big crashes if not done properly, or the small little thing users can fix themselves in all of a few minutes or less? Yeah, they'll fix the big things so the site will keep running. No amount of duplicate threads will change that.
Click ✨ HERE ✨ For My Youtube Videos featuring Guides, Tips & Tricks for using D&D Beyond.
Need help with Homebrew? Check out ✨ this FAQ/Guide thread ✨ by IamSposta.
I dunno, that seems like a really long way to say an issue that affect every warlock player now needs to rely on difficult workarounds because they're a big company.
Sure, I agree. But it's still a pretty widely affecting issue that I personally think should be resolved.
Thanks for your opinion:)