rpg

3210 readers

30 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.

founded 2 years ago

MODERATORS

Avogadro@ttrpg.network

sirblastalot@ttrpg.network

TripHammer@ttrpg.network

Primarch@ttrpg.network

BrentTaylor@ttrpg.network

Forged in the dark : one large clock, or stacking small clocks ? (sh.itjust.works)

submitted 6 months ago* (last edited 6 months ago) by Ziggurat@sh.itjust.works to c/rpg@ttrpg.network

10 comments fedilink hide all child comments

A very short question, for people used to Forge in the dark games.

To manage a situation evolving negatively or positively on the long term, do you use a large clock, or stack several one small ones with a concrete impact every time they fill?

let’s say the PC are asking questions they shouldn’t be asking about “the bad guys”. Would you say

3 times 4 tick clock : leading to “bad guys hear rumours about someone asking question”/Bad guys Finds out who asks the question/ Bad guys guards find the PC.

A 12 tick clock and continuously increasing the pressure on the PC as the clock is filling ?

The related question, is how do you handle the consequence of the clocks filling beside the : Enemy guard found you (or missing accomplished when it’s on the PC side). Just by role-playing, or would you change the PC position or is it as often in rpg “it depends” ?

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

[–] Kolanaki@yiffit.net 0 points 6 months ago* (last edited 6 months ago) (2 children)

I don't usually use any kind of pre determined timing that would be measured with a clock. I use story beats to introduce new ideas and events in the story so it always flows naturally based not just on what I have my NPCs doing in the background, but also what the PCs are doing in the foreground. I might have things that are timed out in weeks or months that can be triggered by the party resting or training or whatever, but this would only be because they've triggered an event like an incoming invasion force or something as it falls along the way the story has progressed.

Let's say the players are asking questions they shouldn't be asking about...

If the players are asking questions that are metagaming, I direct them back to the game and what information their characters have and what questions they would have based on that. If the characters shouldn't be asking the question because of some in-world reason, such as the characters they are talking to are loyal to a king who finds such talk treasonous, well then it would just play out in-game taking those things into account and the party may be pushed into a fight or taken to jail.

I employ as much improv as I write things down ahead of time. There is no way you can account for every single thing that every other player at the table may do, so I think it's best to leave a huge degree of vagueness until things start happening, so you can just make shit up on the fly for things you couldn't prepare for.

Time is relative. Especially in story-telling.

[–] corcaroli@ttrpg.network 1 points 6 months ago

It feels like you've never run Blades or any kind of a similar game...

load more comments (1 replies)