Star Wars: Edge of the Empire Rule Book

OBLIGATION IN PLAY

In addition to the narrative implications, Obligation
has a mechanical impact as well. Every session, the
GM determines whether the group's total Obligation
affects the game.

Before each session, the GM rolls percentile dice
and compares the results to the group's current out-
standing Obligation (the chart discussed in "Assem-
bling the Group's Obligation").

OBLIGATION CHECK RESULTS

If the roll is greater than the party's total Obligation,
then their Obligation is low enough that their collec-
tive tangible or intangible debts and duties are not
pressing enough to affect them—at least for now.

However, if the roll is equal to or less than the group's
total Obligation, something related to their Obligation
may introduce complications during the upcoming ses-
sion. First, rolling equal to or lower than the group's
Obligation means that all characters reduce their strain
threshold by 1 for the remainder of the session.

In addition, the GM can determine exactly whose

Obligation triggered by comparing the results of his

roll to the chart. If, for example, the GM rolled a 1 7,

then the character with the Obligation value 16-30

would have his Obligation triggered. This Player Char-

acter reduces his strain threshold by 2 (instead of 1)

for the remainder of the session.

Finally, if the GM triggered an Obligation and the roll

was doubles (an" 11" or a "44" for example), the effects

of triggering that Obligation also double. All characters

reduce their strain threshold by 2 for the remainder of

the session, and the Player Character whose Obliga-

tion triggered reduces his strain threshold by 4.

These mechanical effects represent either internal or

external pressure on the Player Characters as a result

of their Obligation. It could be as simple as the charac-

ters being worried about paying off their Obligations,

and their concern distracting them and stressing them.

However, (especially if the GM rolls doubles) triggered

Obligation can also result in tangible problems. Favors

could be called in, debts may require an impromptu

payment, or an addiction may bring with it a sudden

craving that needs to be satisfied.

ASSEMBLING THE GROUP'S OBLIGATION

flnce each player in the group has picked his char-

Uacter's Obligation, the GM assembles all of the

Obligations into a single table. If the GM is using

the group sheet from the back of this book, he'll

find a place to record the group's collective Obliga-

tions. Otherwise, he can simply write them down in

a table. The table should have three columns. The

first is the column that contains each Obligation's

value. The second column details the type of Ob-

ligation. The third column records the character to

whom each Obligation belongs.

There isn't a "standard" Obligation Check Chart-

each is unique to each group and play session,

based on the characters' individual Obligations.

The GM notes each of the players' names and his

character's Obligations on a sheet of paper. The

GM then creates an Obligation Check chart, as-

signing percentiles to each character and his ap-

propriate Obligations. In some cases, the group

may possess an Obligation as a whole (not di-

vided amongst the characters). In this case, the

group Obligation gains its own entry and listing.

For example, consider a party with four Player

Characters, Oskara the Twi'lek, 41 -VEX the droid,

Lowhhrick the Wookiee, and Pash the human.

Since there are four of them, each started with

10 Obligation (according to Table 2-2: Starting

Obligations). Oskara's Obligation is Duty (in this

case, her duty to her clan back home), 41 -VEX's

Obligation is Debt (the cost of purchasing his own

freedom), Lowhhrick's Obligation is Oath (he's

sworn to hunt down the Trandoshan slavers who

kidnapped his family) and Pash's Obligation is Fa-

vor (he owes his old mentor for setting him up as

a smuggler). In addition, Pash's player decided

to start Pash with an additional +5 Obligation to

gain +5 starting XP, for 1 5 total Obligation.

The GM takes this information and assembles the

following chart.

Obligation Value Obligation Type Character

1-15 Favor Pash

26-35 Oath Lowhhrick

in •

Note that the GM added each Obligation onto the

previous total when assembling the list. This is ex-

tremely important when using Obligation in a game

session, as it allows the GM to roll a percentile dice

and randomly determine if any of the Obligations

come into play during that session. It also shows

the GM the total Obligation of the characters. The

GM should organize the Obligation list from the

highest total value to the lowest total value.