Hello and welcome back to RPG PhD.

I'm Dr. Ben.

Today's lecture gets at something fundamental about what separates

a session people remember from a session people merely attended.

We're talking about dramatic tension curves and rhythmic pacing,

specifically how to use both to take intentional control of your sessions.

Narrative flow.

The principles we're working with today come from the theatrical theory,

narrative science, and psychology.

People have been studying why certain experiences grip us and others

don't for a very long time, and that research has real,

practical applications behind the game master screen.

So let's get into it.

Let's start by building a shared vocabulary, because tension is

one of those words that gets thrown around a lot in game master advice,

without anyone stopping to define it precisely.

Tension is the felt experience of unresolved expectation.

It lives in the gap between what players want and what they have,

between what they fear and what hasn't happened yet.

It's the space between a question being asked and a question being answered.

Danger and conflict can create it, but neither is tension itself.

In plenty of dangerous conflict, field sessions produced almost none of it

because the outcomes feel inevitable.

Tension requires genuine uncertainty and requires the possibility

that things could go either way, and that the difference between

those two outcomes actually matters to the people at the table.

That gap, that space of unresolved possibility

is one really important engine of engagement.

In 1863, a German

playwright named Gustav Freitag

mapped dramatic structure as a pyramid exposition at the base,

rising action climbing toward

a climax at the peak, then falling action descending to resolution.

You've seen this diagram every high school English class has drawn it

on a white board.

At some point, Richard was describing something real, but his model

has a problem for our purposes, and it's a significant one.

It assumes a single author controlling a single linear narrative.

That's a play or a novel that is emphatically not a tabletop

roleplaying game session, where five people at the table

can collectively detonate your carefully planned act two in the first 40 minutes

because someone had an idea.

So Fritz, Pyramid is our starting point rather than our destination.

What I want you to picture instead is something more flexible.

Imagine a simple graph.

The horizontal axis is time measured in scenes.

The vertical axis is emotional intensity running from

zero at the bottom to ten at the top.

Zero is complete.

Rest.

Players are in town recovering, having a quiet conversation over a fire.

Ten is maximum stakes.

Someone is about to die.

A terrible choice has to be made.

The room has gone completely silent.

Plot your session on that graph and it makes a shape, a line that rises

and falls, peaks and valleys across the runtime of your evening.

That shape is what we're designing today.

Psychologist Barbara Fredrickson and Daniel Kahneman

identified something they called the peak end rule.

Through extensive research, they found that

people don't judge an experience by its average quality.

Memory reconstructs the whole from two specific moments

the most emotionally intense point and how it ended.

Everything in between carries far less weight than we assume.

It does.

Everything in between is largely reconstructed from those two anchors,

so think about what that means for your sessions.

A three hour session

with one genuinely devastating, perfectly placed climax and a resonant

ending will have more of a chance of being remembered as a great session.

A three hour session of consistent, competent, medium

intensity encounters might be remembered as fine.

Not bad, just fine.

Narrative theorist

Roland Barthes, in his analysis of how stories generate engagement,

identified five narrative codes operating simultaneously in any text.

Two of them are directly useful here

the hermeneutic code, the engine of suspense built from an open question.

The reader, or in our case, the player desperately wants answered,

and the erotic code, the code of actions where things happen and they're happening

generates forward momentum through the story.

Barthes was working as a literary theorist, but the pattern

he identified connects directly to something behavioral economist

George Loewenstein documented empirically in 1994.

Loewenstein described curiosity as a state of cognitive deprivation

arising from the gap between what we know and what we want to know.

That gap generates genuine discomfort,

and the discomfort motivates resolution.

Research since then has found that curiosity activates the same dopamine

pathways in the brain that respond to food and other biological rewards.

A scene that

opens a question and lays its answer is pulling on a drive

that runs considerably deeper than narrative convention.

Hitchcock understood this intuitively long before the neuroscience caught up,

he drew a distinction between surprise and suspense

that is worth quoting almost exactly.

Surprise is a bomb under the table explodes without warning,

and you get 15 seconds of shock and suspense is the audience knows

the bomb is there, the characters don't, and the conversation continues,

and you get 15 minutes of unbearable tension from the same bomb.

The bomb is low in Stein's information gap, made physical.

The conversation that continues over it is the delay that transforms

a single shock into sustained biological,

almost involuntary engagement.

Your attention curve is a map

of how you manage those questions across a session.

When you ask them how long you hold them open, when you answer them, and crucially,

how you make sure a new question opens the moment an old one closes

a session that closes

every question cleanly and opens no new ones can go flat.

A session that opens questions and never answers them can become frustrating.

The craft is in the rhythm between those two states.

Before we start building good tension

curves, we need to be honest about what breaks them.

Because the two most common session pacing failures are both completely

understandable, both incredibly common, and have both solid

theoretical explanations for why they don't work.

The first is the flat line.

A flat line session lives between a four

and a six on the intensity scale for its entire runtime.

Encounters happen, but none of them feel urgent.

NPCs appear, but none feel genuinely threatening.

Revelations land, but none land very hard.

Players are present and engaged in a surface sense, but they're not invested.

The session is competent,

and two weeks later, nobody can quite remember what happened.

This is the most common pacing failure that I see,

and it comes from a completely human place.

Game masters want their players to have fun,

so sometimes they smooth off the rough edges.

They soften danger to avoid frustration.

They resolve conflict quickly to keep things moving.

They avoid the scenes that might make players

uncomfortable because discomfort can feel like failure.

At some tables,

the result is a session where nothing genuinely hurts,

and as a direct consequence, nothing genuinely soars.

Chuck sent me high ease flow model gives us a useful frame for why this fails.

He described optimal engagement as a channel balanced between two states

boredom, which occurs when challenge falls below the player's

skill and investment level, and anxiety, which occurs when it exceeds it.

The flatline session sits permanently in boredom territory.

Players are capable of more emotional engagement than the session

is asking of them, so their minds begin to wander the caring is there.

The session just has no where to put it.

There's also something Barthes would recognize here.

A flat line session is one where the hermeneutic code never fully

activates.

Questions are asked softly and answered quickly.

Nothing stays open long enough to generate genuine suspense.

The engine of engagement never turns over.

The second is the red line.

The red line session is the flat line's

mirror image, and it's equally destructive in a less obvious way.

Everything is urgent.

Every NPC is a potential threat.

Every room might be an ambush.

Stakes are always maximum.

The Game Master has absorbed the advice that tension is good

and has applied it everywhere, all the time without relief.

What happens to players in a red line session?

They go numb.

It's basic physiology.

Walter Cannon's foundational research on the fight or flight response identified

how the sympathetic nervous system mobilizes the body under threat.

Adrenaline surges, arousal spikes.

The system prepares for action.

What cannon also understood is that this response is designed

for acute threat rather than sustained exposure.

Later stress physiology research confirmed what follows.

When the signal runs continuously, the nervous system habituate.

It stops responding to the threat.

Because the threat has become ambient noise.

This might be why players start making jokes during your three hour climax.

It's their nervous systems calling for an exhale.

You haven't given them all evening.

They're self-regulating because the session isn't doing it for them.

The Yerkes Dodson framework, developed in 1908, gives us a useful model

for why this matters. For performance.

Moderate arousal produces peak cognitive and emotional engagement.

Push past that point and performance degrades a relationship researchers

have since observed across a wide range of tasks and contexts.

Flat lines fail on one side of that curve, red lines fail on the other.

Here's the cruelest part of the red line problem your actual climax.

The moment you've built toward the scene that should be the emotional

peak of the evening arrives when players have nothing left.

They've been

spending emotional bandwidth since sessions start.

By the time you need them fully present, fully invested and fully feeling it.

The tank is empty.

The climax was well designed, it was just positioned

wrong and positioning is everything.

Kahneman's peak in rule cuts both ways.

Yes, a genuine peak moment defines the session's memory,

but if the entire session is at peak intensity, there is no peak.

There's just a flat line at the top of the scale instead of the middle.

So we've established that sessions have a shape,

and we've named two ways that shape goes wrong.

Now let's look at a way that might feel better at the table.

Here is the principle that ties everything together,

