Pathfinder: Kingmaker Update 2.0.7 Live

After releasing the final bit of DLC as well as the Enhanced Edition for Pathfinder: Kingmaker back in June, Owlcat Games refocused their efforts on ironing out the game’s remaining bugs and issues. This resulted in a number of fairly meaty updates, the latest one of which went live just a few days ago. Here are the patch notes:

Please be aware of plot spoilers in the description below!

Classes

• Strength Surge, Cleric’s strength domain ability, did not work on allies. Resolution: fixed.
• The Russian description of the Touch of Good ability (Good domain) incorrectly mentioned that it gave a bonus equal to the level of the class that granted access to that domain. In fact, the bonus amounted to half of the class level. Resolution: fixed.
• Remove Fear did not work against Frightful Presence. Resolution: fixed.
• Magic Fang and Greater Magic Fang did not show up on characters as a buff. Resolution: fixed.
• Studied Target, Freebooter’s Bane and Quarry abilities now work correctly when used by different characters on one target.
• Resistant Touch ability of the Protection Domain was not giving bonuses to the target. Resolution: fixed.
• Feybane ability of the Defender of the True World (Druid’s archetype) did not provide bonuses to saving throws against fey. Resolution: fixed.
• Sorcerers and Eldritch Scions with the Arcane or Sage bloodline were unable to use their Bond item to restore spells. Resolution: fixed.

Items

• Cloak of Sold Souls summoned a friendly Thanadaemon. Resolution: fixed.
• Mail of Clear Skies was not considered a light armor. Resolution: fixed.
• Thundering Claw of the Bear God did not work with Beast Shape III; Call Lighting was cast also if an animal companion landed a critical hit. Resolution: fixed.
• Disruption Thundering Heavy Flail +2 was a regular flail, not a heavy one. Resolution: fixed.
• Bleed inflicted by Serrator did not work in the first round. Resolution: fixed.
• The effect of Tangled Claws did not have any visuals on a target. Resolution: fixed.
• Skin of the Rough Beast had incorrect sounds and ability visuals. Besides, the ability affected not only enemies. Resolutions: fixed.
• Scroll of Cape of Wasps had DC = 0. Resolution: fixed.
• Blakemoor’s grimoire description was not properly displayed. Resolution: fixed.
• Ring of Circumstances now correctly continues to grant its bonuses after resting. The Narrow Path amulet checked the alignment of the wearer instead of the target. Resolution: fixed.
• Mail of Clear Skies had incorrect stats. Resolution: fixed.
• Lycanthrope Bane Disruption Club +3 had an incorrect price. Resolution: fixed.
• Singing Steel Breastplate had an incorrect price. Resolution: fixed.
• Adamantine Breastplate +3 had an incorrect price. Resolution: fixed.
• The Bladed Plate item incorrectly appeared in Kaessi’s house in the capital. Resolution: fixed.

Miscellaneous

• Some new locations for random encounters did not have names. Resolution: fixed.
• The icon to exit the Silverstep Grove area was located too low. Resolution: fixed.
• Fixed a collision problem on the stairs of the Academy of Grand Arts in Pitax.
• Sometimes players could get stuck in the Owlbear cage at the Stag Lord’s Fort. Resolution: fixed.
• In some cases, players could hear the crying woman near the Bridge over the Gudrin River even if she had already left. Resolution: fixed.
• In the dungeons under the Old Sycamore, the player could first sent Harrim to Oleg’s Trading Post and then dismiss all the companions. After that, Harrim would remain in the party but his companion dialogue would become unavailable. Resolution: fixed.
• In the Troll Lair, the “Tell Ekun about our victory” objective appeared even if the player had already killed Ekun on the first encounter. Resolution: fixed.
• At the Capital Tavern, citizens sometimes got broken and stopped sitting at the tables. Resolution: fixed.
• The first dialogue with Darven in the Deal with the Devil quest could be repeated erroneously. Resolution: fixed.

A friendly reminder: while we deeply admire the contribution that mod authors make to our game, we would like you to remember that running custom modifications can lead to unexpected bugs and crashes. Unfortunately, if you encounter any issues while playing with mods, our team will not be able to help you. If this happens, please report these issues to the mod’s original creator. Also, remember that after each game update, there is a high probability of previously installed mods not functioning properly. If you wish to play with mods anyway, disabling auto-updates might prevent your save files from becoming corrupted.

And if you’re interested in what the earlier updates brought to the table, you can find their patch notes right here – update 2.0.4, update 2.0.5, and update 2.0.6.