Jan 252011

I’ve seen folks describe Fate in a variety of ways. Collect them all together and it becomes a big jumble of paradoxes. It’s rules light and it’s heavy, etc. And it’s true, we’ve certainly “overwritten” our Fate 3 based games out of a great love for explanation, examples, guidance, and advice. But at the end of the day, is the system all that heavy?

If I’m right, there are two things that lead to the Big Tome Effect. The first is the above “great love” I’ve already mentioned. The other is additional scaffolding provided in service of a particular implementation.

With that in mind, I’m going to write up Fate Core without the overwriting tendencies — so, minimal explanation and advice, no examples — and see if it’s really all that big. My suspicion, not so much. This will be largely off the top of my head, with an occasional reference to the books when I’m doublechecking something. When I’m done this should read like a brisk version of The Basics chapter from either of our games, plus condensed versions of a few system components outside of that content.

This is a rough draft, written with minimal revision and editing.

When you’re done reading — what did I forget?

The Core of Fate Core


In Fate, you can roll 4dF, or d6–d6. A dF is a six-sided die with two sides marked -1, two sides blank (zero), and two sides +1.

This should be a decision made for the entire game, as each has its own peculiarities. Both produce a zero-centered distribution running from either -5 or -4 to +4 or +5. 4dF will generally feel more reliable, with the center weighted more heavily, while d6–d6 will produce wider and more frequent variation.

When you roll the dice, the number you get is added to the rating of the skill you’re using to get the final result. Skills are rated according to the ladder.

The Ladder

Skills (and difficulties) are rated according to the adjective ladder. Each adjective also has a numeric value associated with it. You can treat the adjectives as optional or mandatory; they are there as tools for giving you a plain-English way of talking about the numbers. The default ladder for Fate is as follows (but can always be tweaked for your specific implementation’s needs):

Value Adjective
+8 Legendary
+7 Epic
+6 Fantastic
+5 Superb
+4 Great
+3 Good
+2 Fair
+1 Average
+0 Mediocre
-1 Poor
-2 Terrible
-3 Awful
-4 Abysmal


Difficulties are rated on the ladder as well. When you roll, your skill rating + dice roll is compared to difficulty rating, and the difference between those two numbers is measured in shifts.

Generally speaking, if you get zero or more shifts (meeting or beating the difficulty target), your action is considered a success.

So what’s a shift? Think of it as a unit of momentum, something which is used to shift the action in a direction you want. Some elements of the system may allow you to spend shifts as a kind of currency, spreading around the result, while others may simply be interested just in the total number.


Characters have skills, which are rated on the ladder. So what’s a skill?

Skills represent what your character can do, the kinds of actions he or she can undertake. Skills also differentiate characters from one another, highlighting where they’ll shine and where they’re likely to play second fiddle. Actions will be discussed in greater detail later on in this document.

Choosing skills:

There are any number of ways you might have characters select skills in your game. In our published games, we favor a “pyramid” or “tower” style, where slots for skills are bought at each rating level from Average on up, with requirements as to how those slots are stacked atop each other. Other implementations may favor a simple point buy approach, or something else entirely.

When setting things up for skill choice, think about two things:

  • Niche protection: Offer enough skills with enough variety that each player can shine in a distinct and different way.
  • Breadth of competence: How many skills can each character manageably take, and how many must they not take as a result?

The ideal (which may be different depending on the demands of your implementation) is a sweet-spot between the two, allowing players to create broadly competent characters that nonetheless do not step on each other’s toes.

Designing skills:

A specific game should have a customized skill list that fits the priorities of the game’s story and setting. A game where social interaction isn’t particularly important or nuanced might simply present all social skills as a single Interaction skill. When social interaction is important (and system support of that is desired), multiple skills may be warranted (such as Empathy, Rapport, Reputation, Deceit, Intimidation).

Skills are composed of one or more trappings. Broadly, a trapping is a kind of action (or family of actions) that a character can undertake using the skill. The concept of trappings is optional, really, but can be a good way to double-check that you’re covering all your bases.

Some skills may have overlap, sharing a particular trapping between them. Nothing’s wrong if this happens, but again, it’s a good thing to keep an eye on.

If you’re going to be using stunts, it’s helpful to know what trappings your skills have.

Each skill might offer one or more of the following options for action, which will be discussed in more detail later in this document:

  • The ability to take on a particular family of difficult tasks
  • A method of gaining knowledge through perception or research
  • A mode of attack
  • A mode of defense
  • The ability to endure a kind of stress
  • The ability to speed movement and to move past obstacles
  • The ability to change a target or environment in some way, often by introducing or discovering an aspect (note: an “environment” is not always about physical surroundings)
  • A method of presenting a difficulty that others must overcome

In some implementations, every skill might offer every option, but in most cases each skill uses a subset available via the skill’s trappings.


