lukasparke-archivesOfNethysScraper/sorted/rules/Running a Chase.json

{
 "breadcrumbs": [
  "Chapter 3: Subsystems",
  "Chases"
 ],
 "breadcrumbs_spa": [],
 "category": "rules",
 "exclude_from_search": false,
 "id": "rules-1217",
 "markdown": "<title level=\"1\" right=\"Rules\">[Running a Chase](/Rules.aspx?ID=1217)</title>\r\n\r\n<row gap=\"tiny\">**Source** [Gamemastery Guide](/Sources.aspx?ID=22) pg. 158</row>\r\n\r\n<row gap=\"medium\">\r\n<column gap=\"medium\" flex=\"1 1 400px\">\r\nWhen running a chase, narrate the scene and give vivid descriptions of the obstacles the PCs face, rather than just reading off a list of skills and immediately having the players start rolling dice and making checks. A chase is a framework for roleplaying, not just a dice game. Encourage the PCs to describe what they’re doing, and how they’re helping their comrades overcome each obstacle.\n\n Typically, it’s best to tell the players the DCs of the default options, so they can make informed decisions. At the least, you should indicate the relative difficulty of the clear paths. The PCs are adventurers, so they’re experienced at assessing which path is going to be easier or harder.\n\n Try to make it feel like the PCs are really part of a chase scene, like in a movie. As each side makes progress, describe how they pull ahead or close the gap. PCs far from their foes might hear shouts in the distance. As they get closer, they catch glimpses, and then finally see their quarry in full view once they’re on the enemies’ heels. Think about how the events of the chase affect the environment, as well. For instance, if a kaiju is chasing after the PCs, after the PCs overcome an obstacle consisting of a thick copse of trees, you could describe how the kaiju flattens the trees beneath its feet as it stomps after them.\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-1218\" />\r\n\r\n<document level=\"2\" id=\"rules-1219\" />",
 "name": "Running a Chase",
 "next_link": {
  "label": "Sample Obstacles",
  "url": "/Rules.aspx?ID=1220"
 },
 "previous_link": {
  "label": "Building a Chase",
  "url": "/Rules.aspx?ID=1212"
 },
 "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. 158</row>\r\n\r\nChapter 3: Subsystems / Chases\r\n</additional-info>",
 "source": [
  "Gamemastery Guide"
 ],
 "source_raw": [
  "Gamemastery Guide pg. 158"
 ],
 "source_category": "Rulebooks",
 "source_markdown": "<row gap=\"tiny\">[Gamemastery Guide](/Sources.aspx?ID=22) pg. 158</row>",
 "speed": {},
 "text": " Running a Chase Source Gamemastery Guide pg. 158 When running a chase, narrate the scene and give vivid descriptions of the obstacles the PCs face, rather than just reading off a list of skills and immediately having the players start rolling dice and making checks. A chase is a framework for roleplaying, not just a dice game. Encourage the PCs to describe what they’re doing, and how they’re helping their comrades overcome each obstacle. Typically, it’s best to tell the players the DCs of the default options, so they can make informed decisions. At the least, you should indicate the relative difficulty of the clear paths. The PCs are adventurers, so they’re experienced at assessing which path is going to be easier or harder. Try to make it feel like the PCs are really part of a chase scene, like in a movie. As each side makes progress, describe how they pull ahead or close the gap. PCs far from their foes might hear shouts in the distance. As they get closer, they catch glimpses, and then finally see their quarry in full view once they’re on the enemies’ heels. Think about how the events of the chase affect the environment, as well. For instance, if a kaiju is chasing after the PCs, after the PCs overcome an obstacle consisting of a thick copse of trees, you could describe how the kaiju flattens the trees beneath its feet as it stomps after them. ",
 "type": "Rules",
 "url": "/Rules.aspx?ID=1217",
 "weakness": {}
}