Source strings

130 Strings 100%
Browse Translate
135,109 Words 100%
1,284,730 Characters 100%
This translation is being used as source strings within this component.

Strings status

Strings Words Characters
130 135,109 1,284,730
All strings Browse Translate Zen
130 135,109 1,284,730
Translated strings Browse Translate Zen
12 29,783 285,744
Strings with any failing checks Browse Translate Zen
3 20,009 200,228
Failing check: Unpluralised Browse Translate Zen
2 4,727 40,222
Failing check: Ellipsis Browse Translate Zen
8 5,717 50,878
Failing check: Multiple failing checks Browse Translate Zen

Overview

Project website github.com/fvtt-cn/swade_compendium_chn
Instructions for translators

SWADE 汉化
Translation license GNU General Public License v3.0 or later
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Any authenticated user can contribute.
  • The translation uses monolingual files.
  • The translation base language is editable.
Source code repository https://github.com/fvtt-cn/swade_compendium_chn
Repository branch main
Last remote commit Merge pull request #16 from bnp800/main 229e66a
User avatar bnp800 authored a year ago
Weblate repository https://weblate.dickytwister.org/git/swade/swade_compendium_chn/
File mask */swpf-core-rules.swpf-rules.json
Monolingual base language file en-US/swpf-core-rules.swpf-rules.json
Translation file Download en-US/swpf-core-rules.swpf-rules.json
Last change March 9, 2024, 4:22 p.m.
Last change made by hmqgg
Language English
Language code en
Text direction Left to right
Number of speakers 1,728,900,209
Number of plurals 2
Plural type One/other
Plurals Singular 1
Plural 0, 2, 3, 4, 5, 6, 7, 8, 9, 10, …
Plural formula n != 1
4 weeks ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 130 135,109 1,284,730
Translated 100% 130 100% 135,109 100% 1,284,730
Needs editing 0% 0 0% 0 0% 0
Read-only 0% 0 0% 0 0% 0
Failing checks 9% 12 22% 29,783 22% 285,744
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 0% 0 0% 0 0% 0
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 131 changes 0 changes 1 change 0 changes
AprMayJunJulAugSepOctNovDecJanFebMar

Quick numbers

135 k
Hosted words
130
Hosted strings
100%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
+100%
—
Contributors
—
User avatar hmqgg

Resource updated
Parsing of the “en-US/swpf-core-rules.swpf-rules.json” file was enforced. a year ago
User avatar None

Resource updated
File “en-US/swpf-core-rules.swpf-rules.json” was added. a year ago
User avatar None

String updated in the repository
<div class="swpf-core">
<h1 class="wide">Travel</h1>
<p>
Many epic tales feature trips across great expanses. A party may sail the
Inner Sea or ride across the frontier of Varisia or navigate every district
in Absalom.
</p>
<p>
Below are some guidelines to help you figure out how long these journeys
take and what dramatic events might happen along the way.
</p>
<p>
<strong>When to Use These Rules:</strong> If it doesn’t matter how long the
trip takes, skip all this. Narrate the journey, maybe do an
<strong>@UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore04theadv.JournalEntryPage.04interludes0000]{Interlude}</strong>, and get to the next scene. If you
need to know how long the trip takes, or want to insert an obstacle or
encounter of some sort, use the information below as a guideline.
</p>
<p>
<strong>The Basics:</strong> The mode of travel determines how many miles the group makes per day.
</p>

<h2>Travel Times</h2>

<p>
The rates below assume reasonable terrain and weather. Difficult conditions
can drastically decrease progress (or increase it in the case of sailing
with strong winds).
</p>
<table style="width: 50%;">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<th class="main-heading" colspan="2">Average Travel Times</th>
</tr>
<tr>
<th class="sub-heading left">Transport</th>
<th class="sub-heading">Miles/8 hour Day</th>
</tr>
<tr>
<td>Foot</td>
<td class="centered">24</td>
</tr>
<tr>
<td>@Compendium[swpf-core-rules.swpf-actors.Horse, Light]{Horse}</td>
<td class="centered">30</td>
</tr>
<tr>
<td>@Compendium[swpf-core-rules.swpf-actors.Cart]{Cart} (one beast)</td>
<td class="centered">30</td>
</tr>
<tr>
<td>@Compendium[swpf-core-rules.swpf-actors.Carriage]{Carriage}</td>
<td class="centered">40</td>
</tr>
<tr>
<td>@Compendium[swpf-core-rules.swpf-actors.Wagon, Light]{Wagon} (per beast)</td>
<td class="centered">30</td>
</tr>
<tr>
<td>@Compendium[swpf-core-rules.swpf-actors.Rowboat]{Rowboat}</td>
<td class="centered">24</td>
</tr>
<tr>
<td>@Compendium[swpf-core-rules.swpf-actors.Sailing Ship]{Sailing Ship}*</td>
<td class="centered">30</td>
</tr>
<tr>
<td>Steam Ship*</td>
<td class="centered">40</td>
</tr>
<tr>
<td>@Compendium[swpf-core-rules.swpf-actors.Airship (Dirigible)]{Airship (Dirigible)}</td>
<td class="centered">80</td>
</tr>
<tr>
<td>@Compendium[swpf-core-rules.swpf-actors.Glider]{Glider}</td>
<td class="centered">60</td>
</tr>
</tbody>
</table>

<p>
<em>
*Sailing ships are greatly affected by currents and winds. Strong winds or
currents in the right direction allow them to travel about 60 miles per
day. Poor winds or going against the current reduce them to 20 miles per
day or less.
</em>
</p>

<h2>Encounters</h2>

