rpg

4272 readers

1 users here now

This community is for meaningful discussions of tabletop/pen & paper RPGs

Rules (wip):

Do not distribute pirate content
Do not incite arguments/flamewars/gatekeeping.
Do not submit video game content unless the game is based on a tabletop RPG property and is newsworthy.
Image and video links MUST be TTRPG related and should be shared as self posts/text with context or discussion unless they fall under our specific case rules.
Do not submit posts looking for players, groups or games.
Do not advertise for livestreams
Limit Self-promotions. Active members may promote their own content once per week. Crowdfunding posts are limited to one announcement and one reminder across all users.
Comment respectfully. Refrain from personal attacks and discriminatory (racist, homophobic, transphobic, etc.) comments. Comments deemed abusive may be removed by moderators.
No Zak S content.
Off-Topic: Book trade, Boardgames, wargames, video games are generally off-topic.
No AI-generated content. Discussion of AI generation pertaining to RPGs is explicitly allowed.

founded 2 years ago

MODERATORS

Avogadro@ttrpg.network

sirblastalot@ttrpg.network

TripHammer@ttrpg.network

Primarch@ttrpg.network

BrentTaylor@ttrpg.network

Blades in the Dark: seeking advice for running (infosec.pub)

submitted 1 week ago by codemichael@lemmy.world to c/rpg@ttrpg.network

16 comments fedilink hide all child comments

I agreed to run a game of Blades in the Dark starting in Feb. I've not run or played it before, but I have plenty of GMing experience. The plan is to do a limited game, once or twice a month for about six months (so somewhere around nine to twelve sessions in total).

It seems like the most important thing will be getting as much of the lore in my head as I can between now and then so that I can respond to the evolving gameplay, rather than plan out any kind of storyline.

If anyone is interested in sharing their dos and don't, or other experience, my player will appreciate it.

you are viewing a single comment's thread
view the rest of the comments

[–] codemichael@lemmy.world 3 points 6 days ago (1 children)

Sorry you didn't have a great experience, but thank you for sharing it. It's a useful perspective to keep in mind, thank you.

[–] INeedMana@piefed.zip 3 points 4 days ago (1 children)

character was always fucking up

That reminded me. In BitD a lot rides on presentation. Try to not make failed/complicated rolls about the characters failing but the circumstances not being in their favor, instead

They didn't break the lockpick - they noticed a nasty trap in the lock just in time to not get stung, the lock will need more work
They didn't get hit when grappling with a guard - they hear footsteps approaching (trauma in general is the least interesting choice, unless you feel it's time for it to appear in the story) They didn't make noise when sneaking by - there was a loose plank in the floor they had no way of noticing

From my experience, when you most often aim at coming up with new external problems (like those footsteps), characters will start to bounce off them, instead of just progressing through the story. It might feel like you can't ever really challenge them but on the other side of the table something can always come up and they have to constantly think on their feet, which simulates the feel of a heist.

Unless placed so it builds tension, "you missed" most often just breaks the flow of the plot. It's a temporary setback that doesn't build anything. "You got him clean but it's the funny/irritating/popular/w/e guy among the guards. Everyone knows him. I'm marking first piece on alarm clock because sooner or later they will notice he's not around tonight" - that builds tension and the world even if during this heist it will be the last piece marked on that clock

[–] codemichael@lemmy.world 3 points 4 days ago

I was starting to think along these lines, but you've got some great examples here. Thanks.