A fruitful void is a part of a role-playing game that is not covered by the game's rules (procedural elements), but which the rules and system direct players towards.[1] In role-playing game theory, the fruitful void is a concept that says a game is not only about parts of play covered by game mechanics, but also about parts of play that are not covered by mechanics and yet are still central to the story.[2]

Vincent Baker has summarised the concept as a piece of advice: "design your game to pose a question, then don't design it to trample on the answers!"[3]

Fruitful voids allow players to engage with their subjects (which may be themes, situations, etc.) in their own way, by using their own creativity and without being subject to the limits of game mechanics. Not all games have or need a fruitful void, and not every sort of gameplay that isn't covered by mechanical procedures is a fruitful void.

The term was coined in 2005 by Ron Edwards on The Forge,[4] and has since been expanded on by Vincent Baker and other theorists.[1]

In 2019, Avery Alder said that the notion of the fruitful void was one of three game design theories from the days of The Forge and the Big Model that remain useful at the end of 2019.[2]

Examples of fruitful voidsEdit

See alsoEdit


Community content is available under CC-BY-SA unless otherwise noted.