and I want you to sit with it before we complicate it at all

sessions.

Breathe.

That's the whole model sessions.

Inhale, tension rises and they exhale.

Tension releases.

Your job is a game master is to control the breath, know

when to push and when to pull back.

The exhale is doing real work every moment it's present because without it,

the next inhale has nowhere to build from.

This comes from a place deeper than role playing game theory.

Leonard Mayer, in his landmark work Emotion and Meaning in Music, argued

that musical emotion is generated

almost entirely by the creation and violation of expectations.

Tension in music arises when an expected resolution is delayed.

Release comes when it finally arrives.

The emotional power

of a piece of music lives in the relationship between its tension

and its resolution and, crucially, in the timing of that relationship.

Psychologist David Sheeran built on Meyer's work and identified what he called

the it prey cycle imagination,

tension prediction, reaction appraisal, the full psychological

arc of an anticipated event before an outcome arrives.

We imagined possible futures in field tension.

As uncertainty builds.

Once it arrives,

we experience an immediate response to whether our prediction was accurate,

then a fast, instinctive reaction to the outcome itself,

and finally a slower appraisal of what it meant.

Two phases, everything before the moment of resolution and everything after it.

The heartbeat model is how you design it

intentionally, and it works on two layers.

Layer one is the beat cycle.

Nearly every scene in your session moves through four phases.

You can think of them as action, consequence, reflection, and anticipation.

Action is the scene happening, the fight, the negotiation,

the revelation, the discovery.

Something occurs.

This is the part

game masters are generally good at because it's the most visible part.

It's the content.

Consequence is the immediate aftermath.

What changed? What was lost or gained?

Who is different now than they were before the scene began?

This phase is critical, and it's one that some game

masters skip, usually due to wanting to keep momentum moving.

The scene ends and the instinct is to cut immediately

to the next thing, but resist that instinct.

The consequence phase is where the action can acquire meaning.

Reflection is the emotional processing beat.

This is where characters and by extension players respond to what just happened.

A brief conversation around a body, a moment of silence after a revelation,

a character staring at their hands after a difficult choice.

This doesn't need to be long.

30s of genuine emotional space

does more work than five minutes of filler dialog.

What you're doing in the reflection phase is inviting players

to feel something rather than just react to something.

Stanislavski, the Great theatrical director, built his entire rehearsal

method around what he called units and objectives

the idea that every beat of a scene has an intention

and a scene ends when that intention is achieved or blocked.

The reflection phase is Stanislavski denouement.

For the individual scene, it completes the unit.

It tells the players brains that this experience is finished

and processed before the next one begins.

Anticipation is the transition forward a hint, a threat, and unanswered question.

A door that just opened an NPC's parting warning.

This is your inhale.

Tension begins to build again.

The next scene has been seated before it starts,

when you cycle through all four phases before cutting to the next scene.

Players can experience the session as a sequence of complete

emotional events, rather than a list of things that occurred.

The session gains texture

because the cycle gave them somewhere to put their feelings.

Layer two scene types is instrument.

The beat cycle governs how individual scenes breathe.

This second layer governs how scenes relate to each other,

and it's where the compositional thinking really opens up.

Think of your scene types as instruments in an orchestra.

You might have combat, role play, exploration, mystery, and rest.

Each has a natural tension range.

Combat might sit between a six and a nine, is physically urgent,

mechanically immediate, with stakes that are visible and legible

even when the party is unlikely to lose.

Combat communicates danger through its structure.

Role play might range

from a two to an eight, depending on its emotional content.

A casual tavern scene is a two.

A confrontation with a dying mentor is an eight.

The range is wide, which makes role play your most versatile instrument.

Exploration tends maybe toward a 3 to 5 curiosity

and discovery, the pleasure of the unknown,

but without the immediate pressure of physical danger.

It's a clarinet to combat brass section, lighter, more agile,

capable of carrying melody without demanding attention.

Mystery is interesting because it builds.

It might enter a scene at a three and creep toward a seven as clues

accumulate in implications. Sharpen

mystery is the instrument that rewards patience.

It needs room to develop.

Rest. Genuine rest.

True downtime lives at a 0 to 2