<p>
If an area is dangerous or lawless, draw a card from the @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore03rules0.JournalEntryPage.03rules000000000]{Action Deck} once
per day (or even two or three times a day in particularly dangerous areas).
A face card or higher represents an encounter, and the card suit can be used
to determine the type.
</p>
<p>
Draw twice more if the card is a Joker and combine the results — such as Enemies and an Obstacle, or Strangers and Treasure.
</p>
<p>
Game Masters are highly encouraged to customize encounters based on their setting.
</p>
<ul>
<li>
<span class="list-heading">Spades — Enemies:</span> Monsters, enemies, or hostile beasts
bar the way. Perhaps they lie in ambush if it’s a popular path, waiting
for the next band of unwary travelers.
</li>
<li>
<span class="list-heading">Hearts — Strangers:</span> The group comes upon neutral or
friendly nonplayer characters such as merchants, lost travelers, a
guide, or even other adventurers.
</li>
<li>
<span class="list-heading">Diamond — Treasure:</span> Somewhere along the way is something
of value — a caravan eager for trade or a forgotten ruin with treasure— and
guardians to protect it!
</li>
<li>
<span class="list-heading">Clubs — Obstacle:</span> The heroes encounter an obstacle of
some kind and must figure out how to circumvent it. Some examples are a
flooded river, a decaying rope bridge, a dangerous whirlpool, etc. The
obstacle might be defended by creatures or enemies as well.
</li>
</ul>

<h2 class="example">Example: Cinderlands</h2>
<p>
Our heroes are traveling across the frontier of Varisia, traversing the burning plains of the Cinderlands.
</p>
<p>
The GM draws a Jack of Clubs and decides the area is currently in the throes of an emberstorm— a dangerous black blizzard of dust and ash. This slows progress to a crawl for hours and makes the characters roll for @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore03rules0.JournalEntryPage.03situationalr00]{Fatigue} from heat and the relentless dusty winds (see the <strong>@UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore04theadv.JournalEntryPage.04hazards0000000]{Hazards}</strong> section).
</p>
<p>
The GM draws again later that day and gets a Queen of Spades. From an unseen burrow under the charred ground, an ankheg surfaces, hungry for fresh prey.
</p>
<div><img src="modules/swpf-core-rules/assets/art/p166_Mokmurian_Fight.webp" alt="wizard blocking golems attack with a shield spell"></div>
</div>
<div class="swpf-core">
<h1 class="wide">Travel</h1>
<p>
Many epic tales feature trips across great expanses. A party may sail the
Inner Sea or ride across the frontier of Varisia or navigate every district
in Absalom.
</p>
<p>
Below are some guidelines to help you figure out how long these journeys
take and what dramatic events might happen along the way.
</p>
<p>
<strong>When to Use These Rules:</strong> If it doesn’t matter how long the
trip takes, skip all this. Narrate the journey, maybe do an
<strong>@UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore04theadv.JournalEntryPage.04interludes0000]{Interlude}</strong>, and get to the next scene. If you
need to know how long the trip takes, or want to insert an obstacle or
encounter of some sort, use the information below as a guideline.
</p>
<p>
<strong>The Basics:</strong> The mode of travel determines how many miles the group makes per day.
</p>

<h2>Travel Times</h2>

<p>
The rates below assume reasonable terrain and weather. Difficult conditions
can drastically decrease progress (or increase it in the case of sailing
with strong winds).
</p>
<table style="width: 50%;">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<th class="main-heading" colspan="2">Average Travel Times</th>
</tr>
<tr>
<th class="sub-heading left">Transport</th>
<th class="sub-heading">Miles/8 hour Day</th>
</tr>
<tr>
<td>Foot</td>
<td class="centered">24</td>
</tr>
<tr>
<td>@Compendium[swpf-core-rules.swpf-actors.Horse, Light]{Horse}</td>
<td class="centered">30</td>
</tr>
<tr>
<td>@Compendium[swpf-core-rules.swpf-actors.Cart]{Cart} (one beast)</td>
<td class="centered">30</td>
</tr>
<tr>
<td>@Compendium[swpf-core-rules.swpf-actors.Carriage]{Carriage}</td>
<td class="centered">40</td>
</tr>
<tr>
<td>@Compendium[swpf-core-rules.swpf-actors.Wagon, Light]{Wagon} (per beast)</td>
<td class="centered">30</td>
</tr>
<tr>
<td>@Compendium[swpf-core-rules.swpf-actors.Rowboat]{Rowboat}</td>
<td class="centered">24</td>
</tr>
<tr>
<td>@Compendium[swpf-core-rules.swpf-actors.Sailing Ship]{Sailing Ship}*</td>
<td class="centered">30</td>
</tr>
<tr>
<td>Steam Ship*</td>
<td class="centered">40</td>
</tr>
<tr>
<td>@Compendium[swpf-core-rules.swpf-actors.Airship (Dirigible)]{Airship (Dirigible)}</td>
<td class="centered">80</td>
</tr>
<tr>
<td>@Compendium[swpf-core-rules.swpf-actors.Glider]{Glider}</td>
<td class="centered">60</td>
</tr>
</tbody>
</table>

<p>
<em>
*Sailing ships are greatly affected by currents and winds. Strong winds or
currents in the right direction allow them to travel about 60 miles per
day. Poor winds or going against the current reduce them to 20 miles per
day or less.
</em>
</p>

<h2>Encounters</h2>

<p>
If an area is dangerous or lawless, draw a card from the @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore03rules0.JournalEntryPage.03rules000000000]{Action Deck} once
per day (or even two or three times a day in particularly dangerous areas).
A face card or higher represents an encounter, and the card suit can be used
to determine the type.
</p>
<p>
Draw twice more if the card is a Joker and combine the results — such as Enemies and an Obstacle, or Strangers and Treasure.
</p>
<p>
Game Masters are highly encouraged to customize encounters based on their setting.
</p>
<ul>
<li>
<span class="list-heading">Spades — Enemies:</span> Monsters, enemies, or hostile beasts
bar the way. Perhaps they lie in ambush if it’s a popular path, waiting
for the next band of unwary travelers.
</li>
<li>
<span class="list-heading">Hearts — Strangers:</span> The group comes upon neutral or
friendly nonplayer characters such as merchants, lost travelers, a
guide, or even other adventurers.
</li>
<li>
<span class="list-heading">Diamond — Treasure:</span> Somewhere along the way is something
of value — a caravan eager for trade or a forgotten ruin with treasure— and
guardians to protect it!
</li>
<li>
<span class="list-heading">Clubs — Obstacle:</span> The heroes encounter an obstacle of
some kind and must figure out how to circumvent it. Some examples are a
flooded river, a decaying rope bridge, a dangerous whirlpool, etc. The
obstacle might be defended by creatures or enemies as well.
</li>
</ul>

<h2 class="example">Example: Cinderlands</h2>
<p>
Our heroes are traveling across the frontier of Varisia, traversing the burning plains of the Cinderlands.
</p>
<p>
The GM draws a Jack of Clubs and decides the area is currently in the throes of an emberstorm— a dangerous black blizzard of dust and ash. This slows progress to a crawl for hours and makes the characters roll for @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore03rules0.JournalEntryPage.03situationalr00]{Fatigue} from heat and the relentless dusty winds (see the <strong>@UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore04theadv.JournalEntryPage.04hazards0000000]{Hazards}</strong> section).
</p>
<p>
The GM draws again later that day and gets a Queen of Spades. From an unseen burrow under the charred ground, an ankheg surfaces, hungry for fresh prey.
</p>
<div><img src="modules/swpf-core-rules/assets/art/p166_Mokmurian_Fight.webp" alt="wizard blocking golems attack with a shield spell"></div>
</div>
a year ago
User avatar None

String updated in the repository
Travel
Travel
a year ago
User avatar None

String updated in the repository
<div class="swpf-core">
<h1 class="wide">The Planes</h1>

<p>
While the world of Golarion exists on the Material Plane, there are many
other realms in other dimensions of reality known as the planes of
existence. Scholars and sages call these, collectively, the Great Beyond.
</p>
<p>
<strong>When to Use These Rules:</strong> Reference these summaries of the
five general types of planes when characters travel to other planes or
encounter creatures from the Great Beyond.
</p>
<p>
<strong>The Basics:</strong> Each plane is effectively its own universe with
its own natural laws. Rare linking points allow travel between the planes.
Some powers also allow — or prohibit — travel between the planes.
</p>

<h2>Material Plane</h2>

<p>
The default plane for play in <cite>Pathfinder for Savage Worlds</cite>, the
Material Plane operates under the same set of natural laws as our real
world. The size and scope of it depends on the GM’s campaign, although the
world of Golarion remains the focus of <em>Savage Pathfinder</em>.
</p>

<h2>Transitive Planes</h2>

<p>
These planes overlap and interact with other planes, especially the
Material. Transitive planes are accessed by powers and special abilities,
allowing for travel to other planes of reality. These are the most common:
</p>
<h3>Astral Plane</h3>
<p>
This silvery void connects the Material and Inner Planes to the outer
Planes. A traveler in the Astral Plane sees it as a vast and empty void
dotted with motes of physical reality intersecting with countless
overlapping planes.
</p>
<h3>Ethereal Plane</h3>
<p>
The Ethereal Plane overlaps with both the Material and the Shadow Plane. A
traveler experiences the Material world as if the world were an
insubstantial ghost. He can move through solid objects without being seen by
creatures in the natural world. Strange creatures dwell here; they can
sometimes influence the real world in mysterious and terrifying ways, such
as a ghost haunting a graveyard.
</p>
<h3>Shadow Plane</h3>
<p>
Best described as a warped "reflection" of the Material Plane, the Shadow
Plane is a grim, colorless "duplicate" of the real world. It is infused with
negative energies and serves as home for creatures such as undead shades.
Plane shifters use the Shadow to cross vast distances across the Material.
</p>

<h2>Inner Planes</h2>

<p>
The Inner Planes contain the building blocks of reality. Each Inner Plane is
made up of a single type of energy or element, with inhabitant of the same
type.
</p>
<h3>Elemental Planes</h3>
<p>
Air, Earth, Fire, Water — each of these elements command their own planes,
with classic Elemental creatures and other strange beings such as genies and
mephits.
</p>
<h3>Energy Planes</h3>
<p>
The energies of the Positive and Negative energy planes infuse reality on
the Material world. The former provides the spark of life, while the latter
harbors the taint of undeath. In general, all characters who use powers draw
energy from these planes as well.
</p>

<h2>Outer Planes</h2>

<p>
Beyond the mortal world, these planes are the various realms of the gods and
the final resting places of the dead from the Material Plane. Characters
with arcane powers often contact beings from these planes for advice,
guidance, and summoned allies.
</p>

<h2>Demiplanes</h2>

<p>
These are extra-dimensional spaces that function like planes but have
measurable size and limited access. Items such as a bag of holding and
portable hole access these strange places.
</p>
</div>
<div class="swpf-core">
<h1 class="wide">The Planes</h1>

<p>
While the world of Golarion exists on the Material Plane, there are many
other realms in other dimensions of reality known as the planes of
existence. Scholars and sages call these, collectively, the Great Beyond.
</p>
<p>
<strong>When to Use These Rules:</strong> Reference these summaries of the
five general types of planes when characters travel to other planes or
encounter creatures from the Great Beyond.
</p>
<p>
<strong>The Basics:</strong> Each plane is effectively its own universe with
its own natural laws. Rare linking points allow travel between the planes.
Some powers also allow — or prohibit — travel between the planes.
</p>

<h2>Material Plane</h2>

<p>
The default plane for play in <cite>Pathfinder for Savage Worlds</cite>, the
Material Plane operates under the same set of natural laws as our real
world. The size and scope of it depends on the GM’s campaign, although the
world of Golarion remains the focus of <em>Savage Pathfinder</em>.
</p>

<h2>Transitive Planes</h2>

<p>
These planes overlap and interact with other planes, especially the
Material. Transitive planes are accessed by powers and special abilities,
allowing for travel to other planes of reality. These are the most common:
</p>
<h3>Astral Plane</h3>
<p>
This silvery void connects the Material and Inner Planes to the outer
Planes. A traveler in the Astral Plane sees it as a vast and empty void
dotted with motes of physical reality intersecting with countless
overlapping planes.
</p>
<h3>Ethereal Plane</h3>
<p>
The Ethereal Plane overlaps with both the Material and the Shadow Plane. A
traveler experiences the Material world as if the world were an
insubstantial ghost. He can move through solid objects without being seen by
creatures in the natural world. Strange creatures dwell here; they can
sometimes influence the real world in mysterious and terrifying ways, such
as a ghost haunting a graveyard.
</p>
<h3>Shadow Plane</h3>
<p>
Best described as a warped "reflection" of the Material Plane, the Shadow
Plane is a grim, colorless "duplicate" of the real world. It is infused with
negative energies and serves as home for creatures such as undead shades.
Plane shifters use the Shadow to cross vast distances across the Material.
</p>

