lukasparke-archivesOfNethysScraper/sorted/rules/Depth of Downtime.json

{
 "breadcrumbs": [
  "Chapter 1: Gamemastery Basics",
  "Running Downtime"
 ],
 "breadcrumbs_spa": [],
 "category": "rules",
 "exclude_from_search": false,
 "id": "rules-871",
 "markdown": "<title level=\"1\" right=\"Rules\">[Depth of Downtime](/Rules.aspx?ID=871)</title>\r\n\r\n<row gap=\"tiny\">**Source** [Gamemastery Guide](/Sources.aspx?ID=22) pg. 22</row>\r\n\r\n<row gap=\"medium\">\r\n<column gap=\"medium\" flex=\"1 1 400px\">\r\nDetermine how involved your group wants downtime to be at the start of the game. If your players vary greatly in preference, you might need to find a middle ground, or some way to give the players least interested in downtime something they would find compelling. You can adjust downtime depth as the game goes along, and you might find it becomes more important to the players as their connection to the setting grows stronger.\n\n Pay attention to the amount of real-world time you spend in downtime and the level of detail. Downtime should rarely last a whole session. Usually, a half hour between significant adventures is about right, and 15 minutes for shorter lulls in the action, such as when PCs return to a town briefly in the middle of an adventure. You can extend this as needed for more detailed roleplaying scenes.\n\n For the level of detail, it’s important to give more than just an overview, but often the basics will do. “A fleet of merchant ships arrives in the port, and an officer puts you to work unloading cargo” might do for using [Sailing Lore](/Skills.aspx?ID=8) to [Earn Income](/Actions.aspx?ID=23), and “Your shipment of iron arrives late, but you’re able to complete the armor” could be enough for [Crafting](/Actions.aspx?ID=43). Go deeper if the player sets out to do something specific or asks questions you think have potential for an interesting story, but be careful with too much detail, as you run the risk of boring most of the table with minutiae.\r\n</column>\r\n\r\n<column gap=\"medium\">\r\n\r\n</column>\r\n\r\n</row>\n\n<document level=\"2\" id=\"rules-872\" />\r\n\r\n<document level=\"2\" id=\"rules-873\" />",
 "name": "Depth of Downtime",
 "next_link": {
  "label": "Long-Term Goals",
  "url": "/Rules.aspx?ID=874"
 },
 "previous_link": {
  "label": "Running Exploration",
  "url": "/Rules.aspx?ID=858"
 },
 "rarity": "common",
 "release_date": "2020-02-26",
 "resistance": {},
 "search_markdown": "<additional-info>\r\n<row gap=\"tiny\">**Source** [Gamemastery Guide](/Sources.aspx?ID=22) pg. 22</row>\r\n\r\nChapter 1: Gamemastery Basics / Running Downtime\r\n</additional-info>",
 "source": [
  "Gamemastery Guide"
 ],
 "source_raw": [
  "Gamemastery Guide pg. 22"
 ],
 "source_category": "Rulebooks",
 "source_markdown": "<row gap=\"tiny\">[Gamemastery Guide](/Sources.aspx?ID=22) pg. 22</row>",
 "speed": {},
 "text": " Depth of Downtime Source Gamemastery Guide pg. 22 Determine how involved your group wants downtime to be at the start of the game. If your players vary greatly in preference, you might need to find a middle ground, or some way to give the players least interested in downtime something they would find compelling. You can adjust downtime depth as the game goes along, and you might find it becomes more important to the players as their connection to the setting grows stronger. Pay attention to the amount of real-world time you spend in downtime and the level of detail. Downtime should rarely last a whole session. Usually, a half hour between significant adventures is about right, and 15 minutes for shorter lulls in the action, such as when PCs return to a town briefly in the middle of an adventure. You can extend this as needed for more detailed roleplaying scenes. For the level of detail, it’s important to give more than just an overview, but often the basics will do. “A fleet of merchant ships arrives in the port, and an officer puts you to work unloading cargo” might do for using Sailing Lore to Earn Income, and “Your shipment of iron arrives late, but you’re able to complete the armor” could be enough for Crafting. Go deeper if the player sets out to do something specific or asks questions you think have potential for an interesting story, but be careful with too much detail, as you run the risk of boring most of the table with minutiae. ",
 "type": "Rules",
 "url": "/Rules.aspx?ID=871",
 "weakness": {}
}