-
Notifications
You must be signed in to change notification settings - Fork 82
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Update catalogueing rules for cross referencing (#1223)
- Loading branch information
Showing
73 changed files
with
1,421 additions
and
489 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,57 @@ | ||
| { | ||
| "id": "gob", | ||
| "scenario_name": "Guardians of the Abyss", | ||
| "full_name": "Guardians of the Abyss", | ||
| "header": "", | ||
| "type": "core", | ||
| "setup": [ | ||
| "$explore_rule", | ||
| "$story_cards", | ||
| "$strength_of_the_abyss", | ||
| "$taken_by_the_abyss" | ||
| ], | ||
| "steps": [ | ||
| { | ||
| "id": "$explore_rule", | ||
| "title": "Explore", | ||
| "type": "rule_reminder", | ||
| "text": "Some abilities in <i>Guardians of the Abyss</i> are identified with an <b>Explore</b> action designator. Such abilities are generally used to find new locations to put into play, and are initiated using the “activate” action.\n<b>Explore</b> abilities instruct you to draw the top card of the “exploration deck,” which is a separate deck that will be constructed during this scenario. This deck consists of several single-sided locations and treachery cards.", | ||
| "bullets": [ | ||
| { | ||
| "text": "Each <b>Explore</b> ability indicates a particular type of location that you are seeking to draw. <b>If a location of that type is drawn, it is put into play, and you move to that location.</b> This is considered a “successful” exploration." | ||
| }, | ||
| { | ||
| "text": "If any other location is drawn, place it next to the exploration deck, and draw the next card from the exploration deck. Repeat this process until a location of the indicated type is drawn, or a treachery is drawn. After this action has ended, shuffle each location next to the exploration deck back into the exploration deck." | ||
| }, | ||
| { | ||
| "text": "If a treachery card is drawn, it is resolved as normal. If it is discarded, place it in the encounter discard pile as you would normally. There is no discard pile for the exploration deck. This is considered an “unsuccessful” exploration." | ||
| }, | ||
| { | ||
| "text": "When a single-sided location is put into play from the exploration deck, place clues on that location equal to its clue value." | ||
| }, | ||
| { | ||
| "text": "If the entire exploration deck is revealed without finding either a treachery card or a location specified by the explore ability, the exploration simply ends. It is neither successful nor unsuccessful. All locations drawn during the exploration should be shuffled back into the exploration deck, and the investigator’s action ends." | ||
| } | ||
| ], | ||
| "example": "<i>Example: Act 1a—“Search for the Gate” has the following ability: “[action]: <b>Explore</b>. Draw the top card of the exploration deck. If it is a connecting location, put it into play and move to it.” Ursula Downs is at the Expedition Camp and wishes to find a new location to travel to. She spends her first action to explore, drawing the top card of the exploration deck. The card she draws is Desert Oasis. Because Desert Oasis is a location that is not connected to the Expedition Camp, it is placed next to the exploration deck, and Ursula draws the next card in the exploration deck. This time, she draws the Sandstorm treachery card, which she resolves as normal and places in the encounter discard pile. Her exploration is unsuccessful, and she must shuffle the Desert Oasis that she drew previously back into the exploration deck. Ursula decides to explore one more time, spending a second action. This time, she draws Nile River, which is connected to the Expedition Camp. Her exploration is successful. Nile River is put into play with clues on it equal to its clue value, and Ursula immediately moves from the Expedition Camp to the Nile River.</i>" | ||
| }, | ||
| { | ||
| "id": "$story_cards", | ||
| "title": "Story Cards", | ||
| "type": "rule_reminder", | ||
| "text": "Story cards are a new cardtype in this scenario. These cards serve as an avenue for additional narrative and typically appear as the reverse side of another scenario card. When you are instructed to resolve a story card, simply read its story text and resolve its game text, if any.\n<i>(Note: When a location or enemy that is in play is flipped over to a story card on its other side, that location or enemy is still considered to be in play while that story card is being resolved.)</i>" | ||
| }, | ||
| { | ||
| "id": "$strength_of_the_abyss", | ||
| "title": "Strength of the Abyss", | ||
| "type": "rule_reminder", | ||
| "text": "During this scenario, resources on the scenario reference card represent the current strength of the abyss. When you are instructed to add strength to the abyss or remove strength from the abyss, adjust the number of resource tokens on the scenario reference card accordingly. The strength of the abyss has no inherent game effect on its own, though certain encounter card effects may grow stronger or change depending on the current strength of the abyss. Beware—as the abyss grows in strength, so too will the forces set against you. Should it grow too powerful, you will surely fail as Guardians of the Abyss." | ||
| }, | ||
| { | ||
| "id": "$taken_by_the_abyss", | ||
| "title": "“Taken by the Abyss”", | ||
| "type": "rule_reminder", | ||
| "text": "If an effect states that a defeated investigator or [[Ally]] asset has been <i>“taken by the abyss,”</i> that character has been afflicted by a curse which puts them in a comatose state. When an investigator or [[Ally]] asset is <i>taken by the abyss</i>, first add 1 strength to the abyss. Then, if that card was unique, record in the campaign log that <i>“(card name) was taken by the abyss.”</i> An investigator who has been <i>taken by the abyss</i> is treated as if he or she was killed or driven <b>insane</b>. Additionally, for the remainder of the campaign, players cannot play copies of any unique [[Ally]] asset who has been <i>taken by the abyss.</i>" | ||
| } | ||
| ] | ||
| } |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,29 @@ | ||
| { | ||
| "rules": [ | ||
| { | ||
| "title": "", | ||
| "steps": [""] | ||
| }, | ||
| { | ||
| "title": "", | ||
| "steps": [""] | ||
| } | ||
| ], | ||
|
|
||
| "rules": [ | ||
| { | ||
| "title": "", | ||
| "steps": ["$"] | ||
| } | ||
| ], | ||
|
|
||
| "id": "", | ||
| "scenario_name": "", | ||
| "full_name": "", | ||
| "header": "", | ||
| "type": "core", | ||
| "setup": [ | ||
| ], | ||
| "steps": [ | ||
| ] | ||
| } |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,32 @@ | ||
| { | ||
| "id": "ptc", | ||
| "scenario_name": "The Path to Carcosa", | ||
| "full_name": "The Path to Carcosa", | ||
| "header": "", | ||
| "type": "core", | ||
| "setup": [ | ||
| "$hidden_keyword", | ||
| "$doubt_and_conviction", | ||
| "$story_cards" | ||
| ], | ||
| "steps": [ | ||
| { | ||
| "id": "$hidden_keyword", | ||
| "type": "rule_reminder", | ||
| "title": "New Keyword: Hidden", | ||
| "text": "Some encounter cards in <i>The Path to Carcosa</i> campaign have the “hidden” keyword. Hidden cards have <b>Revelation</b> abilities that secretly add them to your hand. This should be done without revealing that card or its text to the other investigators. While a hidden card is in your hand, treat it as if it were in your threat area. Its Constant abilities are active, and abilities on it can be triggered, but only by you. A hidden card counts toward your hand size, but it cannot be discarded from your hand by any means except those described on the card. When discarded, hidden cards are placed in the encounter discard pile. They do not remain a part of your deck like weaknesses do. For the best experience, players are encouraged to stay “in character” and not share information about hidden cards in their hand." | ||
| }, | ||
| { | ||
| "id": "$doubt_and_conviction", | ||
| "type": "rule_reminder", | ||
| "title": "Doubt and Conviction", | ||
| "text": "Some story resolutions and interludes in The Path to Carcosa campaign instruct the players to “Mark one <b>Doubt</b>” or “Mark one <b>Conviction</b>” in their Campaign Log. This is done by filling in one of the boxes next to “<b>Doubt</b>” or “<b>Conviction</b>” in the Campaign Log.\nLater in the campaign, some scenarios may be changed or altered depending on whether the investigators “have more <b>Doubt</b> than <b>Conviction</b>” or “have more <b>Conviction</b> than <b>Doubt</b>.” The investigators have more <b>Doubt</b> than <b>Conviction</b> if the number of boxes filled in next to <b>Doubt</b> is greater than the number of boxes filled in next to <b>Conviction</b> (and vice versa). <b>Doubt</b> and <b>Conviction</b> are shared among all of the investigators, and they are not tied to any specific investigator. <b>Doubt</b> and <b>Conviction</b> have no game effect except when explicitly referenced by the Campaign Guide or by a card effect." | ||
| }, | ||
| { | ||
| "id": "$story_cards", | ||
| "type": "rule_reminder", | ||
| "title": "Story Cards", | ||
| "text": "Story cards are a new cardtype in <i>The Path to Carcosa</i> campaign. These cards serve as an avenue for additional narrative and typically appear as the reverse side of another scenario card. When you are instructed to resolve a story card, simply read its story text and resolve its game text, if any." | ||
| } | ||
| ] | ||
| } |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.