<h2>Inner Planes</h2>

<p>
The Inner Planes contain the building blocks of reality. Each Inner Plane is
made up of a single type of energy or element, with inhabitant of the same
type.
</p>
<h3>Elemental Planes</h3>
<p>
Air, Earth, Fire, Water — each of these elements command their own planes,
with classic Elemental creatures and other strange beings such as genies and
mephits.
</p>
<h3>Energy Planes</h3>
<p>
The energies of the Positive and Negative energy planes infuse reality on
the Material world. The former provides the spark of life, while the latter
harbors the taint of undeath. In general, all characters who use powers draw
energy from these planes as well.
</p>

<h2>Outer Planes</h2>

<p>
Beyond the mortal world, these planes are the various realms of the gods and
the final resting places of the dead from the Material Plane. Characters
with arcane powers often contact beings from these planes for advice,
guidance, and summoned allies.
</p>

<h2>Demiplanes</h2>

<p>
These are extra-dimensional spaces that function like planes but have
measurable size and limited access. Items such as a bag of holding and
portable hole access these strange places.
</p>
</div>
a year ago
User avatar None

String updated in the repository
The Planes
The Planes
a year ago
User avatar None

String updated in the repository
<div class="swpf-core">
<h1 class="wide">Social Conflict</h1>
<p>
Not every conflict is won by the blade. Successful oratory can topple nations.
</p>
<p>
<strong>When to Use These Rules:</strong> Most social exchanges are a simple
skill roll resisted by the appropriate Trait, such as @Compendium[swpf-core-rules.swpf-skills.Intimidation]{Intimidation} or
@Compendium[swpf-core-rules.swpf-skills.Persuasion]{Persuasion} vs. @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore01charac.JournalEntryPage.01traitsummari00]{Spirit}. For longer interactions, such as the back and forth
of a long argument, negotiation, or a legal proceeding, the following system
adds some drama and structure to each side's discussion. (The GM might use a
@UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore04theadv.JournalEntryPage.04dramatictask00]{Dramatic Task} instead if the argument must be won in a hurry!)
</p>
<p>
<strong>The Basics:</strong> Characters make arguments back and forth over
three rounds, roll their appropriate skills, then consult the
<strong>Conflict Results</strong> table (below) to see how well they've
influenced their audience.
</p>

<h2>Conflict Rounds</h2>

<p>
The conflict is broken down into three rounds of conversation, each focusing
on a particular point (or a few highly connected points).
</p>
<p>
During each round, the player roleplays her character's argument and makes a
@Compendium[swpf-core-rules.swpf-skills.Persuasion]{Persuasion} roll opposed by the Spirit of whoever she's trying to convince.
If a rival argues against her, the roll is opposed by his Persuasion instead.
</p>
<p>
Each success and raise by the petitioner grants her an "Influence Token"
(rivals don't gain tokens, they just oppose the petitioner and keep her from
gaining them).
</p>
<p>
<strong>Modifiers:</strong> Persuasion rolls should be modified by the
situation as the GM sees fit. A hero trying to convince a wizard of a fact
within his field rolls the lowest of his Persuasion or @Compendium[swpf-core-rules.swpf-skills.Occult]{Occult}. A
particularly brilliant argument or impassioned roleplaying might add +1 to
+4. An insult or <em>faux pas</em> inflicts a similar penalty.
</p>
<p>
Hindrances should also be considered. Convincing a jury that an @Compendium[swpf-core-rules.swpf-hindrances.Outsider]{Outsider
(Major)} is innocent of a crime, for example, might inflict a −2 penalty.
</p>
<h3>Results</h3>
<p>
At the end of the third round, the speaker looks up her total Influence
Tokens on the <strong>Social Conflict Results</strong> table below.
</p>
<p>
<strong>Trials:</strong> Run trials and similar conflicts from the accuser's
point of view since they must usually prove the accused's guilt. If the
player characters are the defenders, they oppose the prosecution and must
keep them from gaining Influence Tokens with the judge (baron, king,
warlord, etc.).
</p>
<p>
Accusers in a trial must get at least three tokens to convict. Lesser or
greater results indicate the degree of punishment based on local customs and
laws.
</p>

<h2>Example: To Arms!</h2>

<p>
The cleric must convince a baron to send troops to the defense of a
neighboring fiefdom. The barony has warred with his neighbor for generations
so the GM decides that's a −4 penalty to the @Compendium[swpf-core-rules.swpf-skills.Persuasion]{Persuasion} roll.
</p>
<p>
Worse, she's opposed by his slimy wizard, who argues against the idea every round (he opposes her Persuasion rolls).
</p>
<p>
The cleric gets lucky the first round and gets a @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore03rules0.JournalEntryPage.03rules000000000]{raise}. That's two Influence
Tokens. She fails on the second, but gets another raise in the third, for a total of four tokens.
</p>
<p>
The baron agrees but requires payment in land from his neighbor in return for sending part of his army to his rival's defense.
</p>

