Most GMs who put a vampire, a grave-fae or a revenant in front of a player who wants them end up running one of two scenes. Either the creature is a trap, and the player learns the price after the kiss. Or the GM loses nerve, and the candle goes out before anyone has chosen anything. There is a third way, and it begins with the creature opening its mouth.

You have run this scene. The player leans in. The thing across the table from their character is beautiful and wrong, and it plainly wants them back. You now have about four seconds to decide what kind of scene this is. If the creature is dangerous, the price (a bite, a year, a soul) lands after the fact, and the player feels ambushed. If the creature is safe, there is no story, and you cut to morning with relief.

Neither version hands the player a decision worth making. That is the frustration. Monster romance is the oldest genre at the table, older than dungeons, and it keeps collapsing into a saving throw or a fade.


Why the seduction scene turns into a trap

The cause is simple once you see it. In most monster scenes, the creature's desire is hidden. The vampire wants blood and says "come closer". The fae wants a name and offers a dance. The reveal is the horror beat, and the genre has trained us to protect it.

But a hidden want makes consent impossible, in the fiction and at the table. The character cannot agree to a cost they cannot see, so whatever the player decides, they decided it on false information. When the price finally lands, the player does not feel seduced. They feel cheated, and they are right.

The usual tool makes it worse. "Roll to resist her charm" turns a choice into a die result. On a failure the player chose nothing; on a success the scene is over. Either way, the one person whose desire should drive the scene has been written out of it.

The early fade has the same flaw in a kinder coat. I have written before about how fading to black too soon also fades out the player's agency. With a monster, it fades out the monster too. You never find out what it wanted, and so neither does your player.


The pact: a creature that names its price

The fix I now use for every uncanny partner fits in one sentence: nothing takes what it is not given. The creature says what it wants, aloud, in its own voice, before it touches anyone. Everything else in this method follows from that sentence.

I will walk it through with one creature doing all the work. He is roll 00 of a book I just finished, and he is already on the shop listing, so I am not spoiling anything you cannot read for free.

A wet copper spins on the cobbles at your feet, then another, out of the sealed well. A grey hand comes over the lip, and a man hauls himself onto the stone in a coachman's coat that streams water and never stops. His lips are a drowned man's blue. He watches the yard gate like a clock.

The man is Absalom Tunnicliffe, a drowned coachman. Thirty years old when the well took him, he smells of horse and lamp-oil under the green, and he never lets go of the rim. What he wants is word of the passenger he waited for, and whether they ever asked after him.

1. The price is spoken first, and it is specific

Here is his pact, in his voice:

"Meet the coaches for me. Every Hallowtide, stand in this yard and ask each one for my passenger, in my name, as long as you live."

In return, he will dive for everything the well ever took from you.

Notice the shape of the price. Neither "your soul" nor "a favour, to be named later": a habit the character will carry for the rest of their life: one night a year, in one coaching yard, asking strangers a dead man's question. A good price is concrete enough that the player can picture their character paying it at sixty.

Three tests before the scene. Can it be paid? Will the character still feel it in a year? Would the creature say it in those words? If the price fails the third test, it is your price, not the creature's, and the player will hear the difference.

Two more, so you can see the range. A yew on the churchyard walk asks for one season of your sleep. A reflection in the Mirror Hall steps out of the glass and asks to finish its last dance. Each kind of creature takes a different kind of thing. The returned dead take a promise kept in their name; the thirsting take a chosen vein; the things at the crossroads take a clause. Deciding what your kind of monster takes is half the design, and you only have to decide it once per kind.

2. The pact buys a favour, not the scene

This is the step most GMs skip, and it is the one that makes the scene safe to run. Agreeing to the price does not buy the creature a night. It buys the favour. Whether anything more happens is a second question, and the creature asks it, in its own voice. Then you ask it again, as yourself, across the table.

