The Alexandrian

Check out Putting a Bullet in Descriptive Text from Charles Ryan.

It closely matches how I prep descriptive text for my own sessions. And, as you can see in Complex of Zombies, I actually push this philosophy even further: Every aspect of an encounter area is keyed as a clearly titled and easily identifiable “chunk” that allows you to instantly grasp the entirety of even the most complex areas in a single glance.

I’ve been thinking about writing a longer essay of my own on this topic for awhile, and I probably still will at some point. But, in the mean time, check out Ryan’s piece.

Technoir - Jeremy KellerAs I’ve discussed previously, Technoir features a conflict-resolution system in which players push adjectives onto other characters. For example, instead of making an attack roll with your machine gun to inflict hit point damage, you instead use your Shoot verb to apply the adjective of riddled to the target.

In the rules as written, positive and negative adjectives “can be applied to a character directly – representing her physical or psychological state – or to an object belonging to a character – representing its physical condition or the states of its electronics and software”. When applying the latter, you’re supposed to draw a line from the adjective to the piece of equipment being affected. Some of the former might only apply to a particular part of the body; if so, that should be indicated in parentheses next to the adjective. (For example, broken (arm).)

RELATIONSHIP ADJECTIVES

There is also one other type of adjective in the game: The permanent, locked relationship adjectives which describes how a PC feels about their connections. (These adjectives act “as positive adjectives when the protagonist is helping or defending that character, they act as negative adjectives if she acts against that character”.)

What I would like to propose is a slight conceptual and mechanical shift in how relationship adjectives are handled throughout Technoir.

1. A relationship adjective specifically refers to any adjective which describes the connection between two characters.

2. When you apply a relationship adjective to a character, you specify which character they have that relationship with. The adjective describes the target character’s relationship with that character; it does not necessarily describe the character’s relationship with them.

(You can already apply an adjective like trusting. What I’m saying is that you should specify who, exactly, the character trusts. For example, trusting (Paul) or affectionate (Cyndi). This would mean that they’re trusting of Paul or affectionate of Cyndi; it wouldn’t necessarily means that Paul trusts them or Cyndi likes them.)

3. If you want a relationship adjective to describe their relationship with multiple people – for example, if you want them to be trusting of both you and your friends – then you need to use the rules for multiple targets: You need to have an adjective or tag that justify the application and you need to discharge a Push die (that is not rolled as part of the dice pool) to pay for the attempt.

Pushing relationship tags that describe relationships with multiple people onto multiple targets costs two Push die (one for multiple relationships; one for multiple targets).

(For example, if you want to make an entire Cyn Set gang loyal to Saito International, you’d need to spend one Push die to affect all the members in the gang and a second Push die because Saito International represents a large group of people. However, if you just want the leader of the gang to feel loyal to the corporation, that would only cost one Push die. Similarly, if you want the whole gang to feel loyal to a particular representative of the Saito International, that would also only cost you one Push die.)

4. Relationship adjectives generally act as negative adjectives when you act against the character you have a relationship with and positive adjectives when you’re helping or defending that character. Some exceptions may exist.

5. In general, relationship adjectives work just like any other adjective. If someone is fleetingly trusting of a character, they’ve been momentarily persuaded to believe their story. If that same adjective is made sticky, on the other hand, then they’ll keep swallowing the character’s bullshit for a long time.

If a relationship adjective is locked onto a protagonist, however, the character it describes automatically becomes a connection. (Somebody is saying “this guy is of major importance to this protagonist” and that needs to be respected.) This means they can be hit up like any other connection, added to the plot map, and so forth. (The GM can prep customized connection tables for the new connection; use them to replace a connection who has been killed or otherwise removed from play; or even make them the seed for a new or overlapping transmission. Alternatively, the GM can just use the master table for the connection whenever the nouveau connection is hit up.)

6. Of course, as with any other adjective, you still need to establish the proper vector for applying the adjective.

Legends & Labyrinths - Art Logo 1

Snowmancer - Viktor Fetsch

Snowmancer – Viktor Fetsch

Among the artistic goals I set for Legends & Labyrinths was:

Goal #2: Find a balance between men and women.

I suppose one could claim this represents some sort of agenda for political correctness on my part. But, really, I just like pictures of pretty women doing heroic things.

Another goal was:

Goal #3: Realistic armor.

And this one is completely agenda-driven.

Primarily, this is about eliminating chainmail bikinis. But it’s also about recapturing the simple realism of a bloke in plate armor facing the terrifying and supernatural unknown.

I’m a huge fan of Final Fantasy and anime and World of Warcraft, but I think there’s a current imbalance in fantasy art. I also think that the interesting contrast between the mundane and the supernatural in fantasy art has been lost as heroes and monsters alike both reach for ever-more-gonzo proportions.

And after all, as Viktor Fetsch so aptly demonstrates with his Snowmancer, you can still look completely badass while dressed in completely reasonable clothes.

Ptolus - In the Shadow of the Spire

IN THE SHADOW OF THE SPIRE

SESSION 2B: A WOMAN ASSAULTED

March 18th, 2007
The 16th Day of Amseyl in the 790th Year of the Seyrunian Dynasty

Read more »

IN THE SHADOW OF THE SPIRE

Session 2B: A Woman Assaulted

In which assaults both inexplicable and inexcusable are committed against the innocent and guilty respectively, and a holy man asks a favor with long-lasting consequences…

The shivvel addict in the first part of Session 2 is what I sometimes think of as a “foreshadowing encounter”.

In the Shadow of the Spire is primarily designed as a node-based campaign (with a few wrinkles that I’ll discuss at greater length at a later date). This means that I do have some general sense of what will be included in the campaign, if not necessarily what will happen in the campaign.

(Although only a general sense: There are quite a few “foreshadowing encounters” scattered throughout these journals which foreshadow… absolutely nothing. The PCs went a different way. I like to pretend that I always meant for those to be “local color encounters”.)

In this particular case, I knew that the PCs were probably going to get wrapped up in a tight little knot of criminal conspiracy involving the shivvel trade. The pay-off starts coming in Session 7, but by laying the groundwork for shivvel here I’ve established some necessary exposition which will make the later stuff easier to present when it comes up. I’ve also established shivvel as part of the wider reality of Ptolus; so when I later say “the shivvel trade is important”, the players don’t have to just take my word for it: They know it.

A subtler example in this same session is Brother Fabitor. I knew that in Act II (which turned out to be several dozen sessions later) I would need someone from the Imperial Church to contact the PCs; thus the introduction of Brother Fabitor here.

I thought there was actually decent odds that Brother Fabitor would become a more significant NPC. And he might have if the paladin Alysta had remained part of the campaign. Instead the PCs ended up becoming more closely associated with Mand Scheben (who you haven’t met yet) and ended up engaging the Imperial Church in completely unanticipated fashion.

… but those are tales for the future.

FURTHER READING
Random GM Tip – Foreshadowing in RPGs

Archives

Recent Posts

Recent Comments

Copyright © The Alexandrian. All rights reserved.