players recovering characters in safety, the world going quiet for a moment.

This is the instrument some game masters are afraid to play.

So here's the

compositional principle that binds all of this together.

You don't play the same instrument for the entire session.

The power of an orchestra comes from the relationship

between its instruments, the quiet passage that makes the brass entry devastating,

the held note before the crescendo that gives it space to land.

The silence, actual silence that makes what follows

it feel enormous.

Your session works the same way.

A combat encounter that arrives after 30 minutes of building mystery hits

differently than a combat encounter in the opening five minutes,

a quiet role play scene after a brutal fight might do more

emotional work than a post combat narration.

An unhurried exploration sequence between two major

confrontations is structural preparation.

It's the valley that makes the next peak possible.

This is

Myers principle, applied directly to session design.

The emotional power of your peak is relational.

It comes from what surrounds them.

You are designing scenes, yes, and you are equally

designing the spaces between them.

You are designing contrast and contrast,

handled with intention is a fantastic tool for the game master.

One final note on rare, specifically because it's the instrument

that some GM's most consistently under use

genuine rest beats moments where nothing is threatening,

where players can breathe and characters can exist without urgency,

are active structural components doing essential work.

They are widening the valley and as we have established earlier,

the depth of your valley directly determines the height your next peak

can reach.

When I studied theatrical lighting design, one thing that I found

really interesting was a technique we use for climactic moments on stage.

So let's say you needed a

light cue to hit as bright as possible at the peak of a scene.

Maximum intensity, full power.

The moment lands and the audience feels it.

Simple enough.

Except what do you do when the lights are already at full?

You've been building all scene and now you're at 100%.

There's no where to go.

The solution is counterintuitive,

but you start by dropping the intensity to, say, 80%.

But so gradually that nobody in the audience consciously registers it

a few percent over 30s slow enough that it isn't noticeable.

And then at the climactic moment, you push the lights back to full,

the audience experiences the lights getting brighter

than they appeared to be before, but they didn't.

They just return to where they already were.

But the brief, imperceptible dip gave their eyes a new baseline,

and from that baseline, full power reads as something even brighter

than what was experienced earlier.

Your sessions work the same way.

The valley is the slow dim.

The peak is the return to full.

Don't fill your rest beats. Protect them.

Let them be genuinely low.

Let your players feel safe for a moment.

So based on the theories that we have examined

so far, let's build a practical and malleable session shape.

We will start with the three peak session structure.

So I want to introduce a default architecture for a standard 3

to 4 hour session.

I want to be clear upfront this is a skeleton.

This is not a formula.

Its purpose is to give you a starting shape.

You can bend, compress, or expand based on

what your specific session needs.

It's not meant to be a rigid prescription.

Some sessions want to peak, some want for.

The point is that you're making that decision deliberately rather

than discovering the shape of your session after the fact.

So here's the skeleton.

Pick one the question.

This lands within the first 30 minutes and sits around

a 6 or 7 on the intensity scale.

Its job is singular.

Establish why today matters this session right now.

What is the question this session is going to answer?

And why do the players need to care about that question?

This peak can be a revelation that recontextualizes

everything the players thought they knew in arrival.

That changes the political landscape of the scene.

An NPC in crisis who needs help immediately.

An emergency that overrides whatever the players plan to do.

The content is flexible.

The function is fixed, create urgent, legible stakes quickly,

and leave a thread of unresolved consequence that players can pull on

pacing wise question peak should be punchy.

Escalate faster.

Cut before the scene overstays.

You're trying to open a question that demands an answer.

Peak two A complication.

This lands roughly at the session's midpoint

and escalates to around a 7 or 8.

The complications job is to take whatever progress players

made in the first half and make it cost something.

A plan that was working hits an obstacle.

An ally is revealed to be compromised or simply wrong.

A choice is force that players would rather not make.

The world pushes back.

The complication is where your session earns some emotional weight,

because it's where consequences become personal.

The first peak establish stakes.

The complication makes those stakes specific to the player's decisions.

It says.

You've made choices, and those choices had a shape.

And here is what that shape looks like now between peak two and three

do you might want your deepest valley, your genuine exhale and exploration