Separating the two questions saves you from the oldest problem in the genre: sex as the price. When intimacy is the currency, a refusal costs the character the favour, and that is coercion with a dice pool. When intimacy is its own yes, it can be wanted, which is the only state in which it is worth playing.

At the table it sounds like this. In the creature's voice: "You could stay a while. You need not." Then out of the voice, to the player: "Do you want to play it, or move to morning?" A no to that second question ends the scene with the pact intact, and the creature accepts the no. Absalom nods, and goes on watching the gate.

3. Four endings, and refusal is one of them

Every pact I write gets four branches, written before the session: the character accepts and stays; pays and leaves; bargains; or refuses. The discipline is that all four are real outcomes with a scene in them, not three outcomes and a wall.

Absalom's bargain goes like this. The character offers to find the passenger instead: two bells of asking at the coaching inn and a bribe to the ostler. He carries the name down like a stone in his mouth, and the coins stop rising, your lost things with them. The counter-offer is where the player gets to be clever, so give it a real alternative with a cost of its own. Cheaper, and you lose the favour.

His refusal is shorter. He nods, as at a fare who changed their mind, and goes back over the rim. Far down the shaft, a coach horn sounds once, for a passenger who never came.

That is a complete ending. Nobody was punished. Something happened, and the table will remember the horn. Write the refuse branch first. If it comes out thin, your pact is a trap in disguise, and you have found out before the players did.

4. What the price leaves behind

A price paid in full has to show up later, or it was never a price. Think of it as a mark on the character's life rather than a curse or a penalty on the sheet. Give it one visible sign and one date. Absalom's character stands in a coaching yard every Hallowtide, and that is a scene you get to run next year, with a player who has been dreading and wanting it for twelve sessions.

This is also where the explicit question answers itself. Whatever your table's register, the accept branch can be read in full or skipped to this line, what the price left behind. The scene survives the skip. The pact was the scene.

5. World, sign, aftermath

The last three lines of a pact are not about the player at all. They are yours. A custom of the place: Wayfare seals a well when someone drowns in it and never fills it in, and a sealed well, the inns say, lets its dead out yearly. A sign that the creature is near, so the table can feel it coming: wet coppers on dry cobbles, lamp-oil under green water. And what the night leaves behind in the city after the characters have gone.

The custom lets you plant the creature a session early. The sign lets a player who is paying attention see the monster before it speaks, and that is the moment they decide whether to stay in the yard. The aftermath is how the city shows it noticed.


Running it at your table

Session-zero the register before anything else: how explicit the accept branches may be, lines and veils, and a visible X-card. The pact method does not replace those tools. It handles the far more common case where nobody wants to stop and everyone wants to know the cost.

Write the pact and the four branches on an index card before you sit down. Read the price aloud in the voice, then fall silent. Do not fill the silence; the silence is the scene. When the player answers, ask the second question as yourself. Honor a skip the moment it comes, no reason owed.

And roll once before you decide anything. The creature your table gets should surprise you too.


Where this comes from

Writing one of these takes an evening: a creature with a past, a price in its own voice, four endings that each hold up, a sign and an aftermath. Writing a hundred took me a season, and most of it went into the refuse branches.

If you would rather roll than write, Monstrous Desires is a hundred of them. Ten families of the uncanny, each with its own kind of price, from the returned dead to the things in the deep. A haunted gazetteer of twelve places. Five chains that thread three nights together and still work as single rolls. System-neutral, no stat blocks, one encounter to a page, set in Velnaris at Hallowtide and at home in any dark-fantasy city. The accept branches are explicit and the book is 18+; everything else on the page reads exactly like Absalom above, with the fade always offered.


Monstrous Desires: 100 Encounters for Dark Fantasy Cities is on the store now, at half price through Halloween.


Tags: Tabletop RPG · Game Master Tips · Monster Romance · Dark Fantasy · Halloween


Lorenza Nevada is the writer and designer behind Fantasy Vixens, a dark fantasy TTRPG imprint. Her books are on DriveThruRPG, and three of them are free.