Good Old Games
Donate to Codex
Putting the 'role' back in role-playing games since 2002.
Odds are, something you like very much sucks. Why? Because this is the RPG Codex
News Content Gallery People Games Companies  
Forums About Donate RSS Contact Us!  

Pathfinder: Kingmaker Kickstarter Update #40: Chris Avellone Companion Design Guide, Part One

Visit our sponsors! (or click here and disable ads)

Pathfinder: Kingmaker Kickstarter Update #40: Chris Avellone Companion Design Guide, Part One

Development Info - posted by Infinitron on Thu 24 August 2017, 21:36:51

Tags: Chris Avellone; Owlcat Games; Pathfinder: Kingmaker

After a couple of fairly uninteresting Pathfinder: Kingmaker Kickstarter updates this month, Owlcat Games decided to ask Chris Avellone to write an update about his work on the game's companions. As usual, he outdid himself, producing a lengthy multi-part editorial about his companion design methodology. With a bit of cleaning up, it could easily be its own article unrelated to Kingmaker. The first part of the editorial is about companion balance - the fine art of tweaking companions to ensure that they're all maximally worthwhile and useful to the player. Here's an excerpt:

I understand math is the worst subject for any ex-English Major to discuss with any authority, I know, but “the maths” have so much to do with companion design and companion arcs that it deserves some explanation. Or, in this case, a lot of explanation. Because you know us writers, we love them words.

That said, here’s a list of system questions we ask about each companion for the sake of math – and why it’s important for narrative to take these mathematics into account when constructing a companion.

- How does the character systematically fit into this party – does the companion showcase one of the range of races the game offers, especially ones unique to the game and franchise? (Goblins in Pathfinder, for example, exemplified by the companion Nok-Nok in Kingmaker.)

- Class is important narratively as well – not only for franchise-specific classes (hey, here’s a sample of one of the unique professions in the world), but also because you can’t divorce character class from a character’s backstory or their personality – a druid is likely to have a much different upbringing outlook on the world than a rogue, for example, and you need to know what “career” the companion fell into/choose in order to backtrack through their life to build the reasons they chose it – or why the class chose them.

- Is the companion progression done in such a way where the introduction makes sense (ex: you don’t want 2 fighter companions at the outset of the game, but you might want 1, and perhaps also a cleric for healing because giving the player a tank or healer early on as a companion is a great idea – even if the player is a member of both classes). In Planescape: Torment, we introduced Morte first, not just for narrative reasons, but because he is a floating shield that can take a lot of damage, can intercept enemies for you (or lure them to you), carry your stuff (he’s a floating backpack), and inform you about the world.

- Be careful on how you build the companion’s attributes and skill set – they need to follow the exact same rules as the player, and you want to build them in such a way that you don’t make them so specific they can’t make use of certain items in the game (extreme example – but if the paladin companion isn’t built in such a way that she can make use of the best paladin sword in the game, then you’re going to have some angry players – also, it goes without saying, that if the PC is a paladin, the PC gets the best paladin sword).

- It’s an excellent idea to give companions unique traits, unique inventory items, but take care that the companion is not “built” incorrectly (ex: he has higher attributes than the player would be allowed to have) – it’s irritating for a PC to traverse a game with a companion who has the same class as they do but they happen to have an unfair rack of stats, which means the player ends up being second fiddle, math-wise. And players will calculate each point and do comparisons, it’s a given. So mind the rules, even if you’d like to move points around.

- A dash of systemic spice is always welcome. What I mean by this is that the companion may have some item, trait, ability, or twist on their skills that complement their personality. It can be a diary or a space hamster. It can be a unique weapon only they can use (just don’t make it better than any other weapon a player can get, and try to give it room to grow).

- Be careful in assigning skills and attribute points to companions so that you’re not dumping points in skills and attributes they can’t even use. Example: Some games don’t allow companions to “speak,” which often means that giving them Charisma bonuses or adding to their Charisma is useless because it doesn’t do anything – if that’s the case, you might want to expand any attribute or ability that only the player can use but the attribute is shared by both the player and companion (this can be solved in other ways depending on the game design – either never allowing Charisma to be added to, or re-designing the dialogue interface – what I call “Tony Evans style” – so everyone can participate in a conversation and each one can use their stats).