sequence, a role play beat, a moment of rest

where the immediate pressure has lifted and players can reflect

on what just happened and anticipate what might be coming.

This valley is structural preparation.

It's the silence before the crescendo.

Protect it with the same intentionality

you bring to your peaks.

Peak three is the crescendo,

your session ending crescendo, landing in the final 30

to 45 minutes at a nine, or when everything has aligned a ten.

This is the payoff for every tension beat that preceded it, and it carries

one essential design requirement it must be earned.

Kahneman's peak in rule tells us this is the moment

that will define how players remember the entire session.

Then everything else is context for this, which means peak three needs to arrive

when players are emotionally present and personally invested in the outcome.

Earned climaxes are specific.

They resolve questions.

This party opened about these characters in this story.

They call something real, and they leave players feeling the particular

exhaustion of having genuinely mattered.

After peak three, you want a brief denouement.

The consequence and reflection

phases of the beat cycle applied to the session as a whole.

Let the table process before you call time.

So let's talk about building your map.

Here's the practical process.

Before your next session, take a few minutes and do this.

Draw the graph.

Horizontal axis scene's roughly estimated vertical axis intensity 0 to 10.

Mark your three peaks.

Put your hook in the first quarter.

Put your compensation at the midpoint, but your climax in the final quarter.

Now draw your valleys between the hook

and your opening mark 1 or 2

the session needs to establish before it escalates between peak two and peak three.

Draw your deepest valley a genuine 0 or 1 you're protected.

Rest beat a brief mid-level rise, a 4 or 5.

As tension builds toward the climax.

Look at the shape you've drawn.

That's your session's emotional architecture.

It doesn't tell you what happens.

It tells you what order things happen in and how much space to give each thing.

When players deviate and they will, you're not trying to force them

back onto the line.

You're trying to restore the shape.

If the hook landed too hard and you're

in an eight by minute 20, you need a valley faster than planned.

If the compensation deflated and you're at a four when you need a seven,

you have a mechanical or narrative lever to pull.

The map is your reference.

The session is always live.

That's the practice.

It takes five minutes in prep

and it changes the entire felt experience of your session.

So let's talk about endings.

We're going to get resolution versus cliffhanger.

How you into session is per common half of how that session will be remembered.

So this deserves some precise thinking.

A resolution ending completes the session.

Central question players receive the consequence and reflection beats in full.

There is closure of tonight's specific question.

These endings feel satisfying and complete.

They honor the work the players did.

They send people home with a sense of accomplishment rather than of urgency.

So use resolution endings when players are emotionally tired,

when the session has been particularly heavy, or high stakes,

when a character has accomplished something significant

that deserves to land fully before the next thing begins.

When you want to create a genuine chapter, break in the campaign's rhythm,

a cliffhanger ending cuts at or immediately

after a moment of peak tension or major revelation.

It deliberately withholds the reflection phase.

It creates a sensation of incompleteness that makes players

think about your campaign between sessions.

Use cliffhanger endings when you want to maintain

campaign momentum across a sequence of sessions.

When you've just dropped a revelation that needs time to breathe

before it can be processed at the table.

When you want the next session to open with immediate urgency,

rather than requiring a new question to establish the stakes.

One practical note on cliffhangers they work on a per campaign budget

cliffhanger.

Every session might train players to expect incompleteness,

and they might start feeling the urgency.

2 or 3 across the campaign aren't placed at genuinely significant moments.

Hit with real force.

Remember, contrast is key.

So let's talk about reading the Room.

Everything we've built so far lives in your prep notes, the tension map, the peak

placements, the protected valleys, the deliberate sequencing of scene types

that work is real.

And of course it matters. Do it.

And then your players sit down and the session goes live

and none of it survives contact with the table exactly as written.

This is not a problem.

This is the nature of the form.

Tabletop role playing games are not theater, where

the script is fixed and the director's job is fidelity to the text.

The closer to jazz you know, the chord changes.

You know the key.

You have a structure you've internalized deeply enough to depart from it,

and then you play with and for the people in the room,

the map is your preparation real time reading is your performance.

So this section is about the live craft, how to read what's actually happening

