I don't know if this has already been reported.

I'm building a fiend warlock currently, and for some reason the fiend spells are not automatically added as prepared spells when reaching any of the required levels for them. I have not checked if this is a general thing for all warlock subclasses, or even other subclasses.

PS: I should add that when I view the character sheet outside of managing it, the spells are added and usable as expected. But it seems odd that I can accidentally select them when picking spells as well, since they are already unlocked and prepared.

A lot of warlock and paladin are still unplayable in the 2024 rules because their subclass’ spell are not added to the spell they know (Conquest Paladin, Hexblade Warlock…).

It had been said old subclasses will be compatible but that was made with minimum effort

Which is why I and my group don't play with 2024 rules. I happen to run a paladin/warlock multiclass. I'm not moving to 2024 until the problems are fixed. And if they're not, we still have all the D&D books we bought over the years. D&D Beyond is supposed to make playing D&D more convenient. If it doesn't, that's fine. I've been playing D&D since the little white box in the 70s. Playing with D&D Beyond is the exception for me; I can draft up and run a campaign with graph papers and my 40-year+ collection of minis in my sleep (I actually have done that).

The paladin and the warlock are essentially fixed for the subclasses in the PHB. If you want to play one of the others. they provided the legacy updates they promised.

Subclasses are pretty easy to do in the homebrew to update them to have the prepared spells. I created homebrew for a unearthed arcana subclass class my DM said I could play, and it was quicker than I expected since I don't homebrew normally.

I know some people feel they shouldn't have to homebrew to play old subclasses, but if you want the best experience with legacy classes with free prepared spells that seems to be the best way to do it that I have found.

One of my players is happily playing a bladesinger / swashbuckler, and although they are legacy classes, he is happy with them. So they are playable.

Quote from Melfast >>

The paladin and the warlock are essentially fixed for the subclasses in the PHB. If you want to play one of the others. they provided the legacy updates they promised.

Subclasses are pretty easy to do in the homebrew to update them to have the prepared spells. I created homebrew for a unearthed arcana subclass class my DM said I could play, and it was quicker than I expected since I don't homebrew normally.

I know some people feel they shouldn't have to homebrew to play old subclasses, but if you want the best experience with legacy classes with free prepared spells that seems to be the best way to do it that I have found.

One of my players is happily playing a bladesinger / swashbuckler, and although they are legacy classes, he is happy with them. So they are playable.

 Invocations on 2024 Warlock are still not 100% of 100%, nor are they homebrew-able. The former is a mystery as to why not, the second is probably due to the usual "Spaghetti coding+Back end access required" combo.

Likewise, Paladins aren't 100% of 100%, and they both still aren't in 2014, either. Nothing is

What people seem to agree with is that 100% of 100% of material should be not only fully functional, but also all forms of content with a description and/or that is obtainable/learned should be homebrew-able.

All I want personally is that, in the PHB & all other releases, that "We(currently)cannot support (this)(at this time)" be followed up with "because X"(But X shouldn't just be "spaghetti coding+back end access required). If it's for a fixable reason & not just a budget cut issue from Hasbro, transparency would & should be paramount on why it can't be supported & thus homebrewed.

If it is a content you payed for you shouln’t have to homebrew it

Quote from bortDLonzo >>

Here are just a few bugs of things that I have encountered so far while playing around in the character creator, I'm sure things will get ironed out before full release but it's worth documenting them so they get the attention they need.

In the Classes section of Game Rules the class and subclass features do not indicate what level they are awarded.

Ritual Caster feat - not functioning correctly. Main dropdown has classes AND stats (int, cha, wis) in it. If you select a casting stat from the dropdown you indeed benefit from the +1 increase, however the ritual spells you then subsequently choose in the following dropdown menus do not appear in your characters known spells on the character sheet. If you choose a class from the stat increase dropdown you do not benefit from the +1 to a chosen stat and when you select the ritual caster spells you A) Aren't given enough dropdowns to correspond with your current proficiency bonus, my character has +4 proficiency and only has 3 dropdowns to choose spells from, and B) the third dropdown menu doesn't have any options in it.

Fighting Style - Ranger and Paladin are unable to select a fighting style from their dropdown menus.

Warlock Invocations - Agonizing Blast does not let you select one of your warlock cantrips to apply the bonus to, defaults to eldritch blast whether you have chosen eldritch blast as one of your cantrips or not. Also currently only able to select this invocation once, despite being a repeatable invocation.

 

Ritual Caster feat [STILL] isn't showing selected spells in the spells tab.
We're quickly approaching the one year mark.

Sort it tf out.

Men i would love if they just said "expanded content subclasses are not working for warlock". Like the prepared spells granted by the subclass are simply not appearing. It would be nice if it was mentioned somewhere, because right now it only appears as they are not acknowledging this issue.