Characters have aspects, which are not rated on the ladder. They can cover a wide range of elements about the character, painting a picture of who the character is, what he believes in and what’s important to him, but also what he’s connected to and what complicates his life. They can be relationships, believes, catchphrases, descriptors, items, and other things besides.

Importantly, the best aspects are double-edged, providing ways they can be used for advantage, ways they can complicate the character’s situations and decisions, and ways other characters can leverage that part of the character.

Aspects are powered by fate points. A character will usually start with one or more fate points at the start of a session. How many will depend on the particulars of your implementation, but the sweet spot is to supply players with enough fate points that they feel like they can spend them when they most need to, but few enough that they have to make the occasional tough choice.

Aspects don’t live exclusively on characters. Sometimes they live on things which contain characters (like scenes or locations or adventures), or which characters possess (like weapons or vehicles or organizations). Where you might find aspects outside of characters themselves will vary depending on the specifics of your implementation.

Invoking aspects:

A player can take advantage of an aspect by spending a fate point. When this happens, the player invokes the aspect.

To invoke an aspect, identify which aspect you’re intending to use, explain why it is relevant in this situation, and spend a fate point. Invoking lets you either:

  • Pick up the dice you just rolled and roll them again, replacing the previous result with the new roll; or
  • Add two to the result; or
  • Invoke for effect. Invoking for effect allows you to use the aspect to declare something is true (assert story reality) or — if the aspect you’re doing this to isn’t yours — trigger a compel for the character possessing the aspect.

Some implementations may limit or change these options. Some may place limits on which categories and quantities of aspect can be invoked simultaneously (as with Diaspora‘s concept of scope).

Sometimes a player may have an opportunity to invoke an aspect that isn’t a part of his character: perhaps it’s on the location, or on another character. This is perfectly fine so long as an acceptable explanation is made of how the player’s character takes advantage of the aspect.

Some skills may provide the ability to introduce or reveal new aspects on the scene when a successful roll is made. Usually, the character that made the skill roll may invoke that aspect for the first time for free. This is called a tag of that aspect. In some or such cases, the tag may instead be available “publicly” to the first person to incorporate and invoke the aspect in question.

Compelling aspects:

A character’s story can be significantly complicated by the presence of an aspect. When this happens, the player or the GM compels the aspect. When a character is compelled by an aspect, he gains a fate point.

Compels are often subject to some kind of approval process. If a player is undertaking an action that’s complicated by his character’s aspect, and calls out a compel, often it’s up to the GM to agree whether it’s allowed. If the GM compels a character’s aspect, his player may have the option to refuse it (perhaps paying a fate point instead of gaining one). Sometimes a compel may come up after the fact, such as when the GM uses a character’s aspect to introduce a complication to the plot, or when a scene concludes and it’s clear the character was acting under the dictates of one of his aspects throughout.

A compel is a decision to set aside the dice and focus on the dictates of drama instead. It’s a conversation about the aspect and how it creates a new complication, or otherwise shuts down or changes some of the options that were previously available. If the conversation suggests that a character’s Drunk aspect means he makes a fool of himself at the governor’s ball, there’s no need to roll the dice to see what kind of impression he makes. The logic of this conversation replaces the rolling of dice as the way to determine the outcome.

Sometimes an aspect may exist outside of a character, but still be used to compel that character, such as with an aspect found on a location. If the location is “On Fire!”, it’s reasonable to suppose the characters located there will face compels related to their present predicament.

Choosing aspects:

Fate prefers that characters be created as part of a social gathering, rather than as a solo or homework exercise. The main weight of this intent bears on the choosing of aspects.

A character may start with one or two aspects selected simply to say what kind of a person the character is and what sort of complications typically befall him.

The rest of the aspects are determined by stepping through a particular sequence of phases as determined for your implementation.

In each phase, a piece of the character’s back-story is determined, and one or more aspects are derived from that back-story.

One or more of these phases should involve one or more other characters from amongst the player characters. These cross-over phases are key to building a cohesive group that feels natural as a group. They establish lasting, core relationships among allies (and in some cases, enemies or rivals), and provide the social bedrock that the story of the player characters, and thus the game, will be built upon.

Think carefully about how many aspects a player (and, multiplicatively, a GM) will be able to parse, keep track of, and use over the course of a session. Make sure your background and phases don’t result in too large a suite of aspects. Sometimes less is more, and if you’re allowing a character to acquire a few temporary aspects during play (as with consequences, below) you’ll want to be sure to leave room for those in your tally. For our money, the sweet spot in terms of permanent character aspects is between five to ten.


Stunts are optional, but show up in enough implementations to warrant a place in the core. Put simply, they are “locked in” ways that a character can get an extra benefit when doing a specific kind of thing. In this they relate just a little bit to aspect invocations. An aspect invocation costs a fate point and gives you a highly flexible benefit equal to about two shifts. A stunt does not (usually) cost a fate point to use, and offers a specific (thus less flexible) benefit equal to about two shifts.

