Adjudicating Actions.json 3.0 KB

12345678910111213141516171819202122232425262728293031323334353637
  1. {
  2. "breadcrumbs": [
  3. "Chapter 1: Gamemastery Basics",
  4. "Running Encounters"
  5. ],
  6. "breadcrumbs_spa": [],
  7. "category": "rules",
  8. "exclude_from_search": false,
  9. "id": "rules-841",
  10. "markdown": "<title level=\"1\" right=\"Rules\">[Adjudicating Actions](/Rules.aspx?ID=841)</title>\r\n\r\n<row gap=\"tiny\">**Source** [Gamemastery Guide](/Sources.aspx?ID=22) pg. 12</row>\r\n\r\n<row gap=\"medium\">\r\n<column gap=\"medium\" flex=\"1 1 400px\">\r\nSome of the basic actions of the game require you to interpret how a rule should apply. Here, you’ll find advice the types of rules calls that can occur frequently. For rules decisions that are either/or (such as whether a creature can [Aid](/Actions.aspx?ID=75) or [Take Cover](/Actions.aspx?ID=90)), a PC can usually determine before they take the action whether doing so is viable; if it isn’t viable for some reason, alert them that it won’t work before they spend time, actions or resources trying. There are some exceptions, especially if the reason an action wouldn’t work is something a character wouldn’t know. For example, if a character tries to Take Cover behind a wall, not realizing it’s illusory, you shouldn’t reveal the deception prematurely.\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-842\" />\r\n\r\n<document level=\"2\" id=\"rules-843\" />\r\n\r\n<document level=\"2\" id=\"rules-844\" />\r\n\r\n<document level=\"2\" id=\"rules-845\" />\r\n\r\n<document level=\"2\" id=\"rules-846\" />",
  11. "name": "Adjudicating Actions",
  12. "next_link": {
  13. "label": "Maps and Miniatures",
  14. "url": "/Rules.aspx?ID=847"
  15. },
  16. "previous_link": {
  17. "label": "Ad Hoc Bonuses and Penalties",
  18. "url": "/Rules.aspx?ID=840"
  19. },
  20. "rarity": "common",
  21. "release_date": "2020-02-26",
  22. "resistance": {},
  23. "search_markdown": "<additional-info>\r\n<row gap=\"tiny\">**Source** [Gamemastery Guide](/Sources.aspx?ID=22) pg. 12</row>\r\n\r\nChapter 1: Gamemastery Basics / Running Encounters\r\n</additional-info>",
  24. "source": [
  25. "Gamemastery Guide"
  26. ],
  27. "source_raw": [
  28. "Gamemastery Guide pg. 12"
  29. ],
  30. "source_category": "Rulebooks",
  31. "source_markdown": "<row gap=\"tiny\">[Gamemastery Guide](/Sources.aspx?ID=22) pg. 12</row>",
  32. "speed": {},
  33. "text": " Adjudicating Actions Source Gamemastery Guide pg. 12 Some of the basic actions of the game require you to interpret how a rule should apply. Here, you’ll find advice the types of rules calls that can occur frequently. For rules decisions that are either/or (such as whether a creature can Aid or Take Cover), a PC can usually determine before they take the action whether doing so is viable; if it isn’t viable for some reason, alert them that it won’t work before they spend time, actions or resources trying. There are some exceptions, especially if the reason an action wouldn’t work is something a character wouldn’t know. For example, if a character tries to Take Cover behind a wall, not realizing it’s illusory, you shouldn’t reveal the deception prematurely. ",
  34. "type": "Rules",
  35. "url": "/Rules.aspx?ID=841",
  36. "weakness": {}
  37. }