|Joshua J. Frost|
|baron arem heshvaun|
|Paizo Pathfinder® Paizo Games|
|Pathfinder Adventure Card Game Pathfinder Roleplaying Game Pathfinder Adventures Pathfinder Campaign Setting Pathfinder Player Companion Pathfinder Accessories Pathfinder Miniatures Pathfinder Fiction Pathfinder® Society™ Pathfinder Roleplaying Game Compatible Products Pathfinder Apparel & Gifts Pathfinder Licensed Products|
Pathfinder Society Scenario #22: Fingerprints of the Fiend (OGL) PDF
Paizo Publishing, LLC(based on 9 ratings)
A Pathfinder Society Scenario designed for 7th to 11th level characters (Tiers: 7–8 and 10–11).
When a retired Pathfinder's nephew goes missing after allegedly discovered the fabled city of Rachikan of the ancient Jistka Imperium, he turns to the Society for help. Now you've been sent to the coast of devil-tainted Cheliax to uncover the missing nephew's whereabouts and to, quite possibly, uncover one of the most sought-after legendary cities on Golarion. But you have to move quick! The Aspis Consortium is rumored to be racing to the site ahead of you and their involvement could spell disaster for the Pathfinder Society.
Written by Larry Wilhelm
This scenario is designed for play in Pathfinder Society Organized Play, but can easily be adapted for use with any world. This scenario is compliant with the Open Game License (OGL) and is suitable for use with the 3.5 edition of the world’s most popular fantasy roleplaying game.
Fulfilled immediately. Will be added to your My Downloads Page immediately upon purchase of PDF.
Are there errors or omissions in this product information? Got corrections? Let us know at firstname.lastname@example.org.
A few suggestions for Homebrew, set far to the west of the Inner Sea.,
How can my archivist bard best help in combat?,
The Knight-Errant, a class for fallen paladins (2nd draft),
Is Contagion Contagious?,
Protoplasm - how is the attack resolved?,
Star Wars Rebels,
Considering Purchasing HeroLab -- What's Good and What's Bad?,
A request for clarification from management wrt the SLA FAQ change,