at your table moment to moment, and how to adjust your attention curve

in real time without breaking the fiction or losing the room.

The table is a feedback system.

Your players are communicating with you constantly

during a session, sometimes with words,

but just as often with their bodies, their energy, their engagement patterns.

Learning to read those

signals is one of the highest level gamemaster skills there is,

and it should be discussed more explicitly.

So here's one description of what genuine engagement might look like.

Players lean forward.

They make eye contact with each other and with you.

They interrupt each other with plans, reactions, theories because

they're excited.

They ask questions that push the fiction forward.

When you describe something, they respond before you finish describing it.

The table has a collective movement that you can feel as much as see.

So here's what a flatline like look might look like in the room.

Players lean back, phones appear, side conversations emerge

that have nothing to do with the session rules.

Questions surfaced

that feel less like genuine confusion and more like bids for engagement.

They want something to engage with

and have run out of content that's gripping them in the game.

Descriptions land in silence.

Players wait to be told what to do rather than generating their own direction.

Or maybe what a red line looks like in the room.

And this one is a little subtler.

Players start deflecting jokes, arrive at moments that don't call for jokes.

Someone proposes an absurd solution to a serious problem, and then the table

laughs harder than the joke.

Warren's characters do things that are slightly out of character,

slightly too casual, slightly unserious.

That last pattern is the one that catches some game masters off guard, most

because it often looks like the players are having fun, and in one sense they are.

Laughter is a genuine pleasure, but it can also be a pressure valve.

When the nervous system has been running hot for too long.

Humor is one way people self-regulate.

The joke might be a sign that tension has been working without relief for too long,

and the table is taking the exhale that you didn't give them.

When you read the room and recognize that the session shape

needs correcting, here are three possible adjustments.

All of them are nearly invisible to players.

When executed well,

they are completely diegetic, and they don't require you to step outside

the fiction. Accelerate.

Use this when the table is flat, when engagement has dropped,

when energy is low, when players are waiting rather than acting.

Acceleration means cut your current scene

shorter than planned and move to the next escalation faster.

Raise the stakes of whatever is currently happening

by introducing an immediate consequence or complication

at a time pressure that wasn't there before.

Something is coming, something is about to change,

and the players have less runway than they thought.

Bringing an NPC

with urgent information or a direct threat

make something that was background become foreground.

The key to acceleration is that it never feels like a gear shift.

You're simply letting the next thing arrive sooner.

A well-placed NPC interruption is a narrative acceleration

in a completely natural story event.

Simultaneously, a sudden complication that raises stakes

is a pacing correction and good fiction.

Simultaneously, players experience the session getting more interesting.

Hold.

Use this when you've just hit a peak and the table needs to process before

moving on when something significant just happened and you can feel

that players have feelings about it that haven't been expressed yet.

When the reflection phase of your beat cycle is being rushed

by the session's momentum and you need to slow down and let it

breathe, holding means linger in the current moment.

Describe slowly and with more sensory detail than usual.

Ask players what the characters are thinking or feeling,

which is an invitation to the reflection phase rather than a demand for action.

Let silence exist at the table without immediately filling it.

Sit with the aftermath of what just happened,

rather than cutting away from it.

The instinct against holding is strong because silence

can feel like an empty space.

A quiet table feels like a dead table.

But there is a qualitative difference between the silence of disengagement,

which is flat and slightly restless, and the silence of genuine

emotional processing, which has weight and presence.

Learn to distinguish them.

The second kind of silence is some of the most valuable time in your session.

Pivot.

Use this when neither accelerating nor holding is working.

When the session has lost its structural footing entirely.

When a scene is run past its natural end and

is consuming time without generating tension.

When players are stuck in a way that isn't dramatically productive.

When you need a structural reset, a pivot introduces a new element

that reorients the scene or transitions the session into new territory.

A new NPC arrives with information that changes the situation.

An environmental event shifts the physical or emotional context.

A revelation reframes what the players thought they were doing.

A threat that was distant becomes immediate.

The pivot is your emergency tool, and like all emergency tools,

it works best when it doesn't look like an emergency.

