![]() The example I gave before was a good aligned undead with a Paladin with Oath vs Undead. ![]() What happens when a Paladin's Oath goes against her Code of Conduct? Ok so a lot of people are to distracted by the contrived scenerio in the other thread so this is for a much more focused core discussion. If Sue stumbles upon a good-aligned ghost in some abandoned ruin and decides to send the ghost to its rightful rest, then, in my world, Sue's status is fine. ![]() For example, if Zorge the Good Lich is a living lock on the Gates of Hell, and this is widely known, then Sue the Oathbound Paladin should leave him be (or quest to find a way to transfer the lock onto another object and then send him to his rightful rest). In my world, an Oath against Undead wouldn't fall for killing a good aligned undead as long as she ensured that no fallout would cause innocents undue suffering. returns to her demon form just before the paladin walks in and has suffered so many negative levels that one hit from a smite charged weapon kills her). The problem that I have with the contrived scenario is that it's ridiculously contrived to trap the hypothetical paladin (I mean. Paladins sworn to an Oath are different from paladins not sworn to an Oath. In my game world, the Oaths alter and supercede the generic paladin code. Make sure your aspiring paladin players know. Do you consider the Oath fluff and it's just a set of alternative abilities? Great. Make sure your aspiring paladin players know at creation. Do you want the Oath to supercede? Great. I can't speak for PFS, but I think that how the paladin code and the oaths interact with each other is something that the GM decides for his world and lets the players know ahead of time.
0 Comments
Leave a Reply. |