You know that feeling when a session that should’ve been about looting a dragon’s hoard turns into two players glaring at each other over “who really started it”? Yeah. That one.

Hot take: PvP conflict doesn’t kill campaigns. Badly handled PvP conflict kills campaigns. Big difference. One is a mechanic. The other is a table full of people who used to be friends checking their phones during combat because nobody wants to be there anymore.

I want to tell you about a table that almost didn’t make it. A paladin. A rogue. A grudge that started over stolen gold and ended with someone standing up from the table mid-session. And how that table came back from the brink using nothing fancier than a couple of tools you probably already own.

Guess what? You can steal this. That’s the whole point.

Picture this. Your party just walked into a random town you drew up in fifteen minutes. A farmer runs up, out of breath, and says her cow is missing. “Please, kind adventurers, will you find my cow?”

Your players look at each other. You can see the exact moment their eyes glaze over. One player checks his phone. Another starts doodling on her character sheet. Somewhere, a d20 rolls off the table and nobody chases it.

That’s the sound of a side quest dying on arrival.

Look, we’ve all been there. As a GM, you know your campaign needs texture between the big story beats. You know players want to feel like the world is bigger than the main plot. So you throw together a quick “go find my missing cow” errand, and rather than adding life to your table, it sucks the air out of the room.

Here’s the good news: side quests aren’t the problem. Bad side quests are. And once you know what separates a quest that earns its spot at the table from one that’s just filler with extra steps, you’ll never run a dead-cow errand again.

Stay with me here, because this is going to save you hours of prep and about a dozen “can we just skip this?” looks from your players.