Stunts are tied in to skills. More specifically, they’re usually tied into skill trappings, and improving how those trappings are used.

Designing stunts:

Depending on your druthers, an implementation may feature a list of pre-designed stunts for the players to pick from, or may allow the players to design their own. Either way, stunts should be designed along the following lines. (Note: The idea of stunt construction was not fully formed when Spirit of the Century was published, so you may find that some of the stunts in that product do not match up with these guidelines.)

A stunt provides one of the two following options:

  • Adds a new trapping to a skill (usually enabling an action the skill couldn’t normally perform)
  • Extends an application of an existing trapping of a skill by providing about two shifts of benefit

These options should be restricted to a particular broad set of circumstances, and when extending with two shifts, should dictate how those shifts are applied.

Possible extensions include:

  • Give a +2 to a specific application of a non-attack trapping
  • Give a +1 to an attack, improving its accuracy (if your implementation values hit-or-miss accuracy more heavily than magnitude-of-success)
  • Give a +2 to an attack’s result, applied only if the attack was successful (same parenthetical comment as previous)
  • Give one or two expendable 2–shift effects or a persistent 1–shift effect.
  • Reduce the amount of time necessary to complete a particular task by two steps on a time chart
  • Extend the duration of an effect by two steps on a time chart
  • Reduce a particular kind of difficulty factor faced by the skill trapping by up to two
  • Combine any two of the two-shift effects from above at half value
  • Get a more powerful effect, but only when you spend a fate point

Choosing stunts:

When used, stunts are a big factor in character power. They provide an ongoing benefit roughly equal to the character gaining an additional fate point at the beginning of each session beyond the fate points he’ll be starting with. This is something to keep in mind when determining how many stunts a character gets to start. One approach would involve simply setting a fixed number of stunts that each character gets (as in Spirit of the Century).  Another approach would involve reducing the number of fate points a character gets at the start of a session by the number of stunts the character has (as in The Dresden Files RPG). Other approaches may exist as well.

Since each stunt represents a little extra bit of rules a player has to remember, keep that in mind as well when setting limits, and set the limits such that the quantity is likely to be manageable. Five or six stunts on average may be a good practical target.

Powers as Super-stunts:

You may find yourself wanting to create potent abilities for characters. Stunts provide an avenue for this; you might go with the idea of “super-stunts” that simply provide multiple stunts’ worth of benefit all in a single package that consumes multiple stunt slots. This is in essence how the supernatural abilities in The Dresden Files RPG were constructed.


Above, I talked about the sorts of actions a character can take when using his skills. Here, I’ll drill into each kind of action a little more.

The ability to take on a particular family of difficult tasks:

This is the classic catch-all for a skill. A Woodcraft skill would provide the ability to assail a variety of carpentry tasks, while an Athletics ability would include the ability to climb, for example.

As covered above, a difficulty is determined, a roll is made, and the result is compared to the difficulty. Success occurs if the result matches or beats the difficulty. Additional shifts might be “spent” in various ways to improve the quality of that success. Maybe the task is completed more quickly (a “time table” suited to your implementation helps here), or the craftsmanship is of unusually exquisite value.

A method of gaining knowledge through perception or research:

This is really a different variety of the first type of action, but worth calling out on its own. A Guns skill might include the ability to assess the armament of an opponent, or know general trivia about firearms.

Similar to the above, difficulties are determined, and the shifts generated by a success indicates the depth and quality of information attained. Sometimes these shifts might be spent individually for specific questions or facts, and as with the above, might be spent to speed up the rate at which the information is uncovered.

A mode of attack:

An attack is an action that inflicts stress on a target. Stress comes in one or more flavors tied to the kinds of conflict your implementation supports (such as physical, mental, social, resources, hunger, or doom), and as such the “mode” of the attack in question indicates the kind of stress you’re looking to inflict. Rarely, a skill might offer the ability to inflict more than one kind of stress with an attack, chosen at the time the attack is made.

An attack is usually made by comparing two skill rolls, the attacker’s and the defender’s, and using the shifts generated by the attacker (if successful) to determine the amount of stress inflicted. Here, zero shifts means that the attack “connects” but does not inflict stress — a distinction that is relevant if a stunt or other system effect is triggered only when an attack is successful.

That said, frankly, stress is an optional feature. You may wish to make an implementation where hitting your target creates some other effect: outright death or removal from the fight, a difficulty factor that the victim must overcome, or something else. In that case, your “attack” is actually one of the other kinds of actions covered in this section.

A mode of defense:

Defensive uses are reactive, seeking to prevent an attack against you from succeeding. They are often specified to be used only against certain kinds of attack. See the attack action, above, for system particulars.

One downside of a reactive ability like this is that a particularly good roll — one in which the defender generates a number of shifts rather than the attacker — can feel “wasted” unless a use is made possible. A few options exist to address that.