- Balance the placement of the companion so that they are introduced in an area where they systemically shine (not just narratively, but combat, exploration, and tools-wise). Make sure that when the companion is gained, he’s useful immediately and if possible, he’s awesome in the immediate environment. Example – during your adventure, you might be trapped in a field of explosive spells and deadly traps, and Nok-Nok suddenly walks up (perhaps walking across the mine field in his own special trap-detecting way). Perfect. You have your own goblin mine-detector (one way or the other).

- But don’t solely have the placement be something that is a challenge or obstacle, introduce reward with it that the companion can help you reach (you may have encountered a locked chest you couldn’t open earlier in the map, or have a chance to unlock doors and cages in a mage’s storeroom). Maybe you’re a fighter who just found a wicked dagger called The Onyx Vertebrae which happens to be a dagger +2, +4 with Backstab – it’s a good weapon, but you already have a better sword. Still, when Nok-Nok appears, you know exactly who to give it to. After you teach him not to hold it by the blade.

- It’s to your benefit not to let the player get too comfortable with their roster if you’re introducing a lot of companions or introducing companions late in the game. Some players “lock-in” their party and are resistant to change depending on when you introduce a companion (this is why Final Fantasy games often have specific intros for each companion where you are forced to journey with them long enough to get used to them, then they’d be free to be removed from your party – it’s more like forced exposure, but it’s done with the purpose of showcasing that companion).

- Even death involves math – an extreme example, but the tragedy of having decide to save one of two companions is made cheaper when one has a skill set that nobody else. And it’s worse if that same skill grants the player the ability to gain special items, access to more chests, or access to secrets and bonus areas vs. the generic “fighter”. The choice then becomes less a role-playing a choice vs. “well, if I lose him, I’d lose my ability to pick locks anywhere in the world.”

- Lastly, the companions should reinforce or interact with the key systems in the game as well – for example, the player’s Kingdom. Having companions or not having certain companions should cause (and does cause) changes in one’s kingdom in Kingmaker, sometimes for the best, sometimes for the worst – each companion needs to have that “system kingdom arc” spelled out, as when writing them, you’d need to foreshadow and explain personality-wise and dialogue-wise why certain events may occur.

So let’s take our squat little maniac goblin Nok-Nok as an example and examine his schematics. He’s franchise-specific (goblin), he fulfills a role rarely held by other party members (rogue – a class that I find not many people I know seem to take as their primary character, but every seasoned RPG’er knows they always want a rogue in the party to open stubborn locks and get to places only thieves can go as long as it’s not the player that has to waste the skill points). Furthermore, he’s evil-alignment-friendly and can round out a part of evil characters although arguably his trait of being doggedly loyal means he can bond with other alignments (though they may not appreciate this), and he has a few goblin and personality-specific skills that Owlcat and I have kicked around for him being a goblin – some examples (not set in stone) – he may have the ability to gain ugly pets (goblins have the worst “pets,” but Nok-Nok can help you gain them), or he may gain unusual “trophies” (junk) that bolster his confidence as he regards them as relics, and if possible, he may even have the ability to have a unique trap disarm that uses his body as a shield for the damage – and trap damage resistance as a result of being the victim of this ability once too often.

Furthermore, his motivations are very much intertwined with the religion of the world and the religion of the goblins – and then takes it a step farther by wanting to be part of the goblin pantheon as their fifth god. He has impacts on your Kingdom (and on this, I can’t give spoilers). So there you go!
Good stuff. It's still unclear to how much of this game is actually going to be written by Chris, but he's definitely putting a lot of thought into it - and leaving us with a invaluable chronicle of his design philosophy. Coming up next in Part Two, Chris will describe his process for developing narrative outlines and character arcs.

There are 13 comments on Pathfinder: Kingmaker Kickstarter Update #40: Chris Avellone Companion Design Guide, Part One

Site hosted by Sorcerer's Place Link us!
Codex definition, a book manuscript.
eXTReMe Tracker RSS Feed
This page was created in 0.0701940059662 seconds