{"id":113,"date":"2017-08-21T19:49:49","date_gmt":"2017-08-21T19:49:49","guid":{"rendered":"https:\/\/blog.nameless.zanity.net\/?p=113"},"modified":"2018-11-10T00:13:25","modified_gmt":"2018-11-10T00:13:25","slug":"designing-rpg-systems","status":"publish","type":"post","link":"https:\/\/blog.nameless.zanity.net\/?p=113","title":{"rendered":"Designing RPG systems"},"content":{"rendered":"<p>The following are some musings on how to make good RPG systems, and which mistakes or pitfalls to avoid, based on the systems I\u2019ve seen in various roleplaying games.<\/p>\n<p>Note that I am talking specifically about RPG character progression systems, and not the other staples of the genre such as dialogue, choices and consequences.<\/p>\n<p>I feel that a character system should:<\/p>\n<ul>\n<li>Have interesting and meaningful choices<\/li>\n<li>Differentiate gameplay between character builds<\/li>\n<li>Feel satisfying<\/li>\n<li>Avoid offering truly bad choices which only act as traps for inexperienced players<\/li>\n<li>Not get in the way of normal play<\/li>\n<\/ul>\n<p><!--more--><\/p>\n<h2>Levelling systems<\/h2>\n<h3>No bonuses that need to be kept until the end<\/h3>\n<p>It feels bad to get a bonus or reward and be unable to use it, because the bonus will be better \/ stronger if used much later in the game.<br \/>\nFor example, if you find a potion that can permanently increase your Strength by 1 point, if feels bad if you use it only to realise that it would have been more effective if you had used it when you already had much higher strength, due to the cost of increasing strength being exponential, or the attribute having a hard cap.\u00a0 Such a system just leads to the player hoarding such bonuses until so late in the game that they don\u2019t even get much use out of them, which lessens the impact of the reward.<br \/>\nIn this example, a better solution would be to make such a permanent stat increase act as a permanent bonus which isn\u2019t counted in the normal skill calculations for costs and limits.<\/p>\n<p>Another example to avoid is a allowing the player to make a permanent choice which initially only offers bad or lower-quality options, but allows them to choose a much better option later (provided that they didn\u2019t pick a poor option for the \u201cslot\u201d earlier.)\u00a0 The weaker options just act as traps for inexperienced players.<\/p>\n<p>&nbsp;<\/p>\n<h3>Progression systems should align with normal gameplay<\/h3>\n<p>The player should generally be able to progress by playing the game normally.\u00a0 Avoid systems where the player needs to vastly change their play style in order to get the maximum benefit from the progression system, and especially where the best progression is rewarded for really bizarre and unintuitive behaviours.<\/p>\n<p>The best example of what not to do is the old attribute-levelling system from The Elder Scrolls games <em>Morrowind<\/em> and <em>Oblivion<\/em>.\u00a0 In those games, each time you level up, you can choose to upgrade three of your statistics, with the amount of points gained for a stat being dependant on how much you used the skills associated with that statistic since your last level-up.\u00a0 This was combined with your health gain being based on your current Endurance stat, so the ideal way to play was to increase Endurance as fast as possible, which required getting 10 points of Endurance-based skills per level.\u00a0 The end result was a wizard character spending most of their early levels practising with spears and heavy armour, just so they could get a decent Endurance score and get decent hit points.<\/p>\n<p>Another common example is games which reward players with XP for defeating opponents, which can lead to players wandering the world murdering or beating up everyone, allies and enemies alike, for the XP.\u00a0 That can work perfectly for heavily combat-focused games where murdering everything to build up your character <em>is<\/em> the normal gameplay, but might not fit in other types of roleplaying games with a more heavy narrative focus.<\/p>\n<p>&nbsp;<\/p>\n<h3>Avoid use-based skills<\/h3>\n<p>Skills which improve as you use them seem like an obvious and realistic approach at first glance, but they don\u2019t work well as a game system.\u00a0 There is little in terms of interesting choice for the player \u2013 they merely become more powerful at doing what they were doing as they play.<\/p>\n<p>A point-based system, where you gain a fixed number of upgrade points as your character improves, gives the player far more interesting choices in terms of character development.<\/p>\n<p>&nbsp;<\/p>\n<h3>Fewer, more impactful options<\/h3>\n<p>Generally, the difference between having 43\/100 and having 44\/100 of an attribute is fairly negligible, unless that number happens to be the minimum requirement for something.<br \/>\nGiving the player fewer, more meaningful and impactful choices is far more interesting than giving them a lot of points but where individual points don\u2019t have much value.<br \/>\nThis depends a lot on the specific type of progression system being used \u2013 if upgrade points are acquired constantly but in small numbers (such as being able to spend XP directly as soon as you gain it), then having smaller-granularity upgrades is more reasonable, to give a feeling of constant progression.<br \/>\nIf upgrading is instead done in terms of a larger number of points all received upon levelling, then it feels much better to give a smaller number to allow for more impactful upgrade choices.<\/p>\n<p>&nbsp;<\/p>\n<h3>Reward for progression, not method<\/h3>\n<p>In a game which has multiple methods of approaching a problem, there shouldn\u2019t be a vastly different XP reward for the different paths.\u00a0 Rather than giving XP for specific actions performed during a sequence, such as killing or evading enemies, instead give a fixed reward for completing the overall objective.<br \/>\nThat way, players can find their own path, and don\u2019t feel compelled to \u201cgame\u201d the system by performing the actions that give the most XP (such as massacring every living thing in the area to maximise XP gain, or always using the weapon or takedown method which grants the most XP.)<\/p>\n<p>&nbsp;<\/p>\n<h3>Avoid arbitrary and unrealistic restrictions<\/h3>\n<p>While it might make sense to not be able to cast a fireball before you have learned how to do so, it makes a lot less sense to be unable to fire a gun or hold a sword without a requisite skill level, because those are actions that anyone could perform \u2013 albeit poorly.<br \/>\nFavour (possibly massive) penalties instead of outright restrictions.\u00a0 Allow anyone to fire a complex gun, but have an inexperienced user get far worse recoil, terrible aim, frequent jams, less damage, and\/or other penalties for their lack of knowledge.\u00a0 Allow a weak character to try to swing a heavy sword, but end up with incredibly slow and unwieldy swings that make the weapon too cumbersome to use effectively.<br \/>\nMake the player gradually able to use the weapon effectively as their skill increases, rather than a single hard point before which they cannot use the weapon at all, and after which they can use the weapon perfectly.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The following are some musings on how to make good RPG systems, and which mistakes or pitfalls to avoid, based on the systems I\u2019ve seen in various roleplaying games. Note that I am talking specifically about RPG character progression systems, and not the other staples of the genre such as dialogue, choices and consequences. I [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-113","post","type-post","status-publish","format-standard","hentry","category-game-design"],"_links":{"self":[{"href":"https:\/\/blog.nameless.zanity.net\/index.php?rest_route=\/wp\/v2\/posts\/113","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.nameless.zanity.net\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.nameless.zanity.net\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.nameless.zanity.net\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.nameless.zanity.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=113"}],"version-history":[{"count":14,"href":"https:\/\/blog.nameless.zanity.net\/index.php?rest_route=\/wp\/v2\/posts\/113\/revisions"}],"predecessor-version":[{"id":215,"href":"https:\/\/blog.nameless.zanity.net\/index.php?rest_route=\/wp\/v2\/posts\/113\/revisions\/215"}],"wp:attachment":[{"href":"https:\/\/blog.nameless.zanity.net\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=113"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.nameless.zanity.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=113"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.nameless.zanity.net\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=113"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}