![]() I felt it would be unduly punishing if they were forced to pick between one or the other. Note that the name difference is on purpose a dragonborn dragon shaman can use their draconic breath and their breath weapon. The core features give you a “draconic breath” which is identical in concept to the dragonborn’s breath weapon, eventually out-competing it by a bit at lvl 20. There is some overlap here as dragon types are all different, but in the end chromatic dragon shamans tend to be more aggressive with features focused on damage and combat, while metallic dragon shamans have features that help them a bit more with social encounters or beating opponents in ways besides out-right killing them. The skills granted by metallic dragons, by comparison, lean more towards knowledge and passiveness Persuasion, History, and Insight. The skills, for example, granted by chromatic dragons tend to be more aggressive, like Intimidation, Athletics, and Deception. The features the two subclasses do share still highlight the differences between dragon types and chromatic and metallic dragons. Chromatic dragon shamans, by comparison, get features which highlight the aggressive and violent natures of chromatic dragons, such as a Frightful Presence, and the ability to reset their breath weapon when they reach 50% HP (something inspired by 4e monster mechanics). Metallic dragon shamans, therefore, get similar features. This made it much easier to distinguish between the two, as metallic dragons already have built-in similarities they all get some kind of second breath weapon, and they can all transform into other creatures. When I considered that, I realized that I could probably reduce the number of subclasses to 2, one for chromatic dragons and one for metallic dragons. But that resulted in a lot of bloat, and I had difficulty figuring out proper features for each dragon type that justified the many subclasses. So when you hit the appropriate level, you’d chose red dragon, or silver dragon, or copper dragon, or blue dragon, or whatever, the same way a paladin chooses their oath or a wizard chooses their arcane tradition. For a time, I made every kind of totem dragon its own subclass. Most (read: all) of that difficulty came from designing proper subclasses for the dragon shaman class. I found that same difficulty on this attempt. ![]() Originally, I had a lot of difficulty with the full-class attempt (which is the reason why I started looking at subclasses). All of that is difficult to put into a subclass (I might have seen better results with a paladin subclass, but even then I think a full class is necessary to really make the dragon shaman shine). The dragon shaman was always this cool mix of tank, party face, “okay” damage, and light healer. ![]() The dragon shaman is such a cool class from 3.5e, it deserves to be more than just a subclass, losing much of what made it interesting and different. I know what you’re thinking “But Jeff, you already have a homebrew about the dragon shaman. Check the changelog below for the full list of alterations. Now updated with the Gem Totem Dragon after the release of Fizban’s Treasury of Dragons.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |