Why do so many superhero campaigns start strong and then slowly fall apart?
In this episode of Gotham & Beyond, we examine four of the biggest reasons DC Heroes campaigns fail. From overusing famous NPC heroes and escalating threats too quickly, to power imbalance at the table and the temptation to build characters that overshadow everyone else, these are problems that many Game Masters eventually encounter.
Hey folks just a quick update as I am planning to make more episodes soon. So stay tuned!
Coming soon |
Project Prometheus feels like one of those adventures Mayfair probably should not have been able to fit into thirty pages, yet somehow they did anyway. Reading through it now, you can see early DC Heroes trying to figure out what superhero roleplaying could really be. This is not a simple "fight the villain in a warehouse" kind of module. It throws giant eagle attacks, blackouts, secret government investigations, Mediterranean pursuit scenes, ancient mythology, super-science, and a literal Minotaur into the same story and somehow keeps moving forward.
Messy? Absolutely. But boring? Never.
What surprised me most revisiting it was how investigation-heavy it actually is.
The module wants heroes gathering information, chasing leads, talking to contacts, and slowly uncovering a larger conspiracy. The action scenes are big and loud, but the connective tissue is detective work and escalation. That still holds up today. If I ran Project Prometheus now using DC Heroes 3rd Edition, I would mostly clean up presentation and expand some character moments, but I would leave the core structure alone. The strange mythology-meets-technology angle gives the adventure a personality a lot of modern superhero scenarios are missing. It feels unapologetically comic-book, and honestly, that may be why it still works.
Reading through JSA 19 this week, I found something that caught my attention, and it wasn't the fight scenes at all. It was the Spectre and how he was handled in the comic.
Most groups skip the villain downtime tables. I did too at first. It felt like extra bookkeeping. Then I actually started rolling on them. Suddenly the game moved in ways I wasn't expecting.
Episode 19 takes a look at King of Crime, one of the early DC Heroes modules from Mayfair Games, and this one wastes no time getting the city into trouble. Central City is under pressure almost right away, with the Secret Society of Super-Villains making coordinated moves that leave the heroes scrambling from one crisis to the next. That is one of the big strengths of the module. It understands momentum. It gives you a city in trouble, a villain team with personality, and a steady climb in tension that feels very much like an old comic book arc. Instead of one flat plot, you get a string of crimes, public danger, and rising stakes that keep the adventure moving.
This episode of Gotham and Beyond looks at Blood Feud, an early DC Heroes module that still has a lot to teach. I talk about why the adventure works, how it builds pressure, and how you can adapt it for your own custom heroes without needing the exact team it was written for. If you like old superhero modules, city-based trouble, villain teams, and adventures with good bones, this one is worth a second look.
A lot of villains in superhero games fall apart because they get built backwards. You start with powers, numbers, and combat tricks, then try to figure out who they are after the fact.
This one hits different.
You look at that cover and you already know what kind of story this is going to be. Not clean. Not heroic in the shiny sense. This is street-level pressure. People getting grabbed, dragged, hurt. No speeches. Just force.
Some powers in DC Heroes grab you right away.
Super Strength is obvious. Flight is obvious. Heat Vision, Energy Blast, Invulnerability, all of that makes sense the second you read it. You know what those powers do. You know why they matter. They are loud powers. Clean powers. Comic book powers in the most direct way possible.
Then you get to Dispersal.
Episode 14 takes a look at In Hot Pursuit, a fast-moving DC Heroes module built around pressure, momentum, and constant reaction. This time, the focus is not just on the adventure itself, but on how you can take a module written with specific superheroes in mind and make it work for custom characters at your own table.
A case doesn’t start hot. Most of the time it just sits there. A name, a location, a piece of evidence. The book calls out how you can track the heat of an investigation in stages. It is not about speed. It is about tension and risk. Every move the players make either cools things off or makes them boil.
Most players rush interrogation. They think it’s a single roll. Ask the question, get the answer. The book doesn’t treat it like that. It gives interrogation a clock. Every attempt you make has weight. Fail or push too hard and the suspect shuts down, or worse, calls for backup.
Picked Arrow back up and started running through those early episodes again. Mark Scheffer stood out right away, so I figured he was worth a proper write-up for the table.
You read something like Countdown to Armageddon and your first thought is, “This is for Superman.” And yeah… it is. The whole thing is built around him being everywhere at once, solving disasters while Brainiac is pulling strings behind the curtain.
Attribute Points look complicated at first. They measure almost everything in the DC Heroes Role-Playing Game. Time. Distance. Weight. Money. Knowledge. Even damage. But the rule is simple: each AP is twice the previous one. That doubling changes how you think about actions in play.
When you flip through the Drawbacks section in DC Heroes, there’s a line that jumps right out. Traumatic Flashbacks. It looks like just another quirk in a long list of quirks until you actually put it on the table. Then it hits like a truck.
Knockback in DC Heroes is one of those rules that feels small until you actually see it in play. You throw a punch, you roll high, the target goes flying. The book lays it out clean... Column Shifts on the Action Table minus the target’s weight in APs equals the distance they’re sent back. That distance is in APs too, so you can translate it directly into feet, yards, or city blocks.