<table>
<colgroup>
<col style="width: 15%">
<col style="width: 85%">
</colgroup>
<tbody>
<tr>
<th class="main-heading" colspan="2">Social Conflict Results</th>
</tr>
<tr>
<th class="sub-heading left">Tokens</th>
<th class="sub-heading left">Results</th>
</tr>
<tr>
<td>0</td>
<td>
Pleas are denied and negotiations fail. Discussions may reopen if new
information is presented or favors are performed. In a trial, the
defendant is acquitted.
</td>
</tr>
<tr>
<td>1–3</td>
<td>
The target isn't truly convinced, but provides the minimum amount of
support possible. In a trial, the defendant receives the minimum
penalty.
</td>
</tr>
<tr>
<td>4–5</td>
<td>
The arbiter is reasonably convinced or willing to help. He grants the
aid requested, more or less, but only under certain conditions or in
exchange for payment, tasks, favors, etc. The prosecution is
successful with typical sentencing in a trial.
</td>
</tr>
<tr>
<td>6+</td>
<td>
The target is eager to help or agree. He gives more than expected in a
negotiation or provides more support than requested. A defendant is
convicted with the maximum penalty.
</td>
</tr>
</tbody>
</table>
</div>
<div class="swpf-core">
<h1 class="wide">Social Conflict</h1>
<p>
Not every conflict is won by the blade. Successful oratory can topple nations.
</p>
<p>
<strong>When to Use These Rules:</strong> Most social exchanges are a simple
skill roll resisted by the appropriate Trait, such as @Compendium[swpf-core-rules.swpf-skills.Intimidation]{Intimidation} or
@Compendium[swpf-core-rules.swpf-skills.Persuasion]{Persuasion} vs. @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore01charac.JournalEntryPage.01traitsummari00]{Spirit}. For longer interactions, such as the back and forth
of a long argument, negotiation, or a legal proceeding, the following system
adds some drama and structure to each side's discussion. (The GM might use a
@UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore04theadv.JournalEntryPage.04dramatictask00]{Dramatic Task} instead if the argument must be won in a hurry!)
</p>
<p>
<strong>The Basics:</strong> Characters make arguments back and forth over
three rounds, roll their appropriate skills, then consult the
<strong>Conflict Results</strong> table (below) to see how well they've
influenced their audience.
</p>

<h2>Conflict Rounds</h2>

<p>
The conflict is broken down into three rounds of conversation, each focusing
on a particular point (or a few highly connected points).
</p>
<p>
During each round, the player roleplays her character's argument and makes a
@Compendium[swpf-core-rules.swpf-skills.Persuasion]{Persuasion} roll opposed by the Spirit of whoever she's trying to convince.
If a rival argues against her, the roll is opposed by his Persuasion instead.
</p>
<p>
Each success and raise by the petitioner grants her an "Influence Token"
(rivals don't gain tokens, they just oppose the petitioner and keep her from
gaining them).
</p>
<p>
<strong>Modifiers:</strong> Persuasion rolls should be modified by the
situation as the GM sees fit. A hero trying to convince a wizard of a fact
within his field rolls the lowest of his Persuasion or @Compendium[swpf-core-rules.swpf-skills.Occult]{Occult}. A
particularly brilliant argument or impassioned roleplaying might add +1 to
+4. An insult or <em>faux pas</em> inflicts a similar penalty.
</p>
<p>
Hindrances should also be considered. Convincing a jury that an @Compendium[swpf-core-rules.swpf-hindrances.Outsider]{Outsider
(Major)} is innocent of a crime, for example, might inflict a −2 penalty.
</p>
<h3>Results</h3>
<p>
At the end of the third round, the speaker looks up her total Influence
Tokens on the <strong>Social Conflict Results</strong> table below.
</p>
<p>
<strong>Trials:</strong> Run trials and similar conflicts from the accuser's
point of view since they must usually prove the accused's guilt. If the
player characters are the defenders, they oppose the prosecution and must
keep them from gaining Influence Tokens with the judge (baron, king,
warlord, etc.).
</p>
<p>
Accusers in a trial must get at least three tokens to convict. Lesser or
greater results indicate the degree of punishment based on local customs and
laws.
</p>

<h2>Example: To Arms!</h2>

<p>
The cleric must convince a baron to send troops to the defense of a
neighboring fiefdom. The barony has warred with his neighbor for generations
so the GM decides that's a −4 penalty to the @Compendium[swpf-core-rules.swpf-skills.Persuasion]{Persuasion} roll.
</p>
<p>
Worse, she's opposed by his slimy wizard, who argues against the idea every round (he opposes her Persuasion rolls).
</p>
<p>
The cleric gets lucky the first round and gets a @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore03rules0.JournalEntryPage.03rules000000000]{raise}. That's two Influence
Tokens. She fails on the second, but gets another raise in the third, for a total of four tokens.
</p>
<p>
The baron agrees but requires payment in land from his neighbor in return for sending part of his army to his rival's defense.
</p>

<table>
<colgroup>
<col style="width: 15%">
<col style="width: 85%">
</colgroup>
<tbody>
<tr>
<th class="main-heading" colspan="2">Social Conflict Results</th>
</tr>
<tr>
<th class="sub-heading left">Tokens</th>
<th class="sub-heading left">Results</th>
</tr>
<tr>
<td>0</td>
<td>
Pleas are denied and negotiations fail. Discussions may reopen if new
information is presented or favors are performed. In a trial, the
defendant is acquitted.
</td>
</tr>
<tr>
<td>1–3</td>
<td>
The target isn't truly convinced, but provides the minimum amount of
support possible. In a trial, the defendant receives the minimum
penalty.
</td>
</tr>
<tr>
<td>4–5</td>
<td>
The arbiter is reasonably convinced or willing to help. He grants the
aid requested, more or less, but only under certain conditions or in
exchange for payment, tasks, favors, etc. The prosecution is
successful with typical sentencing in a trial.
</td>
</tr>
<tr>
<td>6+</td>
<td>
The target is eager to help or agree. He gives more than expected in a
negotiation or provides more support than requested. A defendant is
convicted with the maximum penalty.
</td>
</tr>
</tbody>
</table>
</div>
a year ago
User avatar None

String updated in the repository
Social Conflict
Social Conflict
a year ago
User avatar None

String updated in the repository
<div class="swpf-core">
<h1 class="wide">Quick Encounters</h1>

<p>
Sometimes the Game Master may want to quickly sum up an encounter rather
than track every action round by round. "Quick Encounters" resolve these
kinds of situations with good collaborative storytelling, tension, and risk.
</p>
<p>
<strong>When to Use These Rules:</strong> Use Quick Encounters when
you're pressed for time, the group isn't as interested in tactical fights,
or they do something the GM isn't prepared for, like infiltrating an enemy
compound she hasn't yet detailed.
</p>
<p>
<strong>The Basics:</strong> Characters make a skill roll based on the type
of encounter and their goal and interpret the results narratively with the
Game Master.
</p>

<h2>Encounter Types</h2>

