I was wondering if anyone knows if there is a way to hide the multitude of options that show up when options for a feature are created. I'm making a draconic barbarian subclass, and I wanted to list the dragon options nicely in a table like the official draconic bloodline sorcerer does.

Unfortunately, all of the options show up after the table also, unlike for the official draconic bloodline sorcerer.

I can't find any options to do this within the subclass builder, and I already made a copy of the draconic bloodline sorcerer to see if there was something in the way it was set up. Although the sorcerer subclass still benefits from the options staying hidden after the table, there seems to be no way of coping this effect for the barbarian subclass.

Help please?

You see all of those options as the creator. But as long as you don’t publish your subclass nobody else will be able to see them at all. The table is purely cosmetic, you can simply drag highlight the table from the Sorcerer subclass and copy/paste it into the description for your Barbarian subclass and change the contents to match the options you’ve created. (In the past the options would stay hidden even after sharing a homebrew and we would have to create a separate class feature to show all of that at the end of the subclass after all of the features. But now once we publish our ‘brews everyone sees the options like we do. 😐 

Its a simple fact that we only have “user access” to the creation software (what we use as the “homebrewer”) but the DDB Devs who code the official stuff have Admin privileges. They can do more with the tool than we can.

Quote from IamSposta >>

You see all of those options as the creator. But as long as you don’t publish your subclass nobody else will be able to see them at all. The table is purely cosmetic, you can simply drag highlight the table from the Sorcerer subclass and copy/paste it into the description for your Barbarian subclass and change the contents to match the options you’ve created. (In the past the options would stay hidden even after sharing a homebrew and we would have to create a separate class feature to show all of that at the end of the subclass after all of the features. But now once we publish our ‘brews everyone sees the options like we do. 😐 

Its a simple fact that we only have “user access” to the creation software (what we use as the “homebrewer”) but the DDB Devs who code the official stuff have Admin privileges. They can do more with the tool than we can.

I plan on publishing the subclass, which is what has me worried about al of these repeated options. Visually, it's a lot uglier to use only the options that I can't seem to hide, and it's absurd to use both the table and the options.

So you're saying that the Draconic Bloodline Sorcerer subclass has developer options already in place, which are copied over when duplicating that subclass (to test the creator interface). That sucks. I'd REALLY like to be able to hide the options from view. The table is so much nicer. If we can have access to that option hiding on that subclass, why can't we have it for our own original works? UGH.

I've already set up a table for my subclass, but thanks. It has the gem dragons added, so the sorcerer's is too short to copy. (Pro Tip → Steal a table form the magic items lists. Those tables are much longer, so they're good for a lot of homebrew things.)

I just click the little button with the html symbol   </>   and edit stuff. Adding extra rows is as easy as copy/paste. (I’m no wiz, but the two semesters of programming I took over 20 years ago is still amazingly somewhat relevant.)

Quote from IamSposta >>

I just click the little button with the html symbol   </>   and edit stuff. Adding extra rows is as easy as copy/paste. (I’m no wiz, but the two semesters of programming I took over 20 years ago is still amazingly somewhat relevant.)

 alright maybe my tip isn't "pro", but it's useful for amateurs with no programming experience. Ha!

This problem is especially annoying, because adding in the later versions of features dependent on the earlier options just adds yet MORE options to the page... I'm trying to figure out a satisfiing way to keep it all cut down or hidden, but not a lot shows promise.

The best you can do is limit the description for each Option down to the minimum 2-4 words and stick everything in the parent feature’s description.

Trust me, I have a couple subclasses that use option trees and they look a right mess now. And that’s with 5 options at a lower level (player picks 1) and those trigger “granted” options at two higher levels that are more “upgrades” or something than genuine options. But it basically shows 15 options across 3 different levels in what is already a veeerryyy long subclass because it includes several small loredumps because it’s the Witcher recreated in D&D. (With a whole suite of Signs, the core 5 Aard, Axii, Igni, Quen, Yrden, being the focus for those options based on which Sign is your “rote” or “primary” sign at the time.) And another fighter where one lower level feature pops of granted options based on choices you make late (like an inverted tree) right mess to look at.

After those I planned for the current layout on my next project. Except, since it’s still getting playtested and edited it isn’t published yet. So even though I can send friends I’m in campaigns with the links and they can view them and such, since it’s unpublished they still see it the old way. But I don’t design them an lay them out that way anymore. (We used to create an entirely cosmetic feature As nothing but a list of the options all grouped together, like how Infusions and Invocations, and Maneuvers, etc. And we would bury it waayyy in the back and set as hidden in builder & on sheet.) Since I don’t do it that way anymore one of of my Artificers is incomprehensible. (I mean that literally. The One Big Main Thing with the Three Big Main Options” [to keep it tidy] is unreadable because nobody but me can read the options….🤦‍♂️

I've figured out my own fix, though it's a lot of work. Instead of putting in the options as options to the base subclass feature, I'm making Replacement subclass features for each damage type that would have been an option instead. This keeps the subclass page looking nice, and the character builder working in effectively, the exact same way—you just choose from a drop down menu which you want.

This should also let me add in the later variations of features to those initial features (as later level unlocked aspects of the same feature) without adding yet more options to the subclass page.

Just be prepared for nobody to understand that and folks to either tell you it’s broken and doesn’t work or complain at you that you “didn’t do it right.” 🙄

Quote from IamSposta >>

Just be prepared for nobody to understand that and folks to either tell you it’s broken and doesn’t work or complain at you that you “didn’t do it right.” 🙄

 No one has ever commented on my plethora of homebrew yet (accept for one, on a spell that was out of date anyway).

I won't expect it, but I can easily leave a comment on the subclass to alert people of the way it's designed. Thankyou for the notice.

Here's the subclass: Path of the Furious Wyrm