The first comment is from November 3, which is the day it was released, so that seems more like a numbering error on the comments rather than earlier comments being missing.
I suspect that WotC ought to have thought this one out just a little bit more because in the various Monster Manuals out there, a Death Knight is an Undead Monster.
I suspect that WotC ought to have thought this one out just a little bit more because in the various Monster Manuals out there, a Death Knight is an Undead Monster.
It's a class from the World of Warcraft MMO that happens to have the same name as a pre-existing monster from D&D. It's okay for two unrelated things to have the same name sometimes.
I suspect that WotC ought to have thought this one out just a little bit more because in the various Monster Manuals out there, a Death Knight is an Undead Monster.
It's a class from the World of Warcraft MMO that happens to have the same name as a pre-existing monster from D&D. It's okay for two unrelated things to have the same name sometimes.
Granted.....BUT......I do cringe when completely different things, objects or classes are given the same name. I have enough trouble differentiating between the 2014 PHB definition of a warlock and the 2024 PHB definition of a warlock when some one wants to combine the 2014 PHB, plus Tasha's Cauldron, plus Xanathar's Guide, plus the 2024 PHB definition of a warlock into one character and then that person begins to whine when the combination of parts do not play well together.
I suspect that WotC ought to have thought this one out just a little bit more because in the various Monster Manuals out there, a Death Knight is an Undead Monster.
It's a class from the World of Warcraft MMO that happens to have the same name as a pre-existing monster from D&D. It's okay for two unrelated things to have the same name sometimes.
Granted.....BUT......I do cringe when completely different things, objects or classes are given the same name. I have enough trouble differentiating between the 2014 PHB definition of a warlock and the 2024 PHB definition of a warlock when some one wants to combine the 2014 PHB, plus Tasha's Cauldron, plus Xanathar's Guide, plus the 2024 PHB definition of a warlock into one character and then that person begins to whine when the combination of parts do not play well together.
That's very much an individual issue. Whoever's the DM needs to put a foot down on that one. As for the Death Knight, yeah, you got the right answer already. WoW classes aren't going to be renamed just because there's also a monster by that name.
There's a few monsters with names of classes or subclasses in base D&D as well, not just a crossover issue. (Bard, Druid, and all 8 base Wizard classes are examples.)
I suspect that WotC ought to have thought this one out just a little bit more because in the various Monster Manuals out there, a Death Knight is an Undead Monster.
It's a class from the World of Warcraft MMO that happens to have the same name as a pre-existing monster from D&D. It's okay for two unrelated things to have the same name sometimes.
Granted.....BUT......I do cringe when completely different things, objects or classes are given the same name. I have enough trouble differentiating between the 2014 PHB definition of a warlock and the 2024 PHB definition of a warlock when some one wants to combine the 2014 PHB, plus Tasha's Cauldron, plus Xanathar's Guide, plus the 2024 PHB definition of a warlock into one character and then that person begins to whine when the combination of parts do not play well together.
That's very much an individual issue. Whoever's the DM needs to put a foot down on that one. As for the Death Knight, yeah, you got the right answer already. WoW classes aren't going to be renamed just because there's also a monster by that name.
There's a few monsters with names of classes or subclasses in base D&D as well, not just a crossover issue. (Bard, Druid, and all 8 base Wizard classes are examples.)
True, so true. When I create a character, I try to remain within the bounds of the 2024 PHB because I know that some of the 2014 rules are incompatible with the 2024 rules and I want to minimize any procedural snarls. Nothing blows a game session apart faster than a dispute over which rule takes precedence.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
When going to the DEATHKNIGHT class page and scrolling down to comments there no section for going to earlier comments.
I can only see comment 175 to 178.
The first comment is from November 3, which is the day it was released, so that seems more like a numbering error on the comments rather than earlier comments being missing.
pronouns: he/she/they
I suspect that WotC ought to have thought this one out just a little bit more because in the various Monster Manuals out there, a Death Knight is an Undead Monster.
It's a class from the World of Warcraft MMO that happens to have the same name as a pre-existing monster from D&D. It's okay for two unrelated things to have the same name sometimes.
pronouns: he/she/they
Granted.....BUT......I do cringe when completely different things, objects or classes are given the same name. I have enough trouble differentiating between the 2014 PHB definition of a warlock and the 2024 PHB definition of a warlock when some one wants to combine the 2014 PHB, plus Tasha's Cauldron, plus Xanathar's Guide, plus the 2024 PHB definition of a warlock into one character and then that person begins to whine when the combination of parts do not play well together.
That's very much an individual issue. Whoever's the DM needs to put a foot down on that one. As for the Death Knight, yeah, you got the right answer already. WoW classes aren't going to be renamed just because there's also a monster by that name.
There's a few monsters with names of classes or subclasses in base D&D as well, not just a crossover issue. (Bard, Druid, and all 8 base Wizard classes are examples.)
True, so true. When I create a character, I try to remain within the bounds of the 2024 PHB because I know that some of the 2014 rules are incompatible with the 2024 rules and I want to minimize any procedural snarls. Nothing blows a game session apart faster than a dispute over which rule takes precedence.