Please use the Search function to confirm if someone has already posted your bug. This is 21 pages of people reporting the same bugs over and over and that's not really helpful for anyone.
Bug reports should have repeat reports. If only a single user reports a bug and no other users confirm the bug with additional reports, it could indicate an account issue, user error, or a number of other issues. If multiple users report the same bug, it could confirm an actual bug as well as multiple ways for the developers to recreate the bug. We should not encourage others not to report a bug if they see that someone else has already posted about it. What should be encouraged is to provide as much detail as possible regarding the bug
I currently cannot select ability score improvement more than once. I am building a fighter and took it at 4th level but cannot select it at 6th or 8th level
Can we please get a list of known bugs and their status, like you all did in the Support Thread for Tasha's? I can see that you keep updating the original post, but there is no way to tell what is being changed.
The paladin that has the same style of feature, has the same issue. Ranger was going to be my first build and i realized that. You can go into the main character sheet into the feat section and manually put the fighting style in for now.
There is a workaround for this until it's fixed. There is a manage feats button in the character sheet under Features & Traits at the very bottom. You can also click the Feats tab to find it easier. You can add the feat to the character sheet there until they fix the issue
Studded leather armor shows up in inventory with the Mastery tag, and clicking on it to bring up the sidebar shows "Mastery: Nick (Dagger)" with the associated Nick description.
Likewise, my +1 leather armor is showing up with "Mastery: Nick (Light Hammer)," with the associated Nick description in the sidebar.
IKR? How long have they known the new books were coming out?
I figured they'd have featured tested all the updates.
"Can't support monk's extended reach"
Is it really that hard?
This feels like Tasha's all over again.
The forum reports of missing content there are legendary.
I'm actually surprised it's so inept! I had thought it would be better role out.
DDB Team: Here's our implementation plan that we (presumably) have mostly completed and tested. Community: NO! WE HATE IT! CHANGE IT NOW!!!!! DDB Team: OK, we're changing course a week out from our release to appease the community. ---- bugs ---- Community! OMG! I CAN'T BELIEVE THERE ARE SO MANY BUGS!! HOW LONG HAVE THEY HAD TO DO THIS??!!!
The Psi Warrior fighter's Telekinetic Shove is showing up as:
As a Bonus Action, you can telekinetically shove one creature you can see within 30 ft. of yourself. When you do so, the target must succeed on a Strength saving throw (DC 8+modifer:int+proficiency - Invalid keyword: modifer) or be moved 5 ft. toward or away from you.
Bug report: basic equipment from the 2014 phb is missing.
Also, If someone wants to make a character with the free release core classes they loose the ability to select options from older books IF that option now appears in the 2024 PHB. For instance I cannot create a core rules Rogue at 3rd level and select the subclass of Arcane Trickster or Soulknife because I don't own the 2024 PHB but the other Rogue subclasses from my other source books CAN be selected, like the Phantom (also from TCoE).
Paladin spells in Oath of Glory aren't configured correctly (I haven't checked other subclsasses). It has 'Consume Spell Slot' set to 'No' which results in the spells showing as 'At Will' on sheets and makes it so you need to manually consume slots when you cast them. Updating the 'Consume Spell Slot' setting to 'Yes' should fix it. It will just need to be done on all of the subclass spells.
IKR? How long have they known the new books were coming out?
I figured they'd have featured tested all the updates.
"Can't support monk's extended reach"
Is it really that hard?
This feels like Tasha's all over again.
The forum reports of missing content there are legendary.
I'm actually surprised it's so inept! I had thought it would be better role out.
DDB Team: Here's our implementation plan that we (presumably) have mostly completed and tested. Community: NO! WE HATE IT! CHANGE IT NOW!!!!! DDB Team: OK, we're changing course a week out from our release to appease the community. ---- bugs ---- Community! OMG! I CAN'T BELIEVE THERE ARE SO MANY BUGS!! HOW LONG HAVE THEY HAD TO DO THIS??!!!
Yeah....
On the one hand I am very appreciative that WOTC recognised the problem they had made for themselves by forcibly upgrading everyone's content whether they asked for it or not, was a problem of their own making and one they had the ability to fix.
For that they get this round of applause. -->👏
What I find staggering, however, is it hadn't apparently occoured to anyone on the implementation side that folk might not want to change up their counterspells etc mid campaign. It should always have been an option. One we are heavily encouraged and incentivised to take but not a fait accompli.
That they decided to back track and had the ability to do so tells me the decision to not impliment a toggle from the start wasn't focused on the user experience.
Onto the point at hand, I am not surprised there are problems caused by a new system roll out and one that as acknowledged underwent a pretty major revision before launch. What is shocking to me is the sheer number and volume and nature of the errors.
People are finding out pretty quick when they try to build characters that a particular feature doesn't work properly.It's like didn't they try building characters themselves before it went live and treating pre-order as a beta test?
If its so evidently obvious to all of us, the wonder has to be how was all of this missed before launch?
I'!m pretty incredulous, that despite knowing the design on the monk, for example for months before publication, a way was not found to code a variable for the value of an attacks reach. I'm not a coder but doesn't strike me as overly difficult. And yet it is an unsupported feature in their brand new PHB which we can't use, apparently.
I think a person can be forgiven at having their flabber ghasted, at the scale of the foreseeable errors, what might have been done to mitigate it.
I am unsure just how much or how many are related to the toggle implementation or the need to be backwards compatible.
Quite honestly, I had assumed it would be a relatively straightforward affair, I am genuinely surprised and confounded to find the litany of complaints growing by the hour.
So why is the Phantom rogue from Tasha's cauldron of everything, the book that's so pushed it was basically reprinted in this PHB, the only subclass from that book that isn't backwards compatible?
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Bug reports should have repeat reports. If only a single user reports a bug and no other users confirm the bug with additional reports, it could indicate an account issue, user error, or a number of other issues. If multiple users report the same bug, it could confirm an actual bug as well as multiple ways for the developers to recreate the bug. We should not encourage others not to report a bug if they see that someone else has already posted about it. What should be encouraged is to provide as much detail as possible regarding the bug
In the 2024 Gloom Stalker Subclass, Dreadful Strike doesn't have "uses" box unlike hunters mark for example.
I currently cannot select ability score improvement more than once. I am building a fighter and took it at 4th level but cannot select it at 6th or 8th level
Can we please get a list of known bugs and their status, like you all did in the Support Thread for Tasha's? I can see that you keep updating the original post, but there is no way to tell what is being changed.
The paladin that has the same style of feature, has the same issue. Ranger was going to be my first build and i realized that. You can go into the main character sheet into the feat section and manually put the fighting style in for now.
There is a workaround for this until it's fixed. There is a manage feats button in the character sheet under Features & Traits at the very bottom. You can also click the Feats tab to find it easier. You can add the feat to the character sheet there until they fix the issue
Missing A LOT of items when I try to add items to my character. Things like +1 studded leather, stone of good luck, ring of invisibility. Lots missing
Thank you so much :D
Very helpful and fast reply ^^
Have a great day
PbP - The Land of Kyralia - DM
Studded leather armor shows up in inventory with the Mastery tag, and clicking on it to bring up the sidebar shows "Mastery: Nick (Dagger)" with the associated Nick description.
Likewise, my +1 leather armor is showing up with "Mastery: Nick (Light Hammer)," with the associated Nick description in the sidebar.
Yep this right here.
The Psi Warrior fighter's Telekinetic Shove is showing up as:
Bard unarmed strike, for the Dazzling Footwork feature is not working as intended and is not referencing dex instead of strength.
Jack of all trades is still adding to Initiative. Is it supposed to? That is one for Sage Advice I think.
The Dragonhide belts from Fizzban's don't affect 2024 monk DC.
Cure wounds is abjuration in the book but evocation in the creator.
Bug report: basic equipment from the 2014 phb is missing.
Also, If someone wants to make a character with the free release core classes they loose the ability to select options from older books IF that option now appears in the 2024 PHB. For instance I cannot create a core rules Rogue at 3rd level and select the subclass of Arcane Trickster or Soulknife because I don't own the 2024 PHB but the other Rogue subclasses from my other source books CAN be selected, like the Phantom (also from TCoE).
Paladin spells in Oath of Glory aren't configured correctly (I haven't checked other subclsasses). It has 'Consume Spell Slot' set to 'No' which results in the spells showing as 'At Will' on sheets and makes it so you need to manually consume slots when you cast them. Updating the 'Consume Spell Slot' setting to 'Yes' should fix it. It will just need to be done on all of the subclass spells.
What is “that” that you are referring to at the start if the thread.
On the one hand I am very appreciative that WOTC recognised the problem they had made for themselves by forcibly upgrading everyone's content whether they asked for it or not, was a problem of their own making and one they had the ability to fix.
For that they get this round of applause. -->👏
What I find staggering, however, is it hadn't apparently occoured to anyone on the implementation side that folk might not want to change up their counterspells etc mid campaign. It should always have been an option. One we are heavily encouraged and incentivised to take but not a fait accompli.
That they decided to back track and had the ability to do so tells me the decision to not impliment a toggle from the start wasn't focused on the user experience.
Onto the point at hand, I am not surprised there are problems caused by a new system roll out and one that as acknowledged underwent a pretty major revision before launch. What is shocking to me is the sheer number and volume and nature of the errors.
People are finding out pretty quick when they try to build characters that a particular feature doesn't work properly.It's like didn't they try building characters themselves before it went live and treating pre-order as a beta test?
If its so evidently obvious to all of us, the wonder has to be how was all of this missed before launch?
I'!m pretty incredulous, that despite knowing the design on the monk, for example for months before publication, a way was not found to code a variable for the value of an attacks reach. I'm not a coder but doesn't strike me as overly difficult. And yet it is an unsupported feature in their brand new PHB which we can't use, apparently.
I think a person can be forgiven at having their flabber ghasted, at the scale of the foreseeable errors, what might have been done to mitigate it.
I am unsure just how much or how many are related to the toggle implementation or the need to be backwards compatible.
Quite honestly, I had assumed it would be a relatively straightforward affair, I am genuinely surprised and confounded to find the litany of complaints growing by the hour.
Bug Report: Epic Boon Feat - Boon of Energy resistance is giving a flat +10 to ability checks instead of the additional +10 to Con Score Maximum.
Celestial warlock subclass spells are listed as "at will" instead of just prepared.
When choosing the various blasts options in invocations there is no drop down menu to select your chosen spell
Lessons of the First ones invocation does not allow you to select the origin feat.
So why is the Phantom rogue from Tasha's cauldron of everything, the book that's so pushed it was basically reprinted in this PHB, the only subclass from that book that isn't backwards compatible?