<p>
No @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore03rules0.JournalEntryPage.03rules000000000]{Action Cards} are dealt in a Quick Encounter. Instead, the GM describes
the scene, and then the players agree on a general plan and what their
characters will do to resolve the situation.
</p>
<p>
Once all the players state their intent, they pick the skill that best
represents their actions during the encounter and roll. Here are some common
examples:
</p>
<ul>
<li><span class="list-heading">Combat:</span> @Compendium[swpf-core-rules.swpf-skills.Fighting]{Fighting}, @Compendium[swpf-core-rules.swpf-skills.Shooting]{Shooting}, arcane skill.</li>
<li>
<span class="list-heading">Crisis:</span> @Compendium[swpf-core-rules.swpf-skills.Athletics]{Athletics}, @Compendium[swpf-core-rules.swpf-skills.Persuasion]{Persuasion} (to calm bystanders), @Compendium[swpf-core-rules.swpf-skills.Repair]{Repair}.
</li>
<li><span class="list-heading">Heist:</span> @Compendium[swpf-core-rules.swpf-skills.Notice]{Notice}, @Compendium[swpf-core-rules.swpf-skills.Persuasion]{Persuasion}, @Compendium[swpf-core-rules.swpf-skills.Stealth]{Stealth}, @Compendium[swpf-core-rules.swpf-skills.Thievery]{Thievery}.</li>
<li>
<span class="list-heading">Mission:</span> @Compendium[swpf-core-rules.swpf-skills.Battle]{Battle}, @Compendium[swpf-core-rules.swpf-skills.Boating]{Boating}, @Compendium[swpf-core-rules.swpf-skills.Fighting]{Fighting}, @Compendium[swpf-core-rules.swpf-skills.Persuasion]{Persuasion}, @Compendium[swpf-core-rules.swpf-skills.Shooting]{Shooting},
@Compendium[swpf-core-rules.swpf-skills.Stealth]{Stealth}.
</li>
<li><span class="list-heading">Trek:</span> @Compendium[swpf-core-rules.swpf-skills.Common Knowledge]{Common Knowledge}, @Compendium[swpf-core-rules.swpf-skills.Notice]{Notice}, @Compendium[swpf-core-rules.swpf-skills.Survival]{Survival}.</li>
</ul>
<p>
<strong>Modifiers:</strong> The GM should assign modifiers based on the
situation. If the heroes greatly outnumber their opposition, pursue much
slower prey, have prior experience with the obstacles in their path, or
special equipment to deal with hazards, the roll might be made at +1 to +4.
</p>
<p>
Very difficult encounters, such as powerful foes (relative to the party),
faster prey, or extreme conditions inflict a −1 to −4 penalty.
</p>
<h3>Turn Order &amp; Critical Actions</h3>
<p>
Players can go in whatever order they want in a Quick Encounter. This might
be important if some of their actions are dependent on someone else's. In a
heist, for example, the group might depend on a smooth-talker to gather
information about the target's security before the thief attempts to break
in. Similarly, a battle commander might need to send a scout across enemy
lines before sending in a team to sabotage the enemy's war engine.
</p>
<p>
Resolve these kinds of actions in the order that makes sense, and allow
those who come after to change their own plans as the situation changes.
</p>
<p>
If a critical task is failed, the GM must decide if it stops the encounter
or simply complicates it (perhaps inflicting a penalty to everyone else's
roll). In the heist example above, for example, maybe the charmer gets the
information but tips off someone who adds extra sentries, inflicting a −2
penalty to @Compendium[swpf-core-rules.swpf-skills.Stealth]{Stealth} or @Compendium[swpf-core-rules.swpf-skills.Thievery]{Thievery} rolls. Likewise, the scout might find the war
engine's location but the enemy moves the device shortly thereafter, adding
the need for additional reconnaissance for the team of saboteurs.
</p>
<p>
These kinds of complications might also mean resolving the encounter in
multiple stages instead of one roll as the heroes must react to the changing
circumstances (see <strong>Staged Encounters,</strong> below).
</p>
<h3>Staged Encounters</h3>
<p>
Quick Encounters are typically a single die roll followed by some narration
between the GM and the players. But some encounters might need additional
rounds to better reflect the results or any new information or events that
come to light.
</p>
<p>
If the heist to break into a wizard's tower and steal a powerful occult
artifact goes badly, for example, the next stage might become a crisis when
the tower suddenly bursts into supernatural flames. That might then lead to
a combat encounter as an artifact in the wizard's study breaks and releases
an angry djinn!
</p>
<p>
The beauty of staged encounters is their ability to handle complex problems
when the constraints of time or larger narrative require a speedy
resolution.
</p>

<h2>Encounter Results</h2>

<p>
Once each player has determined her skill and any modifiers, she rolls the
dice and works with the Game Master to narrate the details based on the
total, the situation, and the other players' actions.
</p>
<h3>Dangerous Encounters</h3>
<p>
If a character fails his roll in a dangerous situation he takes a @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore03rules0.JournalEntryPage.03combat00000000]{Wound} (or
d4 Wounds with a @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore03rules0.JournalEntryPage.03rules000000000]{Critical Failure}). If he's the driver of a vehicle, it
takes a Wound (or d4 with a Critical Failure). Wounds may be @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore03rules0.JournalEntryPage.03combat00000000]{Soaked} as
usual.
</p>
<p>
Success means the hero emerges with only <strong>@UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore04theadv.JournalEntryPage.04hazards0000000]{Bumps and Bruises}</strong>, and a @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore03rules0.JournalEntryPage.03rules000000000]{raise} means he escapes unscathed.
</p>
<h3>Nonlethal Encounters</h3>
<p>
If the encounter isn't physically dangerous, failure means the hero doesn't
contribute to the party's overall success somehow. @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore03rules0.JournalEntryPage.03rules000000000]{Critical Failure} means
she suffers social stigma, loses or breaks a piece of vital equipment, is
positively identified, or gets the wrong information. This likely means
moving on to a second stage of the encounter as she deals with the fallout
of her errors.
</p>
<h3>Success &amp; Failure</h3>
<p>
In general, narration and individual actions determine the success or
failure of an encounter. If the smooth-talker can't learn the habits of the
sentries, for example, and the GM decides this fact shuts down the operation
rather than complicating it, the encounter fails. In other words, let the
story tell the tale.
</p>
<p>
In a more dynamic situation such as combat, assume the group "wins" if there
are at least as many total successes (one for each success and raise) as
there are player characters. They get the information, drive off their foes,
complete the mission, or avert (or escape) the crisis. @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore03rules0.JournalEntryPage.03situationalr00]{Support} rolls
<em>don't</em> count as successes.
</p>
<p>
If there are fewer successes than player characters, they fail. Specifics
are up to the Game Master, but this might mean the party has to fall back or
retreat from their foes, their prey escapes, they don't get the object or
information they sought, they survive the crisis but can't save most of the
bystanders, and so on.
</p>
<p>
If they can try again, the GM should "reset" the encounter with the new
narrative so the group has to come up with a new plan. And of course, their
foes are likely on to them now!
</p>
<h3>Ammo &amp; Power Points</h3>
<p>
Use the rules for <strong>Ammo &amp; Power Points</strong> under <strong>@UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore04theadv.JournalEntryPage.04massbattles000]{Mass Battles}</strong> for combat encounters if desired. Otherwise the player and GM can just decide what resources were consumed in the encounter.
</p>

