I like Fate Accelerated. I really do. Hell, I’ve made two Fate World settings using it, and will likely make my third setting FAE too. That being said, it’s not perfect.
Sidenote: If it’s not perfect, why do I play it? To paraphrase Winston Churchill, “[Fate] is the worst form of [RPG], except for all the others.”
The best part of FAE is that there is always another way to skin a cat; if a party’s sorcerer has to leave the game early because they have work in the morning, you’re not suddenly stuck with a group incapable of overcoming the magic door down the hall; through cleverness, careful study, or barbaric vandalism, they will find a way.
The evil flip-side to this is that whenever you want to encourage a player to approach a problem from one of their lesser approaches, someone will insist that they can use their strongest approach; this frequently called “spamming.” While they mean well, these sophisters will turn every turn into a drawn out negotiation, which can kill the mood and drag the evening out. Of course, the GM could always say “No, you have to use this approach,” but that’s against the spirit of FAE, and saying “No” leads to an unfriendly atmosphere (one of my very first entries discussed how much a GM should say “yes.”)
Evil Hat’s Zen Master of Fate Rob Donogue has proposed some ways to get around this on his blog, The Walking Mind, but I thought I’d try one or two ideas of my own:
Option 1: the Permission Aspect
If a player wants to use an approach that doesn’t seem obvious Require a “Permission aspect” first. This will likely be a situation aspect. If they already have a character aspect, require that they invoke it (which gives them the ability to use the approach AND the invoke bonus).
Ex. Chartok, Marna, and Phil all want to attack the a vicious ingredient in Kitchen Arena, the Monstercheese. Chartok’s player wants to charge straight in using Forceful, while Marna’s player wants to use Clever, and Phil’s player wants to use Sneaky. The GM sees no trouble with Chartok using the Forceful approach to make a raw attack, but feels that using Clever or Sneaky is less justified in this instance. The GM requests they get permission aspects first: a rational person like Marna wouldn’t charge in blindly, but if zhe spends an exchange looking for a weapon first (create an advantage for a Giant Cheese Machete), zhe could attack with Clever during any later exchanges. Similarly, a sneaky attack from Phil out of nowhere seems forced, but if Phil’s player spends a fate point to invoke his aspect “Born in Shadows,” the GM will let him use Sneaky to attack (and also gets the +2 invoke bonus). The GM is feeling generous, and decides these invokes are enough to let them use those approaches for the rest of the scene, or until it no longer makes sense (ex. Marna loses the Cheese Machete; Phil uses Flashy to draw attention to himself.)
If the player has a weapon that’s also a stunt, which is tied to a specific approach (ex. The Bow in in Masters of Umdaar using Quick), then the character can always use that weapon to attack; however, they can only use it whenever it seems right for the weapon (ex. Can’t use the bow in close combat), and only if they possess the weapon (ex. They haven’t been disarmed).
Option 2: Critical Hit
If players don’t like the stick, give them the carrot! Whenever a character makes an attempt with an Approach that is Fair +1 or lower and succeeds, automatically treat the result as success with style. Thus, they have a lower chance of success, but a higher gain should they pull it off. A GM might offer this all the time, but it seems better to me as a bargaining chip.
Player: I don’t want to use Forceful to attack, I want to use Quick, it’s higher!
GM: Okay, but if you hit with Forceful, I’ll give you a Critical Hit bonus…
Which option sounds better to you? Tell us what you think!
Until next week, GAME ON!
Spam image courtesy of Father.Jack from Coventry, UK, Transferred from Flickr by User:Fæ. Used with permission through Creative Commons Attribution 2.0 Generic license. Neither licensor nor the Spam corporation endorses this blog or its use.