The NPC who arrives at exactly the right moment

should feel like the story delivering what it always intended to deliver,

rather than a game master throwing a lifeline.

This is where your prep investments pay off.

The more texture and logic your world has, the more naturally a pivot

can arrive from within the fiction rather than appearing to be imposed on it.

Stanislavski called this kind of intervention and offered circumstance

a new.

Given that actors must respond to, as if it were always part of the scene.

Your pivot is an offered circumstance.

When it works, players experience the world being alive and responsive.

Now let's talk about some of the limits of these frameworks.

These frameworks are tools.

And tools, of course, can be misapplied.

The tension map, the three peaks structure, the beat cycle.

All of it comes from disciplines built around audiences,

around people receiving a designed experience

in tabletop role playing games are only partly that.

The other part is something

those disciplines don't fully account for genuine collaborative authorship.

Your players are not an audience, they are co-creators.

And by co-creators, I mean the players are creating story

arcs within the fiction through their characters actions in the world

and there is a version

of applying these frameworks that forgets that distinction entirely.

If you run your session with one eye permanently on the tension graph, chasing

your plan peaks, protecting your valleys, managing your players emotional states

like a theme park engineer managing queue psychology.

You might produce sessions that are technically well shaped

and experientially hollow.

Players feel the difference between a game master who is present with them,

and a game master who is executing a design at them.

Kahneman can tell you what makes an experience memorable.

He cannot tell you what makes it meaningful.

Those are related, but separate questions.

Flow research is genuinely powerful and is also research

conducted largely on individuals and solitary pursuits.

The social and collaborative dimensions of flow.

At a table of five people with different investment levels, different

emotional states, and different ideas about what a good session looks like,

are considerably messier than the model suggests.

Some nights the table needs something the tension curve cannot provide.

Someone had a terrible day.

Two players are in a weird place with each other.

The campaign has hit a point that is personally resonant

for someone in a way that you didn't anticipate on those nights.

The most important game master skill is putting the framework down

and just being present with the people in the room.

Freitag talks pyramid was designed for tragedy.

His model privileges catharsis, which is an Aristotelian

concept rooted in the idea that audiences need emotional purging.

Your players may want something else entirely.

Resolution, yes, catharsis sometimes, but also wonder.

Absurdity.

Intimacy, shared

laughter, the particular pleasure of a plan coming together cleanly.

Not every

session needs to move through darkness to earn its peaks.

The framework can become a bias toward dramatic suffering if you apply it

without asking whether suffering is what your table actually needs right now.

And finally, a word about the Kahneman caveat.

Specifically, the peak end rule is quite a robust

finding in behavioral economics,

and it describes how people remember experiences after the fact.

It doesn't describe what makes an experience worth having in the moment.

There is a risk in optimizing sessions for memorability

at the expense of the quieter, less peak shaped pleasures that make a long campaign

feel like a life shared rather than a series of highlight reels.

Some of the most important sessions

in a campaign won't have a ten on the tension scale.

They will have a conversation that mattered, a character moment

that landed, a decision that will echo forward.

Those sessions may not score well on the peak end rule.

They are essential anyway, so

use these frameworks as a starting point for thinking about shape and feel.

Hold them loosely enough that the actual people at your table

can always take precedence over the theory.

So now let's look at a field guide for game masters.

So we've covered a lot of ground today theory models mechanics real time craft.

But before we close I want to give you something that you can take to

your prep table tonight a practical field guide a step by step.

The actual process of applying everything we've discussed to a real session.

Step one is draw the map before anything else.

Before you write a single encounter or plan a single NPC interaction,

open a blank page and draw the graph

horizontal axis scene's vertical axis intensity 0 to 10.

It takes 60s and it changes the entire orientation of your prep

marker, three peaks or your two peaks, or whatever you think you're going to need.

Hook in the first quarter of the session.

Complication at the midpoint.

Climax in the final quarter.

They're placeholders for emotional weight.

You're marking where things might need to matter in future.

Now, draw your value so 1 or 2 before the hook,

your establishing be where the session finds its feet before it escalates.

Rising slope from a four to a six between complication and crescendo.

The slow build of your final act.

