The problem is DK already stands on its own well, or at least it did, before subclassing. That was something I liked about the old DK. Having some experience now with subclass and looking at their proposed changes, no amount of change is going to replace the utility provided by subclassing in some instances. I'm sorry/not sorry, but love/hate subclassing, we're not going back.
The question becomes, will the new DK abilities fit into subclassing, or will it be a standalone class? DK already isn't a strong subclass option, so the best-case scenario is to allow the DK to compete with it. But again, I think, in doing this, if you do too much to break down the DK Class identity, compete or not you have completely failed.
The problem is DK already stands on its own well, or at least it did, before subclassing. That was something I liked about the old DK. Having some experience now with subclass and looking at their proposed changes, no amount of change is going to replace the utility provided by subclassing in some instances. I'm sorry/not sorry, but love/hate subclassing, we're not going back.
The question becomes, will the new DK abilities fit into subclassing, or will it be a standalone class? DK already isn't a strong subclass option, so the best-case scenario is to allow the DK to compete with it. But again, I think, in doing this, if you do too much to break down the DK Class identity, compete or not you have completely failed.
The question becomes, will the new DK abilities fit into subclassing, or will it be a standalone class? DK already isn't a strong subclass option, so the best-case scenario is to allow the DK to compete with it. But again, I think, in doing this, if you do too much to break down the DK Class identity, compete or not you have completely failed.