I’m having difficulty seeing when the new options will be available here on DnD Beyond. Anyone have a time table?

I have seen some in other threads that it was typically the Monday after the release from WoTC. This one seemed like a bit more of a surprise so I don't know how much lead time they had to get it implemented. But I'm hoping this week because I am currently playing a dragonborn that I am going to switch to the new UA race.

Edit: I'm wondering now if they were waiting for the app to be released so they could get some news for it before jumping into the new UA stuff. We will see if in the next few days they drop that on the site.

Anxious to update my Dragonborn also!

Right, I’ve always wanted to play a Dragonborn but the other races in my opinion had better options

Their response on twitter is just that they refuse to give an ETA.

I think people are sleeping on the new Kobold UA. Drawing a lot of hate also which I really don't understand compared to the Gem Dragonborn. The sooner the better for sure!

Hopefully today or tomorrow (before my next game!)

Yeah, still unfortunately not up. Wish they would have this sort of thing sorted prior to releasing it on UA. Not a big deal if actually playing in person, but kind of a pain when on Roll20 or Foundry having to remind the DM what the heck you are doing.

Have we heard anything on this yet? 

Nope still in the dark on when it will be on the site.

This has been quite a long time waiting. Wish they would roll it out in phases at this point. Races/feats/spells.

I blame the kobolds for the delay.  

What might work is connecting an older Sega Genesis 6 button controller and doing the following A,B,B,A,C,A,B up, down, left, right, um no that's not it that allows you to play as Akuma

Still nothing...my 5e companion app just updated with them at least

Other than the CFVs, this is the longest I have ever seen a UA go without being implemented. I wonder why…? 🤔

My guess is:

1. they are short staffed - (prioritizing new app and new sourcebooks). 

2. They are having a hard time coding variable class feature options [Kobold]  that feed into the character sheet properly.

C. All of the above. 

Just being hopeful this morning as I check my dragonborn character and see if I have options when I try to change his race. :(

Quote from RaoGung >>

2. They are having a hard time coding variable class feature options [Kobold]  that feed into the character sheet properly.

 I think you’re right about this one (dispute being wrong). I just tried to build it as a variant and hit two snags: I would have had to invent a feature just to replace Sunlight Sensitivity, I couldn’t make a sub-option to allow the player to pick the correct Ability for their Cantrip. (But the Kobold cannot have “class feature options” since it is a race, not a class. 😜)

I wonder if it's not just the fact that Kobold is UA that completely overwrites an existing bit of content. Over time there will be "original Kobold," "UA Kobold," and "new Kobold." All of these need to be distinguishable but they all have the exact same name. Say you see Kobold [archived] on your DDB character after the new published version comes out. Is that the original version archived or the UA version? Are these even meant to overwrite each other or will the published content indicate that they are actually subraces? I would bet that some of this had not even been decided at the time of the UA release, so DDB is in a tough position trying to code all this in a way that doesn't cause problems if WotC pulls back from its original position which is already a bit vague no matter how you look at it.

Quote from scatterbraind >>

I wonder if it's not just the fact that Kobold is UA that completely overwrites an existing bit of content. Over time there will be "original Kobold," "UA Kobold," and "new Kobold." All of these need to be distinguishable but they all have the exact same name. Say you see Kobold [archived] on your DDB character after the new published version comes out. Is that the original version archived or the UA version? Are these even meant to overwrite each other or will the published content indicate that they are actually subraces? I would bet that some of this had not even been decided at the time of the UA release, so DDB is in a tough position trying to code all this in a way that doesn't cause problems if WotC pulls back from its original position which is already a bit vague no matter how you look at it.

 Why should that be any issue at all? In the PHB there is technically no such thing as a “Variant Human,” there is simply a small bit of boxed text that offers “variant Human traits.” DDB technically had to invent it as a “Race Variant,” and because the workflow requires a name, they labeled it “Variant Human.” This Kobold should theoretically work the same way, simply call it “Variant Kobold (UA)” and if it ever goes to print there would be a “Variant Kobold” listed, and floating around somewhere would be various PCs that would inevitably still use this version and it would just end up displaying as “Variant Kobold (Archived)” after DDB updates the name to reflect the status.

If I were a betting man, and I am, my money would go on the fact that it is currently not possible in DDB’s system to implement options within options, nor are they allowed to add features that should not exist. So to actually implement this “Variant Kobold,” they would have to create the middle option as three distinct options, one for each of the potential spellcasting Abilities. I presume that would probably be okay by WotC since so many of the already published official feats had to be implemented in a similar fashion. (Not to mention all of the other jank workarounds they’ve had to implement in order to overcome their software limitations. 😒)
    However, DDB would also have to create a “Sunlight Tolerant” trait (or some such other) to replace the “Sunlight Sensitivity” trait Kobolds normally have, and that may be an issue for them depending on the terms of their contract. And it may not be something they are necessarily willing to throw dollars at lawyers to figure out since this is only UA.

What reason do I have to put my bet on that being a likely issue? Because earlier today I started to construct this Variant Kobold if for no other reason than to prove RaoGung’s guess as incorrect. (Yeah, I know, it would’ve been a jerk move on my part. It was immature of me. I had a bad morning and was feeling particularly antagonistic.) I got exactly halfway through when I understood why it would be an issue. (That’s why I came back just to say I believe RaoGung was in fact correct. I’m at least mature enough to give credit when due and to admit I was both wrong and jerkish.)

Edit: PS- I went back and finished creating this Kobold, snippets, actions and all. if anyone is interested in a copy, PM me.

It certainly seems that Dndbeyond is reducing the amount of resources dedicated to fixing bugs and making efforts since Adam left. Presumably its more exciting to spend money on marketing gimmicks than content and core services.

If I sound salty, look for the forum on the divine soul sorcerer spell swap (allowing you to swap out the divine sorcerer spell granted at first level to expand spell options for the sorcerer). This core element of the subclass has been in progress for nearly 3 YEARS.

*waves in Life Cleric*

I don't think they're dedicating less resources so much as are being either overly careful about not breaking anything while unpicking the gordian knot they painted themselves into, or not having the infrastructural resources to move what they can onto a new backend and maintain the other backend for the stuff we've had to homebrew and jigger together in the meantime. Few sites do, because the issue scales with size. But it'd still be nice if they'd improve their communications around it. The dev update transcripts have stopped too (though the autotranscribed ones were so terrible I couldn't read them).