One such option is the notion of spin. Here, when a defender beats the attack by 3 shifts or more, he gets spin, allowing him to add +1 to either side of the very next roll (including those made by allies), essentially as a way of passing the momentum of a very successful defense on to another part of the scene.

Another possibility, more potent, would be to allow the defender to place a temporary aspect on his attacker when beating the attack by 3 shifts. In overextending himself, the attacker has left an opening…

The ability to endure a kind of stress:

As noted above (see the attack section), characters incur stress when they’re victims of attack actions. Some skills improve the ability to endure this, by increasing the character’s capacity for stress.

All characters have a baseline amount of stress they can take (in DFRPG, 2; in SOTC, 5). This stress is represented as a track of numbered boxes. The higher a character’s stress-capacity skill, the longer the affected track (often gaining an additional box for every two steps above Mediocre, rounded up).

The length of a stress track should be considered carefully when designing your implementation. Make it too long and the characters feel invulnerable (frankly a real risk in SOTC).

When taking stress, the box with a number matching the amount of stress taken is checked off. If that box is already checked off, the next higher unchecked box is checked. If no available higher boxes exist, the character is taken out — removed from the conflict, or at least from the dimension of the conflict represented by the stress track.

When an attack takes out a character, the attacker gets to determine what happens to them within the scope of the type of stress inflicted (you can’t punch someone’s reputation into a bad state, but you can break their bones or kill them or just knock them out).

A player may remove his character from the conflict ahead of time, however, by offering a concession. A concession is identical to a taken out result, but gets defined on the victim’s terms rather than the attacker’s. The attacker may (and often should) get the option to refuse an unreasonable or unsatisfying concession, but this is not a carte-blanche veto power so much as an option to negotiate.

Optionally (but recommended), stress may be mitigated by consequences. A consequence is a temporary, negative aspect the character takes on, usually filling one of a limited number of slots (one of each level). The attacker may tag a consequence as with any revealed-through-a-skill-roll aspect. The amount of stress reduced taking the consequence depends on how long it will take the character to recover from the consequence. Our defaults:

  • Mild consequence, reducing stress taken by 2, fades after a scene of rest
  • Moderate consequence, reducing stress taken by 4, fades after a session of play
  • Severe consequence, reducing stress taken by 6, fades after the conclusion of the current story (implying some downtime before the next story commences)
  • Optional: Extreme consequence, reducing stress taken by 8, but permanent, and possibly replacing one of the character’s other existing permanent aspects

When consequences are in play, you may want to consider a rules option that pays out a number of fate points (1, 2, or 3) equal to the worst level of consequence the character is currently carrying when that character concedes a conflict.

The ability to speed movement and to move past obstacles:

We recommend the use of maps, however abstract, to help root play in a sense of we’re-all-on-the-same-page physicality. In Fate, we divide these maps up into zones. A zone is about as big as the space you’d expect a character to be able to move through in one turn while undertaking another action.

But sometimes moving is the action, and the character should be able to eat up more ground when doing so. Here, the character rolls the appropriate skill against (almost always) a target of 0. If he generates one or fewer shifts, he may only move one zone. If he generates more, he may move a number of zones equal to the number of shifts.

Some maps will offer obstacles which will require multiple shifts in order to move into or out of a given zone. These obstacles are called borders and are given a numeric value equal to the number of shifts required to overcome it. A zone surrounded by a border of 2 will require three shifts to move into (2 to overcome the border, 1 to move into the zone). When a border is involved, failing to generate enough shifts means you can’t move into that zone on this turn. Often it’s workable to accumulate shifts across multiple turns when a particularly large or troublesome border is encountered.

The ability to change a target or environment in some way:

Whether the result of research or specialized knowledge, or as a particular combat maneuver, characters in fate may be able to use their skills to temporarily alter or add aspects on another character, or even the environment itself (whether that environment is the physical location, the loom of fate, or the reactions of a crowd).

In a conflict, this kind of action is referred to as a maneuver. With a knowledge or perception skill, it might be an assessment (where an existing but unknown aspect is discovered) or a declaration (where new facts are asserted as true on the basis of the quality of the character’s knowledge).

In any event, on a success, the player describes the new aspect (or finds out what the new aspect is), and the aspect is available for a tag as previously discussed, as well as invokes and compels. Usually only one aspect may be created at a time, per action. In some cases the value of the roll made will indicate how difficult it is to “uproot” the aspect and get rid of it. In other cases, getting rid of it will be impossible, or require a simple success against a lower target. In addition, the temporary aspect may depending on its nature simply disappear after one use is made of it.

A method of presenting a difficulty that others must overcome:

Some skills may provide a pasive or active ability to create a difficulty rating that others must overcome. A character’s Preparedness skill might represent how difficult it is to surprise him — or enter his private estate undetected. A character might have a combat skill that allows him to interpose himself and offer a second line of defense for an ally under attack.

