Book of Heroes

URL, Quote, Aesthetic/ Conceptual vs Mechanical Rational

Bj_Knows

ModeratorThu Aug 28, 2014 4:28 pm
Subject
URL, Quote, Aesthetic/ Conceptual vs Mechanical Rational
Josh Sawyer wrote:
http://kotaku.com/how-to-balance-an-rpg-1625516832

What Sort of Decisions Do We Want the Player to Make?

By this I mean not only the choices players must make at an obvious level—Strength vs. Charisma, fighter vs. rogue, sword vs. axe—but also, the criteria that drive those decisions. These criteria could be as broad as deciding between a character class that does a lot of damage in combat vs. a class that is great at navigating conversations. Or, they could be as narrow as emphasizing attack speed over damage done on a Critical Hit.

There are two levels at which players generally make these sorts of decisions. The first is aesthetic and conceptual: "Wizards are cool." "Clubs are boring." "Being strong owns."
The second is mechanical/rational: "High damage is important." "Gotta have a healer." "Debuff effects can make a huge difference in fights."

Different players balance these desires differently, but ideally an aesthetic choice will always map to a viable build, and a viable build will map to something players will find cool for their character. When this doesn't happen, it can result in a lot of annoyance from players. They are either forced to play something they conceptually like that is mechanically bad or they have to veer away from their character concept to be mechanically viable. In an RPG, this is undesirable — so say I, at least. That's why this initial stage should only end after you've soberly asked yourself important questions about why players would want to pick any given option you're presenting them.