Just adding more voices to this. While I've been able to come up with workarounds for a lot of other 2024 rules as written still not working on Beyond, this one seems really tricky to fix, so it would be great if they could actually fix it!
They should set it up to have a sub-selection of a cantrip rather than specific cantrip stated in the invocation dropdown... I suspect there's some coding needed, so guessing that's why this is still MIA.
It is April 7th 2025 and this is STILL an issue. What is wrong with these programmers?
They only care about pushing new product to generate revenue. They don't believe fixing existing issues generates any revenue. What they continue to fail to realize is shoddy product is losing them support, and at some point will lose them subscribers.
There's like 5-6 new 3rd-party books I have not yet bought, and usually I buy them the moment I see them. If I can't use what I've already purchased, why would I throw more money at them?
Get it right if you want to keep earning my money.
Not to mention one of the newest books they added Obojima is VERY broken on DnD Beyond. Almost nothing works and you cant use any subclass with the 2024 rules. But the programmers swear that isn't supposed to be the case.
Yeah, I regret buying Obojima. That might be the last purchase I make for a long while. :(
Also, buying the LotR book wrecked my ability to use Beyond's random sheet generator to create NPCs on the fly. The LotR classes keep popping in.
At least they dropped the 3d VTT development no one asked for or wanted, but the problem is, they simply don't seem to be willing to task enough dev to resolve their existing problems.
The huge influx of partnered content right now is a huge money grab red flag.
Fix Agonizing Blast. Fix 2024 homebrew creation. Show us a list of the bugs that you're aware of, and where they are in the bugfix process. This shouldn't be a huge black box of people screaming on forums about problems just so they have a outlet without any knowledge or understanding of what's being worked on.
Just adding yet another voice to the topic. It's been a hot minute since I made a new character and I was flabberghasted that this feature from the 2024 rules doesn't even exist?
Not to mention one of the newest books they added Obojima is VERY broken on DnD Beyond. Almost nothing works and you cant use any subclass with the 2024 rules. But the programmers swear that isn't supposed to be the case.
The brokenness is a legitimate issue; however, the 2024 subclass versions have to come from the third-party dev and they haven't submitted them yet. That's behavior as required (since Beyond isn't permitted to unilaterally apply the updates).
Still not fixed, and even though it says you can select this invocation multiple times, you also can absolutely not do that.
Selected Repelling Blast today and can't selec the cantrip to apply it to. Wizards, we could use a fix on this.
Do you think they'll ever fix agonizing blast? It's March (almost April) and its still broken on DDB.
Just adding more voices to this. While I've been able to come up with workarounds for a lot of other 2024 rules as written still not working on Beyond, this one seems really tricky to fix, so it would be great if they could actually fix it!
They should set it up to have a sub-selection of a cantrip rather than specific cantrip stated in the invocation dropdown... I suspect there's some coding needed, so guessing that's why this is still MIA.
April bump.
Adding to the bump. This is well past ridiculous.
also adding to the bump. its been a while since this was first brought up.
some of us like using other cantrips other than eldritch blast for agonizing blast, and the invocations tagged "repeatable" are not repeatable.
This is a wee bit silly, tbf
Maybe it becomes something worth fixing once this thread hits 50 comments?
It is April 7th 2025 and this is STILL an issue. What is wrong with these programmers?
They only care about pushing new product to generate revenue. They don't believe fixing existing issues generates any revenue. What they continue to fail to realize is shoddy product is losing them support, and at some point will lose them subscribers.
There's like 5-6 new 3rd-party books I have not yet bought, and usually I buy them the moment I see them. If I can't use what I've already purchased, why would I throw more money at them?
Get it right if you want to keep earning my money.
Not to mention one of the newest books they added Obojima is VERY broken on DnD Beyond. Almost nothing works and you cant use any subclass with the 2024 rules. But the programmers swear that isn't supposed to be the case.
Yeah, I regret buying Obojima. That might be the last purchase I make for a long while. :(
Also, buying the LotR book wrecked my ability to use Beyond's random sheet generator to create NPCs on the fly. The LotR classes keep popping in.
At least they dropped the 3d VTT development no one asked for or wanted, but the problem is, they simply don't seem to be willing to task enough dev to resolve their existing problems.
The huge influx of partnered content right now is a huge money grab red flag.
Fix Agonizing Blast. Fix 2024 homebrew creation. Show us a list of the bugs that you're aware of, and where they are in the bugfix process. This shouldn't be a huge black box of people screaming on forums about problems just so they have a outlet without any knowledge or understanding of what's being worked on.
Just adding yet another voice to the topic. It's been a hot minute since I made a new character and I was flabberghasted that this feature from the 2024 rules doesn't even exist?
The brokenness is a legitimate issue; however, the 2024 subclass versions have to come from the third-party dev and they haven't submitted them yet. That's behavior as required (since Beyond isn't permitted to unilaterally apply the updates).
Hate to necromancer this but we are in April now and still having this issue
This is simply absurd
Still not fixed as of April 11th 2025. Maybe give us the digital content we paid for, or refund us.
An inventory bug as come and been fixed but this still isnt.
Adding my complaint to the list. How about rehiring the Sigil folks to fix core bugs that have been around for months?