When used in this way, the skill is rolled to create a block. A block is a short-term, persistent effect which sets the minimum difficulty for making a particular action. From our examples above, the character might roll Preparedness to create a block against enemies trying to infiltrate his estate, or Swordplay to bodyguard his friendly neighborhood wizard. An aggressor must roll well enough to beat either the block or the standard difficulty (or defense roll), whichever is higher, in order to succeed and generate shifts.

Supporting Character Change and Growth (Advancement)

Over the course of stories, characters certainly change, but that does not always translate to measurable, stattable growth. With this in mind, I’m loath to call the following “advancement” on the grounds that that’s too reductionist a way of looking at things. Instead, let’s call this character development. In Fate, character development occurs along several possible axises:

  • Change Aspects: The character experiences a change of nature, perspective, identity, relationship, or belief
  • Shuffle Skills: The character shifts the focus of his expertise, falling out of practice with one skill while improving another
  • Gain or Increase Skills: The character’s competence broadens or deepens
  • Gain Stunts (or FP): The character grows in power

Depending on your implementation particulars, characters may experience development along one or more of the above lines, each at their own pace. One possible plan for this is presented in the Dresden Files RPG, using a system of minor, significant, and major milestones in the story’s progress to determine when a character may do one or more of the above (focusing on the first two as frequent occurrences, while the second two come along more rarely).

Extending the Game: The Fate Fractal

When adding something new to Fate for your specific implementation, it’s important to keep the basics of the system intact. You’re adding new rules, yes, but those rules should be constructed out of the existing building blocks. This helps make sure the new stuff you add in remains familiar to players already on board with the basics of the game.

So what’s the essential atom of a Fate game? The character. What particles make up the atom? Aspects, skills, stunts, and stress tracks. When you use these particles as your building blocks for new system components and concepts, you’re ensuring that the end result has that sought-after familiarity. And thus by building your new system components out of these existing parts, you add seeming complexity while actually retaining the core simplicity of the system.

This effect is what us gearheads refer to as the Fate Fractal. When fully and thoughtfully deployed, the fractal makes sure that no matter how close in or far out you zoom your focus, you’ll find something familiar based in the character components and actions you already know.

A few thought experiments, briefly detailed, to get this concept across:

I’m unsatisfied by representing a burning building simply as an aspect on a location. I want some kind of ongoing damage idea. Using the fractal, I know that ongoing damage should be designed like a character. I’ve already got the aspect; one thing that’s missing is, say, a skill — one which can be used to attack characters exposed to the flame. Voilla — I have something which produces the ongoing damage of a burning building. Maybe it has another skill which represents how hard it is to put out — and a stress track for tracking how effectively it’s being extinguished.

I want to represent vast, secret organizations fighting secret wars, as a second layer of political action running alongside the personal action of the game. Using the fractal, I know these secret organizations can be statted up just like characters, either in a simplified or fully detailed format — Aspects? Sure. Skills? Definitely. Stunts? Could be. Stress tracks? Only if you want to be awesome! Phases and back stories and interrelationships? Now you’re cooking.

I’m running a Fate fantasy game and I’m looking to make magic items potent, rare, and storied. I want them to have a little more traction than just showing up as someone’s aspect (or, maybe, stunt). The fractal tells me that I should make magic items like characters, with their own aspects (resulting from phases — the item has a story), stunts, and skills, potentially conferring onto the bearer or potentially acting on their own. Maybe the items are a way of cheating fate, of allowing the bearer to act above his station or in a way that plays merry havoc with the Great Loom. So how about a stress track, one that represents the magic item’s progression towards ultimate doom?

