Shadow Mage

Quote from Kolzax >>

Honestly I think it’s kind of funny that all this has been said about a subclass I created over 4 years ago before I even really started playing D&D. This is probably the first I created with obviously little to no understanding of how the game works, or how subclasses should be defined mechanically and more vague. Indeed this is a complete and utter failure and wholly agree, and what makes it even funnier is how this subclass isn’t even in my collection anymore!

So I guess the question is weather you simply forget about this subclass or ask me to create an updated version of this subclass with a more mature and defined understanding of the game. Up to you, I couldn’t care either way. (It’ll probably get a new name too, cause “Shadow Mage” - it’s a warlock eesh!)

 I would definitely like if this was updated to be usable

So.... no specification on levels... Do I get all of this at level 1. That would be pretty sick :)

This is top tier character development, from a mere warlock of the Shadowfell to it's emperor
Bravo Vince, truly perfect cinema

Honestly I think it’s kind of funny that all this has been said about a subclass I created over 4 years ago before I even really started playing D&D. This is probably the first I created with obviously little to no understanding of how the game works, or how subclasses should be defined mechanically and more vague. Indeed this is a complete and utter failure and wholly agree, and what makes it even funnier is how this subclass isn’t even in my collection anymore!

So I guess the question is weather you simply forget about this subclass or ask me to create an updated version of this subclass with a more mature and defined understanding of the game. Up to you, I couldn’t care either way. (It’ll probably get a new name too, cause “Shadow Mage” - it’s a warlock eesh!)

you cant really put branching subclasses *in* a subclass.

since there's no more of anything that can be considered rules or mechanics, all that's left to critique is the god awful lore.
first of all there's too much.
As a roleplaying game DnD has an established setting but also works hard to make most if-not all spells and class and such flavour text, generic enough, that it could fit most anyone's DnD game's no matter the homebrew setting. But by picking this subclass you are shackled by "rules" as written, to whatever "the reaper" is, a godlike entity that you have the mandatory fate of overthrowing.
On the other sub-subclass there's a lesser referenced faction you're bound to.
This may be fun for the single character the writer almost definitely had in mind for this but it wouldnt be for anyone with an ounce of creativity. What if i wanted to change my power, become a god of a different domane, or litterally anything else with my fate? Nope. I *have become the reaper now*.
This combined with all of the references to the future or how others see "you" the player betray a fundamental lack of understanding on how any of this works. A fundamental lack of comprehension as to the role of flavourtext for a class in a roleplaying game. It is not the job of flavour text to make my entire character for me, and it is DEFINETLY not it's job to plot and dictate my exact fate, arc, and seemingly my primary motivation for me.

even if the point of subclasses was to just make up cool conscepts and not write any rules or mechanics; this would still be terribly written, cringe-inducingly edgy, uncreative, generic, restrictive to players.
And honestly boring, i'd hate to play someone who just wins and wins and gets handed all this power, becoming *the Reaper* through no effort or sacrifice but just because i levelled up one assumes? Boring. Stupid.

It tells a story, but fails to be useful in an actual game.

erm... awkward!!!

Yeah but what's the crunch?

You went through so many versions but never included a single mechanic. Impressive.

So like...... what does it do??