Editing Unwritten: System Reference Document/Aspects and Fate Points (section)

==Compelling Aspects==

The other way you use aspects in the game is called a compel. If you’re in a situation where having or being around a certain aspect means your character’s life is more dramatic or complicated, someone can compel the aspect. That aspect can be on your character, the scene, location, game, or anywhere else that’s currently in play. We’ll start with character aspects, and then talk about situation aspects in a bit.

In order to compel an aspect, explain why the aspect is relevant, and then make an offer as to what the complication is. You can negotiate the terms of the complication a bit, until you reach a reasonable consensus. Whoever is getting compelled then has two options:

* Accept the complication and receive a fate point
* Pay a fate point to prevent the complication from happening

The complication from a compel occurs regardless of anyone’s efforts— once you’ve made a deal and taken the fate point, you can’t use your skills or anything else to mitigate the situation. You have to deal with the new story developments that arise from the complication.

If you prevent the complication from happening, then you and the group describe how you avoid it. Sometimes it just means that you agree that the event never happened in the first place, and sometimes it means narrating your character doing something proactive. Whatever you need to do in order to make it make sense works fine, as long as the group is okay with it.

GMs, you’re the final arbiter here, as always—not just on how the result of a compel plays out, but on whether or not a compel is valid in the first place. Use the same judgment you apply to an invocation; it should make instinctive sense, or require only a small amount of explanation, that a complication might arise from the aspect.

Finally, and this is important: if a player wants to compel another character, it costs a fate point to propose the complication. The GM can always compel for free, and any player can propose a compel on his or her own character for free.

===Types of Compels===

There are two major categories for what a compel looks like in the game: events and decisions. These are tools to help you figure out what a compel should look like and help break any mental blocks.

====Events====

An event-based compel happens to the character in spite of herself, when the world around her responds to a certain aspect in a certain way and creates a complicating circumstance. It looks like this:

You have ____ aspect and are in ____ situation, so it makes sense that, unfortunately, ____ would happen to you.

As you’ll see with decision-based compels, the real mileage is in the complication itself. Without that, you don’t really have anything worth focusing on—the fact that the PCs continually have complicated and dramatic things happen to them is, well, exactly what makes them PCs in the first place.

GMs, event-based compels are your opportunity to party. You’re expected to control the world around the PCs, so having that world react to them in an unexpected way is pretty much part and parcel of your job description. Players, event-based compels are great for you. You get rewarded simply by being there—how much more awesome can you get? You might have a difficult time justifying an event-based compel yourself, as it requires you to assert control over an element of the game that you typically aren’t in charge of. Feel free to propose an event-based compel, but remember that the GM has the final say on controlling the game world and may veto you if she has something else in mind.

====Decisions====

A decision is a kind of compel that is internal to the character. It happens because of a decision they make. It looks like this:

You have ____ aspect in ____ situation, so it makes sense that you’d decide to ____. This goes wrong when ____ happens.

So the real dramatic impact from these kinds of compels is not what decision the character makes, most of the time—it’s how things go wrong. Before something goes wrong, the first sentence could be a prelude to making a skill roll or simply a matter of roleplaying. The complication that the decision creates is really what makes it a compel.

The decision part should be self-evident, and something a player might have been thinking about doing anyway. The same goes for players trying to compel NPCs or each other’s PCs—make sure you have a strong mutual understanding of what that NPC or other character might do before proposing the compel. 

Players, if you need fate points, this is a really good way of getting them. If you propose a decision-based compel for your character to the GM, then what you’re basically asking is for something you’re about to do to go wrong somehow. You don’t even have to have a complication in mind—simply signaling the GM should be enough to start a conversation. GMs, as long as the compel isn’t weak (as in, as long as there’s a good, juicy complication), you should go with this. If the compel is weak, poll the rest of the group for ideas until something more substantial sticks.

===Compelling with Situation Aspects===

Just like with every other kind of aspect use, you can use situation aspects (and by extension, game aspects) for compels. Because situation aspects are usually external to characters, you’re almost always looking at event-based compels rather than decision-based ones. The characters affected each get a fate point for the compel.

===Retroactive Compels===

Sometimes, you’ll notice during the game that you’ve fulfilled the criteria for a compel without a fate point getting awarded. You’ve played your aspects to the hilt and gotten yourself into all kinds of trouble, or you’ve narrated crazy and dramatic stuff happening to a character related to their aspects just out of reflex.

Anyone who realizes this in play can mention it, and the fate point can be awarded retroactively, treating it like a compel after the fact. GMs, you’re the final arbiter. It should be pretty obvious when something like this occurs, though—just look at the guidelines for event and decision compels above, and see if you can summarize what happened in the game according to those guidelines. If you can, award a fate point.

GMs, remember that a player is ultimately responsible for everything that the character says and does. You can offer decision-based compels, but if the player doesn’t feel like the decision is one that the character would make, don’t force the issue by charging a fate point.

Instead, negotiate the terms of the compel until you find a decision the player is comfortable making, and a complication that chains from that decision instead. If you can’t agree on something, drop it.

If you offer a decision-based compel, and no one can agree on what the decision part should be, it shouldn’t cost a fate point to counter—just drop it. Countering a decision-based compel should only mean that the “what goes wrong” part doesn’t happen.