9
Ideas for Combat Downtime
(lemmy.world)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 24 Jun 2026
9 points (100.0% liked)
rpg
4855 readers
18 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 3 years ago
MODERATORS
When it comes to 3.5, the biggest potential slowdown lies in trying to keep status conditions straight, especially 1) stacked buffs and 2) those with durations measured in rounds at low levels. What sort of arrangements does your table have to track status conditions?
Note also that actually paying attention to the battle instead of treating it as background noise when it's not your turn helps. There's a big table speed difference between having a plan and asking for a summary.