Those are just three examples, but hopefully they point the way as to how you can use the stuff you already know to build and play characters in order to build and use other components for the system. Almost always you can get exactly what you need by treating the thing you want to add as a character — albeit, sometimes at a different scale (physically, temporally, or otherwise) of operation.

  47 Responses to “The Core of Fate Core”

  1. […] Fred Hicks of FATE fame has just posted an off the top of is head summary of the core rules of FATE 3.0: http://www.faterpg.com/2011/the-core-of-fate-core/ […]

  2. […] This post was mentioned on Twitter by Fred Hicks, Rocha, Chris Helton, Dazed (save ends), Patrick Benson and others. Patrick Benson said: RT @fredhicks: New on FateRPG: The Core of Fate Core http://www.faterpg.com/2011/the-core-of-fate-core/ […]

  3. My first read through I cannot find anything missing that I would need in order to play the game. I really like the Fate Fractal examples. This is the kind of document that I want to launch a game with. Nice work!

  4. Thanks, Patrick!

  5. A nice, concise summary, thanks.

    I spotted a typo: in the section “Supporting Character Change and Growth (Advancement)”
    …characters may experience development alone one or more of the above lines….
    “alone” should be “along” ?

    Thanks again

  6. If anything, throw in a couple of examples, like one for skills, Aspects, etc, check references to things like the time chart and add a cover. A thin, elegant and surprisingly encompassing system, there you go!
    Awesomely brilliant and hey, much easier to produce a Brazilian edition too. =)

  7. So, barring some edits and some Lenny/Ryan/Clark/Rob jazz, I think Fred just wrote up FATE Core.


    What I’d like to see in a FATE Core product is, essentially, exactly this — plus edits and jazz — alongside some essays on how to hack the atomic core for various purposes. (Frex, Rob’s tempo system, or some of the ideas floating around for “non-city” City Creation… which isn’t even dealt with in the Core, so a campaign-structure essay is fertile ground. I guess that’s just an element of hacking phases. Anywho.)

    As someone working IN MY COPIOUS FREE TIME (hah!) on a FATE-based hack of S7S as a possible “FATE Core campaign frame,” I’d be glad to contribute a Designer’s Notes sort of discussion of what, how, when, where, and who I hacked to suitably meld the systems.

    Out of blatant personal interest the goodness of my heart, of course.

    Please note, though: this idea would generate a “weird-looking” gaming product. Possibly more akin to Things We Think About Games or The Bones than a standard RPG core book.


  8. Stunts are optional, but show up in enough implementations to warrant a place in the core.

    The more I think about it, it’s skills that are optional, not stunts.

    Or maybe either-or. But that could be some more, uh, advanced thinking.

    – Ryan

  9. @Felipe — I agree, a fuller version would at least have examples. I just think we’d also do well, with the Core, to get away from our excessively advice driven presentation — lots of bloat there. And we don’t need to go crazy with the examples.

    @Mike — Got the typo fixed, thanks!

    @Chad — Maybe I did! Part of the point of writing all this today was to see if that’s in fact the case.

    @Ryan — I admit I have a hard time seeing clear to a skill-free implementation (unless you’re talking about collapsing skill ratings into Aspects — certainly something I’ve seen before), but you do have my attention. 🙂

  10. @Ryan — Skills vs. Stunts… that’s an essay. #icmf

  11. The explanation I’m using for new FATE players is that Aspects are the parent of instances of Stunts and Motivations. I’m using Clinton Nixon’s Secrets & Keys terminology and math, but the idea is the same. Working it this way allows for something like “Epic Wiseass” to be used as a social weapon as well as a motivation and a way of getting into trouble.

    Other than that, I’m using this for the handout for my players for Chicago GameDay…

  12. @Ryan — I admit I have a hard time seeing clear to a skill-free implementation (unless you’re talking about collapsing skill ratings into Aspects — certainly something I’ve seen before), but you do have my attention.

    Lenny & I have been talking about this off and on for a year now — his idea, that I was initially resistance to until he convinced me of its design merits. In our copious free time, I’ll see if we can draft our thoughts together.

    – Ryan

  13. This is very helpful. Thanks, Fred!

  14. That pretty much sums it up the entire game. Good job!
    I know the folks in my group looked at the DFRPG and said, “What do you mean the rules are easy? Those books are huge.” A brief explanation eased their fears.
    I think something like this would be an awesome handout for convention games.

  15. My limited experience introducing people to FATE (through Spirit of the Century) is that the stunts are the part that is a barrier, the “rules heavy” part. You can get by with a summary for most of the game, but selecting stunts that best suit your concept is time consuming. You really need to read all of the stunts, and it’s a big list. In my short-lived Spirit of the Century game, only half of the players ever selected stunts.

  16. Alan, that’s part of why the mortal stunts in DFRPG are on a design-your-own footing. 🙂

  17. I was going to say, maybe some short stunt construction kit. (That’s what I’ve done for Albion.)

    The question I asked on Twitter was, what’s necessary for something to count as Fate? Don’t stray too far beyond that. The way I would want to use something like this (assuming it’s open in that way) is as a basic platform to build on, knowing there’s a solid base of people who have it. A little bit like the Savage Worlds Explorer’s Edition, but hopefully quite a bit shorter and with better layout. 😉

  18. OK, actually read it now! Always helps… Bear in mind I’m not hugely familiar with Fate.

    I think it covers the right ground. This first draft reads like it’s aimed at experienced gamers who are at least vaguely aware of Fate. It’ll need a substantial rewrite to be clear to someone who hasn’t used Fate before, including examples when you introduce things. But that’s the development process. I wonder if it would help to get the basic shape of things down and then go on to talk more about using it.

    You’ve got a bunch of non-standard terminology floating around. I think this is a bit of a stumbling block for Fate, and here’s the opportunity to lower the barrier to entry. Consider whether it’s all needed. For instance, you could easily rewrite it without introducing trappings as a technical term – just talk about uses of skills.

    Aspects section – first para should say how they act and therefore why we should be interested in them.

    Maybe a mention of how skills and aspects replace attributes found in other games.

    Liked the Fate Fractal examples. Maybe add on couple of examples of how a character would interface with these.

    (removes further attempts at back-seat editing)

    Oh, and there’s been a lot of work in RPGnet threads with people producing their own short Fate cores – hopefully you’ve been taking notes from that!

  19. […] Hicks, einer der Erfinder von FATE, hat den Kern von FATE zusammengefasst. Es ist quasi die Anleitung für jeden, der selbst ein Spiel auf der Basis von FATE […]

  20. To Fred (and all you other guys at Evil Hat):
    I love you for puttin this thing up, as I do for the hole system. Thanks, it’s very appreciated and I hope you don’t mind if I make a feeble attempt to translate this text to german (we’ve got quite some fans over here).
    In my first approach, I stumbled over this little phrase (it’s in the “Invoking aspects” passage):
    “Sometimes a character may have an opportunity to invoke an aspect that isn’t a part of his charakter:”
    The character’s character sounds a little strange to me, but I might be a nitpicker here.

    Regards and thanks again, keep up the amazing work

  21. Fred, if you guys wrap this up in book form I will buy it immediately.

  22. Thanks for that catch, Henning. I’ll edit it to be a little clearer.

  23. Pretty great. Some parts I’ll have to read through again, but it’s great to have the pieces laid out so succinctly in a single location. The Fate Fractal examples at the end really bring it home.
    I agree that the concept of stunts isn’t super clear. Maybe more examples?
    Thanks for making this available, Fred. You guys rock.

  24. […] system that you only need the book for character creation. For more on fate feel free to look here http://www.faterpg.com/2011/the-core-of-fate-core/ And for the specific version we use here http://voidstar.squarespace.com/strands-of-fate/ . As […]

  25. […] week, Evil Hat was kind enough to post an initial draft of what could be considered the core systems of FATE 3.0 in compact format. Since this is so directly germane to this post series, it shouldn’t be at […]

  26. Hi again,
    I’m gettin’ close to conclude my translation – and while I still think this is a pretty neat Fate 3 toolkit, something occured to me.

    I just wondered if fate points are not worthy of a section of their own. I know… they’re pretty much intermingled with aspects – and there’s most of the info in that passage. But hey… they share the name of the system. And synced with aspects, it’s where the heart of the system beats IMHO.

    So maybe, it’s worth paying some further attention to them in an upcoming post.

    Thanks for all the insight – you guys rock (& roll)

  27. Fred: Thank you so much for writing this. In reading SotC I never really understood how all the mechanics interacted with each other: having it all reduced down to this helped me considerably.

    @Chad: Re: FATE-based hack of S7S: I would love to see this.

  28. This is a great write up, thanks for this. And thanks for the great games.

    I’ve seen it said so many times in various place that it’s something I’d really like included here.

    Aspects describe [i]who you are.[/i]
    Skills describe [i]what you can do.[/i]

    Simple clear and effective.

    Also, given the great advice here on designing skills… why not let players define them just as they already do Aspects? Certainly cut down on some of that bloat you were referring to. 😉

  29. @Fractaled, I’ve toyed with the notion of providing a system for building custom skills, but I’d bet a lot of players don’t want to do that depth of work and — beyond that — putting together such a system is trickier than it looks at first blush. Good point about the what makes an aspect/what makes a skill lingo, tho.

  30. I played with player-designed skills once. The biggest problem was wasting time and energy on creating a bunch of skills that never came up in play.

    The first thing I’d try is starting with the top three skills, leaving the rest of the skill column blank. Those skills then supplement the aspects in the scenario design process. Other skills can be filled in as they come up; if that leads to overfitting in the first adventure, charge a Fate Point to fill in a skill.

    For a more complicated system, I wonder about letting players build custom skills out of defined trappings, extending them further with stunts.

  31. To be fair, what I was thinking as far as players “designing” their own skills was much closer to something like HeroQuest or Risus, than full on write-ups as per the Fate books already on the market. It wouldn’t be that hard to write-up a framework for PC defined skills with that in mind, while keeping them balanced and actually useful.

  32. In the interest of streamlining; is “The Ladder” necessary? Memorizing a table of adjectives to essentially say I have +3 Swords or +5 Search seems like more trouble than it’s worth…

  33. Yes, categorically, the Ladder is necessary. What’s unnecessary is complaining about it! You needn’t memorize the adjectives, and folks who like the adjectives needn’t memorize the numbers. It’s a big tent, folks. Plenty of room.

  34. I appreciate it when content creators provide values as both adjectives and numbers, e.g. “Athletics: Great (+4)”. When they don’t, the players have to do unreasonable memorization and conversion (just as Colin’s protesting).

  35. I agree with Ezra. Some people prefer the adjectives, while others, like myself, prefer the numbers. The ladder should stay, as should the numbers!

  36. Hi. Translated to Spanish as Lo más básico del Fate básico

    Thank you Fred!

  37. […] The Core of Fate Core » Fate […]

  38. Took the time to read through this, and I have to say that I am very impressed. I agree that when you are ready to wrap this in a cover, I’m ready to add it to my bookshelf. The introduction of the Fate Fractal is fantastic, and would certainly use that approach to add depth to Aspects. Also I find that the section on Trappings actually addresses many of my ruminations on the creation of Magic Skills, or Stunts.

  39. […] Experience with system: not so much – it's pretty easy to pick up.Core of FATE Core […]

  40. […] artículo original se encuentra en http://www.faterpg.com/2011/the-core-of-fate-core/. Desde aquí queremos agradecer a Fred que nos haya permitido llevar a cabo la […]

  41. […] plays into those ideas very nicely. This post on fate.net outlines the essentials of the system, and is really useful in determining how Fate will look for […]

  42. […] we can say right now is the game will use a version of the FATE system to be designed by the brilliant Mike Olson. Our plan is to emphasize accessibility, ease of play, […]

  43. Definitely liked the succinct summary! A few thoughts:

    Possibly a section on generating opponents, npcs, etc – this would cover Minions, Companions, how to throw together NPCs on the fly, that sort of thing?

    Possibly a section discussing ways to handle equipment and resources.

    Definitely at least something discussing how talky skills can be useful in fighty situations.

    I too think that perhaps Fate Points (or the Fate Economy might make for its own section. Everything in the third paragraph about Aspects save the first sentence is really talking about that economy:

    A character will usually start with one or more fate points at the start of a session. How many will depend on the particulars of your implementation, but the sweet spot is to supply players with enough fate points that they feel like they can spend them when they most need to, but few enough that they have to make the occasional tough choice.

    , and it’s where you can discuss the Refresh and shooting for a sweet spot. I once drew a quick diagram to illustrate the idea to new players, so they had a solid understanding of how Fate points changed hands, and why they wanted multi-faced Aspects. Some of the concepts (like the fractal) might benefit from quick sketch or flow visuals.

    In the interest of avoiding the Big Tome effect, perhaps Fate Core could be split into 2 books? One being a streamlined Default Version and the accompanying book being the Tinkerer’s Manual for adjusting all those dials and widgets. One of the big problems with FUDGE (imho) was that since it presented no default system, just all the options for creating the dials and then tweaking them, it demanded way more upfront work than I had time for, even when I was in college, and my time is only more valuable now. One of the things I dig about SOTC and other FATE variants is that they ground you in a solid default, so if you don’t want to tinker (or don’t have time), you can hit the ground running.

  44. […] from a design perspective — is the Fate Fractal principle. Search for that text here –  http://www.faterpg.com/2011/the-core-of-fate-core/ – but in short, it’s the idea that anything in the system can be treated as a character. […]

  45. […] the concept of aspects. Another idea I am trying to figure out how to implement is a version of the Fate Fractal, I want to make the trench that they start in as the first enemy that the players confront. The […]

  46. Well, first, i think you’ve made (and still do) an AWESOME job. I’ve been “teaching” fate to new DMs designing their own worlds, and it’s absolutely nice for any implementation, really not that hard, and definitely not to play or direct if u get the basics. I think Condensed its a truly fiiiine explanation of fate, coz sometimes people get the blank-page syndrome when you put too much freedom, and claims for pre-sets, but then u could explain too much and intimidate. Thing is, people should work a little XD
    I made a system that was a lot like fate, but calling feats and gifts, what you call aspects and stunts, basically, so maybe i found it really easy bc of that. It was after trying to make a DM bot, that realized all RPGS could be resumed (mechanically) as attributes modifying difficulty checks. When yo throw dices against another it’s a random-diff, the example of fire is great. The whole world, terrain, weather, are all “aspects” that either beneffit or complicate certain actions.
    The ability to zoom in or out for skills, with the idea of niches is just crytal clear to me, but found a lot of people had trouble with it when creating (making a skill-tree helped them see that general-particular zooming issue, for example). Like, it’s hard to get that THE RULE IS TO BEND ANY RULE, or something like it.
    For example, there were racial feats that mattered a lot, you can make ASPECTS (always true to some degree, spending fate points to get leverage), STUNTS (extra if u want them to have more to choose, or spending some of the 3 free at the beginning if u want to make it count, restraining with stunts conditions -time, situation, FP, even refresh or -i love this one for incredibly powerful things- tanking consequences), or you could turn them into SKILLS (passive) that are only available for some races. Same goes for spells, special tools, status, or vehicles. You want to separate tanks from cars? more stress/ consequences spaces, and the shooting skill, with the stunts of machine-gun and cannon. The aspect “heavy”, could be used to absorbe damage instead of creating the mentioned strs/cnsq, and forced while crossing a bridge, alerting enemies, or going through snow/sand/ice/mud/whatever (scene aspects or environment stunts).
    Sorry for the lotoftext or self-reference thing, but think some of those examples can be helpull =) There again, thank you for everything!

 Leave a Reply

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>



This site uses Akismet to reduce spam. Learn how your comment data is processed.