Right.. it might work now!
You can setup class under main branches and under subbranches with the class under sub always being prioritized. Old code also allowed for a single class setups, you just had to pick the same class twice. Same thing will work now, you can not specify a class in which case it will be None or specify the same class twice in which case it will be applied only once.
Also, you can NEVER pick two classes from the same branch-tree! It simply will not work.
Also

Do not take the suggested farther/mother/parents/mc order as dogma, I want to allow any deviations from that design as long as descriptions/headers support it.
+ we need testing, it seems to work but you never know when a ctd will creep up on your with datastructure this branched out.
For some reason highlighting and sepia mask is fucked on mc tree, gonna look into that before I call it a night.