<h2 class="example">Example: Night on the prowl</h2>

<p>
Our heroes must break into a nobleman's library, steal an ancient book, and stop an evil conspiracy that threatens all of Golarion.
</p>
<p>
The group decides to play out the break-in as a Quick Encounter. The rogue
plans to use @Compendium[swpf-core-rules.swpf-skills.Thievery]{Thievery} to break into the library, take the manuscript, then
escape out the back. The bard supports her with a diversionary recital in the town square.
</p>
<p>
The GM decides the rogue's Thievery roll is at −2 to get into the library.
The bard gets a success with his @Compendium[swpf-core-rules.swpf-skills.Performance]{Performance} to @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore03rules0.JournalEntryPage.03situationalr00]{Support}. He adds +1 to his
friend's roll.
</p>
<p>
The rogue manages a single success, but since there are two player characters and the rules say they need at least as many successes as there are characters, they fail.
</p>
<p>
The GM says three of the nobleman's guards are alerted by the pair's
actions. The heroes can continue if they want, but the encounter is now more
difficult (−2). The GM also says it's now a Dangerous Encounter as the
guards are armed and nervous.
</p>
<p>
With the fate of Golarion at stake, the party agrees to press on. The rogue
now uses @Compendium[swpf-core-rules.swpf-skills.Stealth]{Stealth} to avoid the guards. The bard disguises himself and knocks
on the door, pretending to be lost! The GM tells the bard to use Performance
for this Support roll. He rolls a 21! Both characters are successful, so the
ancient manuscript is secured!
</p>
</div>
<div class="swpf-core">
<h1 class="wide">Quick Encounters</h1>

<p>
Sometimes the Game Master may want to quickly sum up an encounter rather
than track every action round by round. "Quick Encounters" resolve these
kinds of situations with good collaborative storytelling, tension, and risk.
</p>
<p>
<strong>When to Use These Rules:</strong> Use Quick Encounters when
you're pressed for time, the group isn't as interested in tactical fights,
or they do something the GM isn't prepared for, like infiltrating an enemy
compound she hasn't yet detailed.
</p>
<p>
<strong>The Basics:</strong> Characters make a skill roll based on the type
of encounter and their goal and interpret the results narratively with the
Game Master.
</p>

<h2>Encounter Types</h2>

<p>
No @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore03rules0.JournalEntryPage.03rules000000000]{Action Cards} are dealt in a Quick Encounter. Instead, the GM describes
the scene, and then the players agree on a general plan and what their
characters will do to resolve the situation.
</p>
<p>
Once all the players state their intent, they pick the skill that best
represents their actions during the encounter and roll. Here are some common
examples:
</p>
<ul>
<li><span class="list-heading">Combat:</span> @Compendium[swpf-core-rules.swpf-skills.Fighting]{Fighting}, @Compendium[swpf-core-rules.swpf-skills.Shooting]{Shooting}, arcane skill.</li>
<li>
<span class="list-heading">Crisis:</span> @Compendium[swpf-core-rules.swpf-skills.Athletics]{Athletics}, @Compendium[swpf-core-rules.swpf-skills.Persuasion]{Persuasion} (to calm bystanders), @Compendium[swpf-core-rules.swpf-skills.Repair]{Repair}.
</li>
<li><span class="list-heading">Heist:</span> @Compendium[swpf-core-rules.swpf-skills.Notice]{Notice}, @Compendium[swpf-core-rules.swpf-skills.Persuasion]{Persuasion}, @Compendium[swpf-core-rules.swpf-skills.Stealth]{Stealth}, @Compendium[swpf-core-rules.swpf-skills.Thievery]{Thievery}.</li>
<li>
<span class="list-heading">Mission:</span> @Compendium[swpf-core-rules.swpf-skills.Battle]{Battle}, @Compendium[swpf-core-rules.swpf-skills.Boating]{Boating}, @Compendium[swpf-core-rules.swpf-skills.Fighting]{Fighting}, @Compendium[swpf-core-rules.swpf-skills.Persuasion]{Persuasion}, @Compendium[swpf-core-rules.swpf-skills.Shooting]{Shooting},
@Compendium[swpf-core-rules.swpf-skills.Stealth]{Stealth}.
</li>
<li><span class="list-heading">Trek:</span> @Compendium[swpf-core-rules.swpf-skills.Common Knowledge]{Common Knowledge}, @Compendium[swpf-core-rules.swpf-skills.Notice]{Notice}, @Compendium[swpf-core-rules.swpf-skills.Survival]{Survival}.</li>
</ul>
<p>
<strong>Modifiers:</strong> The GM should assign modifiers based on the
situation. If the heroes greatly outnumber their opposition, pursue much
slower prey, have prior experience with the obstacles in their path, or
special equipment to deal with hazards, the roll might be made at +1 to +4.
</p>
<p>
Very difficult encounters, such as powerful foes (relative to the party),
faster prey, or extreme conditions inflict a −1 to −4 penalty.
</p>
<h3>Turn Order &amp; Critical Actions</h3>
<p>
Players can go in whatever order they want in a Quick Encounter. This might
be important if some of their actions are dependent on someone else's. In a
heist, for example, the group might depend on a smooth-talker to gather
information about the target's security before the thief attempts to break
in. Similarly, a battle commander might need to send a scout across enemy
lines before sending in a team to sabotage the enemy's war engine.
</p>
<p>
Resolve these kinds of actions in the order that makes sense, and allow
those who come after to change their own plans as the situation changes.
</p>
<p>
If a critical task is failed, the GM must decide if it stops the encounter
or simply complicates it (perhaps inflicting a penalty to everyone else's
roll). In the heist example above, for example, maybe the charmer gets the
information but tips off someone who adds extra sentries, inflicting a −2
penalty to @Compendium[swpf-core-rules.swpf-skills.Stealth]{Stealth} or @Compendium[swpf-core-rules.swpf-skills.Thievery]{Thievery} rolls. Likewise, the scout might find the war
engine's location but the enemy moves the device shortly thereafter, adding
the need for additional reconnaissance for the team of saboteurs.
</p>
<p>
These kinds of complications might also mean resolving the encounter in
multiple stages instead of one roll as the heroes must react to the changing
circumstances (see <strong>Staged Encounters,</strong> below).
</p>
<h3>Staged Encounters</h3>
<p>
Quick Encounters are typically a single die roll followed by some narration
between the GM and the players. But some encounters might need additional
rounds to better reflect the results or any new information or events that
come to light.
</p>
<p>
If the heist to break into a wizard's tower and steal a powerful occult
artifact goes badly, for example, the next stage might become a crisis when
the tower suddenly bursts into supernatural flames. That might then lead to
a combat encounter as an artifact in the wizard's study breaks and releases
an angry djinn!
</p>
<p>
The beauty of staged encounters is their ability to handle complex problems
when the constraints of time or larger narrative require a speedy
resolution.
</p>

