Source strings
| 130 | Strings |
|
100% | |
|---|---|---|---|---|
| 135,109 | Words |
|
100% | |
| 1,284,730 | Characters |
|
100% |
This translation is being used as source strings within this component.
| 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/bnp800/swade_compendium_chn |
|---|---|
| Project maintainers |
 Kuroni
 bnp800
|
| Translation license | GNU General Public License v3.0 or later |
| Translation process |
|
| Source code repository |
https://github.com/bnp800/swade_compendium_chn
|
| Repository branch | main |
| Last remote commit |
remove swade.css dependency
d77553d
bnp800 authored 9 months ago |
| Last commit in Weblate |
remove swade.css dependency
d77553d
bnp800 authored 9 months ago |
| Weblate repository |
http://weblate.ashfinder.com/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 | Feb. 5, 2024, 2:07 p.m. |
| Last author | 白菜他爸 |
an hour 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 |
Quick numbers
and previous 30 days
Trends of last 30 days
—
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
+100%
—
Contributors
—
|
bnp800
Resource updated |
|
 None
String updated in the repository |
<div class="swpf-core">
<div class="chapter-heading"> <h1>Powers</h1> <figure class="chapter-number"> <span>Chapter Five</span> </figure> </div> <p class="drop-cap"> Magic is everywhere in <em>Savage </em><em>Pathfinder</em>. Whether it’s hidden occult lore practiced by dark cultists, the righteous rituals of clerics, or the potent spells of sorcerers and wizards, these rules handle it all in one simple system. </p> <p> We call all of these effects “powers.” They work the same from game to game, but the particular use, modifiers, and @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore05powers.JournalEntryPage.05trappings00000]{Trappings} give the same core powers endless variations. </p> <p> Characters gain access to magical powers by taking an Arcane Background, either @Compendium[swpf-core-rules.swpf-edges.Arcane Background (Magic)]{Magic} or @Compendium[swpf-core-rules.swpf-edges.Arcane Background (Miracles)]{Miracles} or one of the more specialized Class Edges. </p> <p> Each type of Arcane Background has the following entries, listed in its description, and may have additional abilities or drawbacks as well. </p> <ul> <li> <strong>Arcane Skill:</strong> This is the skill you roll to activate your powers. Buy it just like any other skill. </li> <li> <strong>Starting Powers:</strong> This is the number of powers a hero starts with when she takes an Arcane Background. Additional powers may be learned with the <strong> @Compendium[swpf-core-rules.swpf-edges.New Powers]{New Powers} </strong> Edge. </li> <li> <strong>Power Points:</strong> The number of Power Points the character starts with. A hero increases Power Points by taking the <strong> @Compendium[swpf-core-rules.swpf-edges.Power Points]{Power Points} </strong> Edge. </li> <li> <strong>Available Powers:</strong> The list of powers characters with that Arcane Background may take. </li> </ul> <h3>Detect Magic</h3> <p> In the magically-charged world of Golarion, any character with an Arcane Background can sense magical or divine auras within 5” (10 yards), unless they are magically concealed. This is an @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore03rules0.JournalEntryPage.03combat00000000]{action}. </p> <p> Detecting magic at a greater range or gaining specific information requires the <em>detect arcana</em> spell, which can also be used to reveal items or beings protected by <em>conceal arcana.</em> See <em> @Compendium[swpf-core-rules.swpf-powers.Detect/Conceal Arcana]{detect/conceal arcana} </em> </p> <p> Identifying magic items requires a @Compendium[swpf-core-rules.swpf-skills.Common Knowledge]{Common Knowledge} roll for everyday items like healing potions. More obscure items require an @Compendium[swpf-core-rules.swpf-skills.Occult]{Occult} roll. </p> <aside class="sidebar"> <h1>Multiple Arcane Backgrounds</h1> <p> If a character takes a new Arcane Background, she gets a d4 in its arcane skill if she doesn’t already have it and any new powers it grants. If she already has an Arcane Background or Mystic Powers, she doesn’t get new @Compendium[swpf-core-rules.swpf-edges.Power Points]{Power Points}, she must share her existing pool with all her Arcane Backgrounds and Mystic Powers. Otherwise, she also gets the Power Points listed for the Edge. </p> <p>Class Edge abilities apply only to spells provided by that class.</p> </aside> </div>
<div class="swpf-core">
<div class="chapter-heading"> <h1>Powers</h1> <figure class="chapter-number"> <span>Chapter Five</span> </figure> </div> <p class="drop-cap"> Magic is everywhere in <em>Savage </em><em>Pathfinder</em>. Whether it’s hidden occult lore practiced by dark cultists, the righteous rituals of clerics, or the potent spells of sorcerers and wizards, these rules handle it all in one simple system. </p> <p> We call all of these effects “powers.” They work the same from game to game, but the particular use, modifiers, and @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore05powers.JournalEntryPage.05trappings00000]{Trappings} give the same core powers endless variations. </p> <p> Characters gain access to magical powers by taking an Arcane Background, either @Compendium[swpf-core-rules.swpf-edges.Arcane Background (Magic)]{Magic} or @Compendium[swpf-core-rules.swpf-edges.Arcane Background (Miracles)]{Miracles} or one of the more specialized Class Edges. </p> <p> Each type of Arcane Background has the following entries, listed in its description, and may have additional abilities or drawbacks as well. </p> <ul> <li> <strong>Arcane Skill:</strong> This is the skill you roll to activate your powers. Buy it just like any other skill. </li> <li> <strong>Starting Powers:</strong> This is the number of powers a hero starts with when she takes an Arcane Background. Additional powers may be learned with the <strong> @Compendium[swpf-core-rules.swpf-edges.New Powers]{New Powers} </strong> Edge. </li> <li> <strong>Power Points:</strong> The number of Power Points the character starts with. A hero increases Power Points by taking the <strong> @Compendium[swpf-core-rules.swpf-edges.Power Points]{Power Points} </strong> Edge. </li> <li> <strong>Available Powers:</strong> The list of powers characters with that Arcane Background may take. </li> </ul> <h3>Detect Magic</h3> <p> In the magically-charged world of Golarion, any character with an Arcane Background can sense magical or divine auras within 5” (10 yards), unless they are magically concealed. This is an @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore03rules0.JournalEntryPage.03combat00000000]{action}. </p> <p> Detecting magic at a greater range or gaining specific information requires the <em>detect arcana</em> spell, which can also be used to reveal items or beings protected by <em>conceal arcana.</em> See <em> @Compendium[swpf-core-rules.swpf-powers.Detect/Conceal Arcana]{detect/conceal arcana} </em> </p> <p> Identifying magic items requires a @Compendium[swpf-core-rules.swpf-skills.Common Knowledge]{Common Knowledge} roll for everyday items like healing potions. More obscure items require an @Compendium[swpf-core-rules.swpf-skills.Occult]{Occult} roll. </p> <aside class="sidebar"> <h1>Multiple Arcane Backgrounds</h1> <p> If a character takes a new Arcane Background, she gets a d4 in its arcane skill if she doesn’t already have it and any new powers it grants. If she already has an Arcane Background or Mystic Powers, she doesn’t get new @Compendium[swpf-core-rules.swpf-edges.Power Points]{Power Points}, she must share her existing pool with all her Arcane Backgrounds and Mystic Powers. Otherwise, she also gets the Power Points listed for the Edge. </p> <p>Class Edge abilities apply only to spells provided by that class.</p> </aside> </div> |
|
None
String updated in the repository |
Powers
Powers
|
|
bnp800
Resource updated |
The “
en-US/swpf-core-rules.swpf-rules.json” file was changed.
10 months ago
|
|
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">
<col> <th class="main-heading" colspan="2">Average Travel Times</th> <tr> <tr> <th class="sub-heading left">Transport</th> <tr> <tr> <td>Foot</td> <tr> <tr> <td>@Compendium[swpf-core-rules.swpf-actors.Horse, Light]{Horse}</td> <tr> <tr> <td>@Compendium[swpf-core-rules.swpf-actors.Cart]{Cart} (one beast)</td> <tr> <tr> <td>@Compendium[swpf-core-rules.swpf-actors.Carriage]{Carriage}</td> <tr> <tr> <td>@Compendium[swpf-core-rules.swpf-actors.Wagon, Light]{Wagon} (per beast)</td> <tr> <tr> <td>@Compendium[swpf-core-rules.swpf-actors.Rowboat]{Rowboat}</td> <tr> <tr> <td>@Compendium[swpf-core-rules.swpf-actors.Sailing Ship]{Sailing Ship}*</td> <tr> <tr> <td>Steam Ship*</td> <tr> <tr> <td>@Compendium[swpf-core-rules.swpf-actors.Airship (Dirigible)]{Airship (Dirigible)}</td> <tr> <tr> <td>@Compendium[swpf-core-rules.swpf-actors.Glider]{Glider}</td> <p> <em> <p> <em> *Sailing ships are greatly affected by currents and winds. Strong winds or </div> |
|
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">
</div> |
|
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">
<th class="main-heading" colspan="2">Social Conflict Results</th> <tr> <tr> <th class="sub-heading left">Tokens</th> <tr> <td>0</td> <td> <tr> <td>0</td> <td> Pleas are denied and negotiations fail. Discussions may reopen if new </tr> <tr> <td>1–3</td> <td> </tr> <tr> <td>1–3</td> <td> The target isn't truly convinced, but provides the minimum amount of </td> </tr> <tr> <td>4–5</td> <td> </td> </tr> <tr> <td>4–5</td> <td> The arbiter is reasonably convinced or willing to help. He grants the </tr> <tr> <td>6+</td> <td> </tr> <tr> <td>6+</td> <td> The target is eager to help or agree. He gives more than expected in a </tr> </div> |
|
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 & 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 & 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 & Power Points</h3> <p> Use the rules for <strong>Ammo & 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">
</div> |
|
None
String updated in the repository |
<div class="swpf-core">
<h1 class="wide">Networking</h1> <p> Pathfinders often need to find information or ask for favors. You can roleplay these encounters out, or you can allow them to use their skills in a "macro" sense — summing up hours of effort with a single roll. </p> <p> @Compendium[swpf-core-rules.swpf-skills.Persuasion]{Persuasion} is the nice way of interacting with one’s contacts. The flip side of the coin is @Compendium[swpf-core-rules.swpf-skills.Intimidation]{Intimidation}. Either can get the job done but in slightly different ways, as shown below. </p> <p> <strong>When to Use These Rules:</strong> When the player characters want to ask around town for favors or information. </p> <p> <strong>The Basics:</strong> Characters use @Compendium[swpf-core-rules.swpf-skills.Persuasion]{Persuasion} or @Compendium[swpf-core-rules.swpf-skills.Intimidation]{Intimidation} to gather favors or information. </p> <h3>Persuasion (The Nice Way)</h3> <p> Characters use @Compendium[swpf-core-rules.swpf-skills.Persuasion]{Persuasion} to socialize within their various social circles for information or favors. When used in this way, Persuasion isn’t a single exchange but several hours of networking, hobnobbing, carousing, drinks, gifts, bribes, or entertaining. This might represent time roaming a marketplace, a series of meetings with important people, or an evening of food and drink. </p> <p> Success grants most of what the character wants, though it may take a while, cost some money, or require a favor in return. A @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore03rules0.JournalEntryPage.03rules000000000]{raise} either gets more of whatever he was looking for, or at a lower cost. </p> <p> Failure means the hero’s efforts are in vain. A @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore03rules0.JournalEntryPage.03rules000000000]{Critical Failure} means he’s cut off from that particular group for a while (up to the GM but typically about a week). </p> <p> <strong>Money Talks:</strong> You can catch more flies with honey than vinegar, the saying goes. A character with a little lucre to spread around gets a @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore03rules0.JournalEntryPage.03rules000000000]{reroll} on her networking attempt, spending money on better bribes, gifts, or wining and dining her contacts. </p> <p> The amount required is up to the GM, the location, and the nature of the contact(s) she interacts with. As a rule of thumb, use the expenses listed under <span>@UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore04theadv.JournalEntryPage.04downtime000000]{Carousing}</span> and modify as appropriate from there. </p> <h3>Intimidation (The Not-so-Nice Way)</h3> <p> @Compendium[swpf-core-rules.swpf-skills.Intimidation]{Intimidation} can also be used to gather information, call in favors, or make demands, but it’s a little less savory. </p> <p> Each attempt to "work the streets" takes several hours of threats and general unpleasantness, rousting the local populace for whatever the hero needs. </p> <p> Success grants the character most of what she wants, though her victims might decide to get some payback later on. A raise means she gets more info, gets it faster, or her victims are too scared or otherwise preoccupied to plot revenge. </p> <p> Failure means the bully doesn’t get anything useful. A @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore03rules0.JournalEntryPage.03rules000000000]{Critical Failure} means she ends the evening with a fat lip, black eye, or broken nose (see <strong>@UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore04theadv.JournalEntryPage.04hazards0000000]{Bumps and Bruises}</strong>). She can work her contacts again the next day, but they’re more likely to be waiting for her this time! </p> <p> <strong>Busting Heads:</strong> The bruiser can improve her odds by getting more violent or extreme than usual. This alienates her contacts for a week but grants her a @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore03rules0.JournalEntryPage.03rules000000000]{reroll} on the Intimidation check. </p> <p> This raises the stakes as well. A simple failure means the evening ends with <strong>@UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore04theadv.JournalEntryPage.04hazards0000000]{Bumps and Bruises}</strong>. A Critical Failure bears more serious consequences. The GM might break the action down to an actual encounter (which might be an ambush!). The hero might run afoul of the law, come back with two levels of @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore03rules0.JournalEntryPage.03situationalr00]{Fatigue} from Bumps & Bruises, or her questions might trigger a deadly reaction from a more powerful enemy! </p> <h2 class="example">Example: Savage Measures</h2> <p> Amiri the barbarian needs to locate a town official held for ransom by nefarious bandits. Her @Compendium[swpf-core-rules.swpf-skills.Intimidation]{Intimidation} is better than her @Compendium[swpf-core-rules.swpf-skills.Persuasion]{Persuasion}, and she has the @Compendium[swpf-core-rules.swpf-edges.Menacing]{Menacing} Edge, which adds +2 to Intimidation rolls. Time is tight so she decides to bust some heads. That gives her a @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore03rules0.JournalEntryPage.03rules000000000]{reroll} as well. With the bonus and reroll she gets a success and a @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore03rules0.JournalEntryPage.03rules000000000]{raise}. The barbarian finds the bandit hideout and learns how many goons guard the official. </p> </div>
<div class="swpf-core">
</div> |
|
None
String updated in the repository |
<div class="swpf-core">
<h1 class="wide">Mass battles</h1> <p> Many adventures feature heroes traveling about the land, gathering @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore04theadv.JournalEntryPage.04allies00000000]{allies} to thwart some inevitable foe or ravaging horde. They build coalitions, train armies, discover powerful artifacts, and finally stand against the enemy in desperate and glorious battle. </p> <p> The rules presented here allow the Game Master to handle a small warband holding a fort against an undead horde, a siege against a walled city, or even full divisions of troops fighting across a massive battlefield. The process is abstract, but it provides a narrative base for heroes to plan, get involved, and take part in the carnage! </p> <p> <strong>When to Use These Rules:</strong> Use the Mass Battle rules when you need to resolve a large conflict that can go either way, and also allow the player characters to have a role in its outcome. The culmination of these tales is not always a foregone conclusion, and failure can be just as interesting as victory! </p> <p> <strong>The Basics:</strong> Each side has a number of “Force Tokens” equal to its relative strength and size. Commanders roll their @Compendium[swpf-core-rules.swpf-skills.Battle]{Battle} skill each turn. The winner reduces his rival’s force until one side or the other breaks. </p> <h2>Setup</h2> <p> To start, give the larger or more powerful army 10 Force Tokens. Give the opposing army a proportional number of tokens. If one army has 10,000 warriors, for example, and the other has 7,000, give the smaller army seven tokens. These represent the troops, ships, and other assets in each side’s army. </p> <p> Adjust the ratio as makes sense to account for special or elite troops, better equipment, and so on. If one army is half as powerful as another, for example, give one side 10 Force Tokens and the other five. Get close enough to give a reasonable approximation of relative strength. The dice and the players’ actions will handle the rest. </p> <h2>Battle</h2> <p> At the start of each round, the player characters discuss and decide on their plan. Then the attackers make an opposed @Compendium[swpf-core-rules.swpf-skills.Battle]{Battle} roll against the defender. Add the modifiers below as appropriate to each roll. </p> <table style="width: 75%"> <colgroup> <col> <col> </colgroup> <tbody> <tr> <th class="main-heading" colspan="2">Battle Modifiers</th> </tr> <tr> <th class="sub-heading left">Modifier</th> <th class="sub-heading left">Circumstance</th> </tr> <tr> <td> <p>+1 per<br>point of<br>advantage</p> </td> <td> <p> <strong>Force Bonus:</strong> The side with the most Force Tokens adds +1 for each point of difference. If the larger army has 10 tokens and the smaller one has 7, for example, the commander of the more powerful army adds +3. </p> </td> </tr> <tr> <td> <p>+1 to +4</p> </td> <td> <p> <strong>Tactical Advantage:</strong> Grant a +1 to +4 bonus for any special circumstances that might help that army, such as fortifications, weather, terrain, or other conditions not otherwise factored into the army’s strength. </p> </td> </tr> <tr> <td> <p>+1 to +4</p> </td> <td> <p> <strong>Battle Plan:</strong> Add +1 to +4 if one side has a particularly effective or clever plan over the other. </p> </td> </tr> </tbody> </table> <h3>Results</h3> <p> The winner of the opposed roll consults the Battle Results. Casualties are generally distributed evenly throughout the army or however the GM feels is most appropriate for the narrative. </p> <p> <strong>Time:</strong> A standard battle round is two hours of hard fighting. The Game Master should change this as suits her needs or the story. A more reserved fight might have four- or even eight-hour rounds, while a siege might be a battle round per day. </p> <table style="width: 75%"> <colgroup> <col> <col> </colgroup> <tbody> <tr> <th class="main-heading" colspan="2">Battle Results</th> </tr> <tr> <th class="sub-heading left">Modifier</th> <th class="sub-heading left">Result</th> </tr> <tr> <td> <p>Tie</p> </td> <td> <p><strong>Draw:</strong> Both sides lose one Force Token.</p> </td> </tr> <tr> <td> <p>Success</p> </td> <td> <p> <strong>Marginal Victory:</strong> The victor loses one Force Token, the defeated loses two. </p> </td> </tr> <tr> <td> <p>Raise</p> </td> <td> <p> <strong>Victory:</strong> The defeated army loses two Force Tokens. </p> </td> </tr> </tbody> </table> <h3>Morale</h3> <p> After an army loses one or more Force Tokens, its leader makes a @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore01charac.JournalEntryPage.01traitsummari00]{Spirit} check modified by these circumstances: </p> <table style="width: 75%"> <colgroup> <col> <col> </colgroup> <tbody> <tr> <th class="main-heading" colspan="2">Morale Modifiers</th> </tr> <tr> <th class="sub-heading left">Modifier</th> <th class="sub-heading left">Circumstance</th> </tr> <tr> <td> <p>−1</p> </td> <td> <p>Each Force Token lost so far.</p> </td> </tr> <tr> <td> <p>+2</p> </td> <td> <p>The army is made up mostly of @Compendium[swpf-core-rules.swpf-abilities.Undead]{undead} or other @Compendium[swpf-core-rules.swpf-abilities.Fearless]{fearless} troops.</p> </td> </tr> <tr> <td> <p>+2</p> </td> <td> <p>The army is within fortifications or prepared positions.</p> </td> </tr> <tr> <td> <p>+2</p> </td> <td> <p>The army cannot retreat or will be killed if it does.</p> </td> </tr> </tbody> </table> <p> Success means the leader cajoles the army to fight on. The battle continues another round (or as the attacker sees fit). </p> <p> Failure means the commander loses control of his force. The army is defeated but conducts an orderly retreat. @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore03rules0.JournalEntryPage.03rules000000000]{Critical Failure} means they flee the field in a reckless rout. They may be scattered temporarily or permanently, ridden down by the enemy, or captured as the GM decides. </p> <h3>Aftermath</h3> <p> When one side routs, retreats, or runs out of Force Tokens, the battle ends. If it’s important to determine the fate of named @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore03rules0.JournalEntryPage.03rules000000000]{Extras} or other nonplayer characters, use the <strong>@UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore03rules0.JournalEntryPage.03healing0000000]{Aftermath & Extras}</strong> rules. </p> <h2>Characters In Mass Battles</h2> <p> Player characters can dramatically affect the results of the battle. Before their commander makes a Battle roll, players who want to enter the fray describe what they’re doing and make a @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore03rules0.JournalEntryPage.03situationalr00]{Support} roll with whatever skill they feel is most appropriate. (Don’t forget that enemy champions can add to the rival commander’s Battle roll as well!) </p> <p> Each hero’s success grants the commander +1 to his Battle roll but the warrior takes @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore03rules0.JournalEntryPage.03situationalr00]{Fatigue} from @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore04theadv.JournalEntryPage.04hazards0000000]{Bumps and Bruises} for the effort. With a @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore03rules0.JournalEntryPage.03rules000000000]{raise}, the character emerges unharmed and rolls on the <strong>Battle Effects</strong> table; the player may choose to use the result rolled or give the commander the usual +2 bonus instead. </p> <table> <colgroup> <col> <col> </colgroup> <tbody> <tr> <th class="main-heading" colspan="2">Battle Effects</th> </tr> <tr> <th class="sub-heading left">2d6</th> <th class="sub-heading left">Result</th> </tr> <tr> <td> 2 </td> <td> <strong>Inspire:</strong> The warrior battles valiantly, inspiring the troops and urging them to fight on despite their injuries. Her side immediately recovers one Force Token. </td> </tr> <tr> <td> 3–4 </td> <td> <strong>Terrorize:</strong> The fighter’s fury terrorizes her foes. The enemy commander subtracts 2 from his @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore01charac.JournalEntryPage.01traitsummari00]{Spirit} roll if forced to test morale this round. </td> </tr> <tr> <td> 5–9 </td> <td> <strong>Valor:</strong> The warrior’s Support adds +2 to the commander’s Battle roll as usual. </td> </tr> <tr> <td> 10–11 </td> <td> <strong>Slaughter:</strong> The foe reels at the champion’s onslaught. Subtract 2 from the enemy commander’s Battle total. </td> </tr> <tr> <td> 12 </td> <td> <strong>An Army of One:</strong> Tales will be told and songs sung of the warrior’s epic feats this day. The enemy army loses a Force Token immediately (this doesn’t subtract from his Battle roll but does cause a morale check even if he wins). </td> </tr> </tbody> </table> <p> Failure means the warrior fought bravely. He takes a @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore03rules0.JournalEntryPage.03combat00000000]{Wound} but doesn’t add to the commander’s Battle roll. A @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore03rules0.JournalEntryPage.03rules000000000]{Critical Failure} means the character rolls on the <strong>Battle Effects </strong>table but also suffers d4+1 Wounds! </p> <p> The Game Master and players should work together to describe each character’s glorious scenes of bravery and carnage once the results are determined. </p> <h3>Ammo & Power Points</h3> <p> If it’s important to track, each round a hero enters the fray and uses @Compendium[swpf-core-rules.swpf-skills.Shooting]{Shooting} or an arcane skill the character expends some ammunition or @Compendium[swpf-core-rules.swpf-edges.Power Points]{Power Points}. </p> <p> Arcane types and archers use 2d6 Power Points or arrows per round of Mass Battle. The GM should alter these numbers based on the character's chosen tactics, the length of each battle round, weapon types, or how long she thinks the hero has to recover or rearm between rounds. </p> </div>
<div class="swpf-core">
<col> <th class="main-heading" colspan="2">Battle Modifiers</th> <tr> <tr> <th class="sub-heading left">Modifier</th> <tr> <td> <p>+1 per<br>point of<br>advantage</p> </td> <td> <p> <tr> <td> <p>+1 per<br>point of<br>advantage</p> </td> <td> <p> <strong>Force Bonus:</strong> The side with the most Force Tokens </td> </tr> <tr> <td> <p>+1 to +4</p> </td> <td> <p> </td> </tr> <tr> <td> <p>+1 to +4</p> </td> <td> <p> <strong>Tactical Advantage:</strong> Grant a +1 to +4 bonus for any </td> </tr> <tr> <td> <p>+1 to +4</p> </td> <td> <p> </td> </tr> <tr> <td> <p>+1 to +4</p> </td> <td> <p> <strong>Battle Plan:</strong> Add +1 to +4 if one side has a </td> </td> </tr> <col> <th class="main-heading" colspan="2">Battle Results</th> <tr> <tr> <th class="sub-heading left">Modifier</th> <tr> <td> <p>Tie</p> </td> <td> <p><strong>Draw:</strong> Both sides lose one Force Token.</p> </td> </tr> <tr> <td> <p>Success</p> </td> <td> <p> <strong>Marginal Victory:</strong> The victor loses one Force Token, the defeated loses two. </p> </td> </tr> <tr> <td> <p>Raise</p> </td> <td> <p> <tr> <td> <p>Tie</p> </td> <td> <p><strong>Draw:</strong> Both sides lose one Force Token.</p> </td> </tr> <tr> <td> <p>Success</p> </td> <td> <p> <strong>Marginal Victory:</strong> The victor loses one Force Token, the defeated loses two. </p> </td> </tr> <tr> <td> <p>Raise</p> </td> <td> <p> <strong>Victory:</strong> The defeated army loses two Force Tokens. </td> </td> </tr> <colgroup> <col> <col> </colgroup> <tbody> <tr> <th class="main-heading" colspan="2">Morale Modifiers</th> </tr> <tr> <th class="sub-heading left">Modifier</th> <th class="sub-heading left">Circumstance</th> </tr> <tr> <td> <p>−1</p> </td> <td> <p>Each Force Token lost so far.</p> </td> </tr> <tr> <td> <p>+2</p> </td> <td> <p>The army is made up mostly of @Compendium[swpf-core-rules.swpf-abilities.Undead]{undead} or other @Compendium[swpf-core-rules.swpf-abilities.Fearless]{fearless} troops.</p> </td> </tr> <tr> <td> <p>+2</p> </td> <td> <p>The army is within fortifications or prepared positions.</p> </td> </tr> <tr> <td> <p>+2</p> </td> <td> <p>The army cannot retreat or will be killed if it does.</p> </td> </tr> </tbody> </table> <p> Success means the leader cajoles the army to fight on. The battle continues another round (or as the attacker sees fit). </p> <p> Failure means the commander loses control of his force. The army is defeated but conducts an orderly retreat. @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore03rules0.JournalEntryPage.03rules000000000]{Critical Failure} means they flee the field in a reckless rout. They may be scattered temporarily or permanently, ridden down by the enemy, or captured as the GM decides. </p> <h3>Aftermath</h3> <p> When one side routs, retreats, or runs out of Force Tokens, the battle ends. If it’s important to determine the fate of named @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore03rules0.JournalEntryPage.03rules000000000]{Extras} or other nonplayer characters, use the <strong>@UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore03rules0.JournalEntryPage.03healing0000000]{Aftermath & Extras}</strong> rules. </p> <h2>Characters In Mass Battles</h2> <p> Player characters can dramatically affect the results of the battle. Before their commander makes a Battle roll, players who want to enter the fray describe what they’re doing and make a @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore03rules0.JournalEntryPage.03situationalr00]{Support} roll with whatever skill they feel is most appropriate. (Don’t forget that enemy champions can add to the rival commander’s Battle roll as well!) </p> <p> Each hero’s success grants the commander +1 to his Battle roll but the warrior takes @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore03rules0.JournalEntryPage.03situationalr00]{Fatigue} from @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore04theadv.JournalEntryPage.04hazards0000000]{Bumps and Bruises} for the effort. With a @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore03rules0.JournalEntryPage.03rules000000000]{raise}, the character emerges unharmed and rolls on the <strong>Battle Effects</strong> table; the player may choose to use the result rolled or give the commander the usual +2 bonus instead. </p> <table> <colgroup> <col> <col> </colgroup> <tbody> <tr> <th class="main-heading" colspan="2">Battle Effects</th> </tr> <tr> <th class="sub-heading left">2d6</th> <th class="sub-heading left">Result</th> </tr> <tr> <td> 2 </td> <td> <strong>Inspire:</strong> The warrior battles valiantly, inspiring the troops and urging them to fight on despite their injuries. Her side immediately recovers one Force Token. </td> </tr> <tr> <td> 3–4 </td> <td> <strong>Terrorize:</strong> The fighter’s fury terrorizes her foes. The enemy commander subtracts 2 from his @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore01charac.JournalEntryPage.01traitsummari00]{Spirit} roll if forced to test morale this round. </td> </tr> <tr> <td> 5–9 </td> <td> <strong>Valor:</strong> The warrior’s Support adds +2 to the commander’s Battle roll as usual. </td> </tr> <tr> <td> 10–11 </td> <td> <strong>Slaughter:</strong> The foe reels at the champion’s onslaught. Subtract 2 from the enemy commander’s Battle total. </td> </tr> <tr> <td> 12 </td> <td> <strong>An Army of One:</strong> Tales will be told and songs sung of the warrior’s epic feats this day. The enemy army loses a Force Token immediately (this doesn’t subtract from his Battle roll but does cause a morale check even if he wins). </td> </tr> </tbody> </table> <p> Failure means the warrior fought bravely. He takes a @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore03rules0.JournalEntryPage.03combat00000000]{Wound} but doesn’t add to the commander’s Battle roll. A @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore03rules0.JournalEntryPage.03rules000000000]{Critical Failure} means the character rolls on the <strong>Battle Effects </strong>table but also suffers d4+1 Wounds! </p> <p> The Game Master and players should work together to describe each character’s glorious scenes of bravery and carnage once the results are determined. </p> <h3>Ammo & Power Points</h3> <p> If it’s important to track, each round a hero enters the fray and uses @Compendium[swpf-core-rules.swpf-skills.Shooting]{Shooting} or an arcane skill the character expends some ammunition or @Compendium[swpf-core-rules.swpf-edges.Power Points]{Power Points}. </p> <p> Arcane types and archers use 2d6 Power Points or arrows per round of Mass Battle. The GM should alter these numbers based on the character's chosen tactics, the length of each battle round, weapon types, or how long she thinks the hero has to recover or rearm between rounds. <colgroup> <col> <col> </colgroup> <tbody> <tr> <th class="main-heading" colspan="2">Morale Modifiers</th> </tr> <tr> <th class="sub-heading left">Modifier</th> <th class="sub-heading left">Circumstance</th> </tr> <tr> <td> <p>−1</p> </td> <td> <p>Each Force Token lost so far.</p> </td> </tr> <tr> <td> <p>+2</p> </td> <td> <p>The army is made up mostly of @Compendium[swpf-core-rules.swpf-abilities.Undead]{undead} or other @Compendium[swpf-core-rules.swpf-abilities.Fearless]{fearless} troops.</p> </td> </tr> <tr> <td> <p>+2</p> </td> <td> <p>The army is within fortifications or prepared positions.</p> </td> </tr> <tr> <td> <p>+2</p> </td> <td> <p>The army cannot retreat or will be killed if it does.</p> </td> </tr> </tbody> </table> <p> Success means the leader cajoles the army to fight on. The battle continues another round (or as the attacker sees fit). </p> <p> Failure means the commander loses control of his force. The army is defeated but conducts an orderly retreat. @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore03rules0.JournalEntryPage.03rules000000000]{Critical Failure} means they flee the field in a reckless rout. They may be scattered temporarily or permanently, ridden down by the enemy, or captured as the GM decides. </p> <h3>Aftermath</h3> <p> When one side routs, retreats, or runs out of Force Tokens, the battle ends. If it’s important to determine the fate of named @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore03rules0.JournalEntryPage.03rules000000000]{Extras} or other nonplayer characters, use the <strong>@UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore03rules0.JournalEntryPage.03healing0000000]{Aftermath & Extras}</strong> rules. </p> <h2>Characters In Mass Battles</h2> <p> Player characters can dramatically affect the results of the battle. Before their commander makes a Battle roll, players who want to enter the fray describe what they’re doing and make a @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore03rules0.JournalEntryPage.03situationalr00]{Support} roll with whatever skill they feel is most appropriate. (Don’t forget that enemy champions can add to the rival commander’s Battle roll as well!) </p> <p> Each hero’s success grants the commander +1 to his Battle roll but the warrior takes @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore03rules0.JournalEntryPage.03situationalr00]{Fatigue} from @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore04theadv.JournalEntryPage.04hazards0000000]{Bumps and Bruises} for the effort. With a @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore03rules0.JournalEntryPage.03rules000000000]{raise}, the character emerges unharmed and rolls on the <strong>Battle Effects</strong> table; the player may choose to use the result rolled or give the commander the usual +2 bonus instead. </p> <table> <colgroup> <col> <col> </colgroup> <tbody> <tr> <th class="main-heading" colspan="2">Battle Effects</th> </tr> <tr> <th class="sub-heading left">2d6</th> <th class="sub-heading left">Result</th> </tr> <tr> <td> 2 </td> <td> <strong>Inspire:</strong> The warrior battles valiantly, inspiring the troops and urging them to fight on despite their injuries. Her side immediately recovers one Force Token. </td> </tr> <tr> <td> 3–4 </td> <td> <strong>Terrorize:</strong> The fighter’s fury terrorizes her foes. The enemy commander subtracts 2 from his @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore01charac.JournalEntryPage.01traitsummari00]{Spirit} roll if forced to test morale this round. </td> </tr> <tr> <td> 5–9 </td> <td> <strong>Valor:</strong> The warrior’s Support adds +2 to the commander’s Battle roll as usual. </td> </tr> <tr> <td> 10–11 </td> <td> <strong>Slaughter:</strong> The foe reels at the champion’s onslaught. Subtract 2 from the enemy commander’s Battle total. </td> </tr> <tr> <td> 12 </td> <td> <strong>An Army of One:</strong> Tales will be told and songs sung of the warrior’s epic feats this day. The enemy army loses a Force Token immediately (this doesn’t subtract from his Battle roll but does cause a morale check even if he wins). </td> </tr> </tbody> </table> <p> Failure means the warrior fought bravely. He takes a @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore03rules0.JournalEntryPage.03combat00000000]{Wound} but doesn’t add to the commander’s Battle roll. A @UUID[Compendium.swpf-core-rules.swpf-rules.swpfcore03rules0.JournalEntryPage.03rules000000000]{Critical Failure} means the character rolls on the <strong>Battle Effects </strong>table but also suffers d4+1 Wounds! </p> <p> The Game Master and players should work together to describe each character’s glorious scenes of bravery and carnage once the results are determined. </p> <h3>Ammo & Power Points</h3> <p> If it’s important to track, each round a hero enters the fray and uses @Compendium[swpf-core-rules.swpf-skills.Shooting]{Shooting} or an arcane skill the character expends some ammunition or @Compendium[swpf-core-rules.swpf-edges.Power Points]{Power Points}. </p> <p> Arcane types and archers use 2d6 Power Points or arrows per round of Mass Battle. The GM should alter these numbers based on the character's chosen tactics, the length of each battle round, weapon types, or how long she thinks the hero has to recover or rearm between rounds. </p> </div> |
| 130 | File in original format as translated in the repository | JSON nested structure file | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 130 | All strings, converted files enriched with comments; suitable for offline translation | Android String Resource | CSV | JSON | JSON nested structure file | gettext PO | iOS strings | TBX | TMX | XLIFF 1.1 with gettext extensions | XLIFF 1.1 | XLSX |
en-US/swpf-core-rules.swpf-rules.json” file was changed. 10 months ago