Then assign scene types to each beat.

Go back to your map and label each major beat with a scene type combat role play.

Exploration. Mystery. Rest.

You're building your orchestration now.

Two guidelines here.

First, avoid two consecutive peaks using the same instrument.

If your question peak is a

combat encounter, maybe think about having your complication peak.

Maybe it's role play confrontation or a mystery revelation.

Consecutive combat peaks might be fine, depending on your campaign,

but it also might train your players to process combat a lower emotional register.

Vary the instrument and the peaks feel like a distinct experience.

Second, your deepest valley is a rest or low stakes roleplay.

Beat a genuine exhale.

Players at a campfire, a quiet moment in town, then ask some questions.

Look at each of your three peaks.

Does each peak have a clear, dramatic question attached to it?

Now let's talk about your valleys.

How low is your deepest valley?

If the lowest point in your session sits at a four,

your peaks could be compromised.

Where is your genuine zero and is it protected from the instinct to fill it?

Now your beat cycles for each of your major scenes, not just your peaks.

Write a brief note covering all four phases action.

Consequence. Reflection.

Anticipation, single lines or just fine action.

What happens? Consequence. What changes? Reflection?

Well, you'll invite players to feel or express anticipation.

What question opens at the scenes in to pull them forward?

The reflection note is the one that some game master

skip over in prep because it feels on scriptable,

and it isn't scriptable in the sense that you can't write the player's response.

What you can write

is your invitation, a question you'll ask, a moment of stillness.

You'll protect an NPC reaction

that gives players permission to feel the weight of what just happened.

Before moving on, write the invitation and then let players fill it.

Then think about your ending before the session begins.

Make a conscious decision, resolution

or cliffhanger based on three factors.

How emotionally heavy has the campaign been lately?

Heavy campaigns need resolution endings more regularly.

Where are you in the campaign arc?

Mid arc sessions can sustain cliffhangers more easily than sessions

coming off a major story that needs to land fully and honestly.

How are your players doing?

Not their characters, your players?

If people have had a hard week, a resolution ending that sends them home

with a sense of accomplishment does more for your table

than a cliffhanger that sends them home with more anxiety.

Decide before you sit down.

Know which ending you're building toward.

You can change it, of course, during the session,

if the live material demands it.

But having a default means your final scene has a shape before it begins.

Prep your three adjustments for each of your three peaks.

Write one.

Ready made version of each adjustment.

What does acceleration look like here?

If this scene goes flat, what's the fastest way to raise

stakes without breaking a fiction?

An NPC arrival, a new threat, a time pressure that wasn't visible before

and you can write it down so you're not improvising under pressure

when the table needs energy.

What does holding look like here?

If this scene needs to breathe after its peak,

what's your invitation to the reflection phase?

A question you'll ask, a pause you'll protect, a beat of stillness.

You'll create.

You can write it

so you can remember to reach for it instead of cutting away too fast.

And what does a pivot look like here?

If this scene loses structural footing entirely, what's your reentry point?

A world event, a new piece of information, a character moment

that redirects without canceling what came before.

Then of course, run the session, then debrief yourself after the session.

Take a few minutes to do this one thing.

Go back to your map and draw what actually happened rather than what you planned.

What the sessions tension curve actually looked like based on your memory

of the table's energy.

Compare the two shapes.

Where did players exceed your plan peaks

that signal about what they care about?

Where did the session flatline despite a planned peak?

That's a signal about what isn't landing.

Where did an unplanned valley open up that you didn't protect?

You don't need to analyze this exhaustively.

Just a few minutes of honest reflection.

One note about what to adjust for next session.

Over time, the gap between your plan shape and your actual shape might get smaller

because you become more fluent in reading them.

That fluency is part of the craft, and it compounds

it all builds toward the kind of game mastering where

the heartbeat model starts being a reflex.

And that's your lecture for today, everyone.

If this video gave you something useful, hit the like button and subscribe

if you haven't already and share it with a game master

that you think would find it useful.

It genuinely helps the channel, and there's a lot more where this came from.

Drop a comment below and tell

me what does your session tension curve usually look like?

And as always, thanks for watching.

See you next time.