I'm currently sitting on the backstory for my upcoming character. I summarize the most important and then I come to the point where I would be very happy about a few ideas and suggestions from you ;)
Race: Elf or Half-Elf - Who dreams of becoming a famous Bladesinger.
He finds a weapon that promises to grant him his wishes. In exchange, he must enter into the contract with his blood on the blade.
In this case, he enters into the contract with Baphomet, who imposes on him a contract, if he does not abide by it, that he will turn him into a Minotaur piece by piece until his race changes completely.
The disillusionment of this agreement shows that he gets quite similar skills, but actually not what he wanted for a very high price.
As an example: Hexblade´s Curse as Bladesong.
And now I'm sitting on the part for the contract. The class features are supposed to be part of the benefits the character gets. What's more of a headache for me is how to word the part that says if you don't do this, for example, a body part or another body part will transform.
So far the only thing I could think of is the enmity to the gnolls. If you see one, you have to get rid of it.
I hope the concept behind this is understandable and I've given you some ideas on how you would approach this.
Thank you very much for reading and your suggestions.
So this reads a little overdetermined for a back story. First off, I'd get with your DM to see how they want to handle your patron. Your pushing mechanical consequences on yourself, and maybe your DM would be fine with that, or maybe they'd have something more their style than transforming your race or making you an NPC.
One thing to keep in mind, Warlock's don't have "contracts" they make "pacts." Pacts and contracts are roughly synonymous, but a pact is generally more in line with a "hand shake deal" or "bargain" a sort of "you scratch my back and I scratch yours thing." When there's a breach, since there's not contract with violation clauses, the offended party doesn't have much more recourse than the express their displeasure through grievances. In other words, Baphomet grants you Hexblade powers with the expectation that you perform services for it, maybe as an assassin, guess starring roles in the Blood War, collector of debts and grievances.... If you violate it, there's no RAW meting out consequences* and it should be more how the DM will play it than you as player punishing the character. Frankly if I was Baphomet and I had Hexblades and you were stepping out of line with my expectations, I send another of my Hexblades to you with the message to get back in line. Why would I make my problem child, really my problem business associate, into one of my minotaurs if you'd just keep being my problem child?
I also wonder if you're laying this out because you want your character to be punished by Baphomet and go through this transformation. That's forcing the DMs hand in some ways and as a DM I wouldn't appreciate it. So again, the best thing to do before you commit this back story is ask your DM how a Warlock patronage to a Demon Lord would work. If I was your DM and you can to me with your story I'd say something like "it's a cool idea and I like how you're incorporating some of the lore association of Baphomet with minotaurs, and I'll keep that in mind, but really for the sake of my game, your character has pact with Baphomet. I'll let you know what Baphomet expects of you as the game progresses, and if you fall out of favor with the Demon Lord, I'll handle the consequences. But I like the character taking Hexblade because of blade singer ambition, sort of the path of Sith of the Dark Side being "quicker, more seductive" than the Jedi path with the Force. We might be able to play with that in a multi class build further down the line."
I just don't accept backstories where certain things "have to happen" to a character because of background. More often than not the character is made without really seeing the full map, so why insist on a destination? There may be cooler and more fulfilling to the game ways this pact could play out.
*There used to be mechanical sanctions for when a DM ruled a PC going out of character, Palladins had the heaviest burden bound to their piety code or what have you with their "extreme Lawful Good" expecatations. Maybe challenged by or at least run up to with the Cavalier's code in AD&D. 5e just doesn't have that. There are rules for "contracts" and deals in regards Devils, and I think Demons, in the sourcebooks, but that's something that occurs in game, and has the DM representing the other side of the deal. If your character is predicated on being from a pact you want addressed in game, that's something for you and your DM to ultimately work out as whatever your DM rules or accepts overrides any perspective you're soliciting here. I like the idea though, just need to give the DM more space to arbitrate consequences, if any, of the pact.
Thanks for your great feedback. Many of your points are currently also giving me a headache. :D
I presented the idea to my DM and he thinks it's good so far. We will sit down again and discuss everything, but until then I want to refine the whole thing a bit.
After your feedback I tend to describe the character like a "normal" elf, with one or 2 features that remind of a minotaur. Maybe small horns on the forehead or a more massive build which is not typical for an elf.
Now of course the exciting question, how could such a pact look like? - Do you exchange humanity for powers? (In return, you grow horns or hooves?) - Does the patron want to further weaken his enemy Yeenoghu and expects you to kill gnolls for him in return?
How could such a pact look like for you?
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Hello all,
I'm currently sitting on the backstory for my upcoming character. I summarize the most important and then I come to the point where I would be very happy about a few ideas and suggestions from you ;)
Race: Elf or Half-Elf - Who dreams of becoming a famous Bladesinger.
He finds a weapon that promises to grant him his wishes. In exchange, he must enter into the contract with his blood on the blade.
In this case, he enters into the contract with Baphomet, who imposes on him a contract, if he does not abide by it, that he will turn him into a Minotaur piece by piece until his race changes completely.
The disillusionment of this agreement shows that he gets quite similar skills, but actually not what he wanted for a very high price.
As an example: Hexblade´s Curse as Bladesong.
And now I'm sitting on the part for the contract.
The class features are supposed to be part of the benefits the character gets.
What's more of a headache for me is how to word the part that says if you don't do this, for example, a body part or another body part will transform.
So far the only thing I could think of is the enmity to the gnolls.
If you see one, you have to get rid of it.
I hope the concept behind this is understandable and I've given you some ideas on how you would approach this.
Thank you very much for reading and your suggestions.
So this reads a little overdetermined for a back story. First off, I'd get with your DM to see how they want to handle your patron. Your pushing mechanical consequences on yourself, and maybe your DM would be fine with that, or maybe they'd have something more their style than transforming your race or making you an NPC.
One thing to keep in mind, Warlock's don't have "contracts" they make "pacts." Pacts and contracts are roughly synonymous, but a pact is generally more in line with a "hand shake deal" or "bargain" a sort of "you scratch my back and I scratch yours thing." When there's a breach, since there's not contract with violation clauses, the offended party doesn't have much more recourse than the express their displeasure through grievances. In other words, Baphomet grants you Hexblade powers with the expectation that you perform services for it, maybe as an assassin, guess starring roles in the Blood War, collector of debts and grievances.... If you violate it, there's no RAW meting out consequences* and it should be more how the DM will play it than you as player punishing the character. Frankly if I was Baphomet and I had Hexblades and you were stepping out of line with my expectations, I send another of my Hexblades to you with the message to get back in line. Why would I make my problem child, really my problem business associate, into one of my minotaurs if you'd just keep being my problem child?
I also wonder if you're laying this out because you want your character to be punished by Baphomet and go through this transformation. That's forcing the DMs hand in some ways and as a DM I wouldn't appreciate it. So again, the best thing to do before you commit this back story is ask your DM how a Warlock patronage to a Demon Lord would work. If I was your DM and you can to me with your story I'd say something like "it's a cool idea and I like how you're incorporating some of the lore association of Baphomet with minotaurs, and I'll keep that in mind, but really for the sake of my game, your character has pact with Baphomet. I'll let you know what Baphomet expects of you as the game progresses, and if you fall out of favor with the Demon Lord, I'll handle the consequences. But I like the character taking Hexblade because of blade singer ambition, sort of the path of Sith of the Dark Side being "quicker, more seductive" than the Jedi path with the Force. We might be able to play with that in a multi class build further down the line."
I just don't accept backstories where certain things "have to happen" to a character because of background. More often than not the character is made without really seeing the full map, so why insist on a destination? There may be cooler and more fulfilling to the game ways this pact could play out.
*There used to be mechanical sanctions for when a DM ruled a PC going out of character, Palladins had the heaviest burden bound to their piety code or what have you with their "extreme Lawful Good" expecatations. Maybe challenged by or at least run up to with the Cavalier's code in AD&D. 5e just doesn't have that. There are rules for "contracts" and deals in regards Devils, and I think Demons, in the sourcebooks, but that's something that occurs in game, and has the DM representing the other side of the deal. If your character is predicated on being from a pact you want addressed in game, that's something for you and your DM to ultimately work out as whatever your DM rules or accepts overrides any perspective you're soliciting here. I like the idea though, just need to give the DM more space to arbitrate consequences, if any, of the pact.
Jander Sunstar is the thinking person's Drizzt, fight me.
Thanks for your great feedback. Many of your points are currently also giving me a headache. :D
I presented the idea to my DM and he thinks it's good so far. We will sit down again and discuss everything, but until then I want to refine the whole thing a bit.
After your feedback I tend to describe the character like a "normal" elf, with one or 2 features that remind of a minotaur. Maybe small horns on the forehead or a more massive build which is not typical for an elf.
Now of course the exciting question, how could such a pact look like?
- Do you exchange humanity for powers? (In return, you grow horns or hooves?)
- Does the patron want to further weaken his enemy Yeenoghu and expects you to kill gnolls for him in return?
How could such a pact look like for you?