It's confusing that it's short-term unfixable, Stormknight, because the Natural Explorer ability, which progresses in the same way, works just fine on the front end. Is there a reason that Favored Enemy can't be treated the same way as Natural Explorer?
It may have to do with humanoids having to pick to subtypes (so the features have to be separate instead of 1 feature that gets more options as you level up).
Is it possible to show each instance of Favored Enemy, based on the level its gained, rather than attempting to read each one and pull them to one field?
No. When a fix is put out your first clue will be that the character sheet has new features, because the bug is tied into how the character sheet is designed.
It's confusing that it's short-term unfixable, Stormknight, because the Natural Explorer ability, which progresses in the same way, works just fine on the front end. Is there a reason that Favored Enemy can't be treated the same way as Natural Explorer?
I'm having the same issue, but as I look at both Natural Explorer and Favored Enemy and the difference I do see is that on the Class Features edit section both Natural Explorer are managed under one drop-down section while Favored Enemy shows up as 2 different sections. The first Favored Enemy says (1st level) and then second says (6th level) but Natural Explorer says 1st level and has both selection drop-down menus. So this seems like a UI issue more than backend.
could be the amount of time it takes to fix the UI is not worth it because they think they're launching a re-design anyway.
dndbeyond forgets that a lot of nerds work in tech/engineering/product making. we know how it goes....now re-prioritize that backlog with favored enemy (စ‿စ )
The thing I'm hung up on is that Favored Enemy is something that every Ranger gets. That means that every single level 6+ Ranger is broken on dndbeyond. I feel like that should be important to them.
The thing I'm hung up on is that Favored Enemy is something that every Ranger gets. That means that every single level 6+ Ranger is broken on dndbeyond. I feel like that should be important to them.
I've mentioned this before, but the same bug effects ASIs. So every single level 8 or higher character is broken.
the news I have on this is somewhat limited, but I wanted to let you know it's not being ignored!
The issue has been fully investigated, in terms of exactly which features are affected by this problem.
It's a design issue, rather than a bug, so it's not something that can be just fixed. It is my understanding that changing the way such abilities are displayed on the character sheet would cause a lot of other problems.
I've spoken with staff about this and it is being addressed, but as part of a larger piece of work.
I hope that helps and apologies that I'm not able to give you a timeframe on that.
Yup, that one from a forum moderator but nobody from the D&D development team. So, when I hear from one of the THEM, then I will know it is ACTUALLY being addressed instead of a forum moderator just putting out the propoganda that WOTC told them to.
Yup, that one from a forum moderator but nobody from the D&D development team. So, when I hear from one of the THEM, then I will know it is ACTUALLY being addressed instead of a forum moderator just putting out the propoganda that WOTC told them to.
DDB is not run by WotC. It is the propaganda the devs told them to put out.
It may have to do with humanoids having to pick to subtypes (so the features have to be separate instead of 1 feature that gets more options as you level up).
it is like adding a new thing as opposed to progressing a current thing. but yeah it would be nice if there was a quick fix just to display it.
Same issue here with one of my player's Ranger:
https://www.dndbeyond.com/profile/JorthinSkogurson/characters/15168502
Is it possible to show each instance of Favored Enemy, based on the level its gained, rather than attempting to read each one and pull them to one field?
Still a problem. Was a fix put out?
No. When a fix is put out your first clue will be that the character sheet has new features, because the bug is tied into how the character sheet is designed.
Stormknight said as much a month ago.
I'm having the same issue, but as I look at both Natural Explorer and Favored Enemy and the difference I do see is that on the Class Features edit section both Natural Explorer are managed under one drop-down section while Favored Enemy shows up as 2 different sections. The first Favored Enemy says (1st level) and then second says (6th level) but Natural Explorer says 1st level and has both selection drop-down menus. So this seems like a UI issue more than backend.
could be the amount of time it takes to fix the UI is not worth it because they think they're launching a re-design anyway.
dndbeyond forgets that a lot of nerds work in tech/engineering/product making. we know how it goes....now re-prioritize that backlog with favored enemy (စ‿စ )
The thing I'm hung up on is that Favored Enemy is something that every Ranger gets. That means that every single level 6+ Ranger is broken on dndbeyond. I feel like that should be important to them.
I've mentioned this before, but the same bug effects ASIs. So every single level 8 or higher character is broken.
Yup. Once you get to 6th Level Ranger, D&D Beyond is pretty useless.
That's an exaggeration. DDB still correctly tracks the features that are useful more than 10% of the time.
I WAS being a bit sarcastic, but the lack of response from anyone at DDB lead me to believe they don't give a crap.
You mean like this response from over a month ago?
Yup, that one from a forum moderator but nobody from the D&D development team. So, when I hear from one of the THEM, then I will know it is ACTUALLY being addressed instead of a forum moderator just putting out the propoganda that WOTC told them to.
DDB is not run by WotC. It is the propaganda the devs told them to put out.
I am having this issue too. The issue still exists.
That is because the major character sheet update that is already planned to fix this is not ready yet.
I hope this frequently repeated response is as helpful as your frequently repeated comment is.
Still having the issue.