<h2>Encounter Results</h2>

<p>
Once each player has determined her skill and any modifiers, she rolls the
dice and works with the Game Master to narrate the details based on the
total, the situation, and the other players' actions.
</p>
<h3>Dangerous Encounters</h3>
<p>
If a character fails his roll in a dangerous situation he takes a @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore03rules0.JournalEntryPage.03combat00000000]{Wound} (or
d4 Wounds with a @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore03rules0.JournalEntryPage.03rules000000000]{Critical Failure}). If he's the driver of a vehicle, it
takes a Wound (or d4 with a Critical Failure). Wounds may be @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore03rules0.JournalEntryPage.03combat00000000]{Soaked} as
usual.
</p>
<p>
Success means the hero emerges with only <strong>@UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore04theadv.JournalEntryPage.04hazards0000000]{Bumps and Bruises}</strong>, and a @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore03rules0.JournalEntryPage.03rules000000000]{raise} means he escapes unscathed.
</p>
<h3>Nonlethal Encounters</h3>
<p>
If the encounter isn't physically dangerous, failure means the hero doesn't
contribute to the party's overall success somehow. @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore03rules0.JournalEntryPage.03rules000000000]{Critical Failure} means
she suffers social stigma, loses or breaks a piece of vital equipment, is
positively identified, or gets the wrong information. This likely means
moving on to a second stage of the encounter as she deals with the fallout
of her errors.
</p>
<h3>Success &amp; Failure</h3>
<p>
In general, narration and individual actions determine the success or
failure of an encounter. If the smooth-talker can't learn the habits of the
sentries, for example, and the GM decides this fact shuts down the operation
rather than complicating it, the encounter fails. In other words, let the
story tell the tale.
</p>
<p>
In a more dynamic situation such as combat, assume the group "wins" if there
are at least as many total successes (one for each success and raise) as
there are player characters. They get the information, drive off their foes,
complete the mission, or avert (or escape) the crisis. @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore03rules0.JournalEntryPage.03situationalr00]{Support} rolls
<em>don't</em> count as successes.
</p>
<p>
If there are fewer successes than player characters, they fail. Specifics
are up to the Game Master, but this might mean the party has to fall back or
retreat from their foes, their prey escapes, they don't get the object or
information they sought, they survive the crisis but can't save most of the
bystanders, and so on.
</p>
<p>
If they can try again, the GM should "reset" the encounter with the new
narrative so the group has to come up with a new plan. And of course, their
foes are likely on to them now!
</p>
<h3>Ammo &amp; Power Points</h3>
<p>
Use the rules for <strong>Ammo &amp; Power Points</strong> under <strong>@UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore04theadv.JournalEntryPage.04massbattles000]{Mass Battles}</strong> for combat encounters if desired. Otherwise the player and GM can just decide what resources were consumed in the encounter.
</p>

<h2 class="example">Example: Night on the prowl</h2>

<p>
Our heroes must break into a nobleman's library, steal an ancient book, and stop an evil conspiracy that threatens all of Golarion.
</p>
<p>
The group decides to play out the break-in as a Quick Encounter. The rogue
plans to use @Compendium[swpf-core-rules.swpf-skills.Thievery]{Thievery} to break into the library, take the manuscript, then
escape out the back. The bard supports her with a diversionary recital in the town square.
</p>
<p>
The GM decides the rogue's Thievery roll is at −2 to get into the library.
The bard gets a success with his @Compendium[swpf-core-rules.swpf-skills.Performance]{Performance} to @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore03rules0.JournalEntryPage.03situationalr00]{Support}. He adds +1 to his
friend's roll.
</p>
<p>
The rogue manages a single success, but since there are two player characters and the rules say they need at least as many successes as there are characters, they fail.
</p>
<p>
The GM says three of the nobleman's guards are alerted by the pair's
actions. The heroes can continue if they want, but the encounter is now more
difficult (−2). The GM also says it's now a Dangerous Encounter as the
guards are armed and nervous.
</p>
<p>
With the fate of Golarion at stake, the party agrees to press on. The rogue
now uses @Compendium[swpf-core-rules.swpf-skills.Stealth]{Stealth} to avoid the guards. The bard disguises himself and knocks
on the door, pretending to be lost! The GM tells the bard to use Performance
for this Support roll. He rolls a 21! Both characters are successful, so the
ancient manuscript is secured!
</p>
</div>
a year ago
User avatar None

String updated in the repository
Quick Encounters
Quick Encounters
a year ago
Browse all translation changes