Pathfinder Adventure Path: Into the Shattered Continent (Ruins of Azlant 2 of 6) (Pathfinder Adventure Path, 122)

Pathfinder Adventure Path: Into the Shattered Continent (Ruins of Azlant 2 of 6) (Pathfinder Adventure Path, 122) image
ISBN-10:

1601259727

ISBN-13:

9781601259721

Released: Oct 10, 2017
Publisher: Paizo, Inc.
Format: Paperback, 96 pages
to view more data

Description:

After working to secure their settlement on the lost continent of Azlant, the adventurers aid the colony by exploring the rest of the island in search of resources and to look for potential dangers. After a few days spent on exploratory missions and returning to the settlement each night, they begin to notice that some people in the settlement are acting strangely, a haunting echo of the clues left behind after the original settlers vanished. Sinister forces are at work in the colony and the adventurers must uncover a menacing threat to the settlement before they become the next victims of a vile plot.

“Into the Shattered Continent” is a Pathfinder Roleplaying Game adventure for 4th-level characters. The adventure continues the Ruins of Azlant Adventure Path, a tale of survival on the deadly island remnants of humanity’s first empire. A selection of new monsters, a gazetteer of the region, and a sampling of ancient treasures round out this volume of the Pathfinder Adventure Path!

Each monthly full-color softcover Pathfinder Adventure Path volume contains an in-depth adventure scenario, stats for several new monsters, and support articles meant to give Game Masters additional material to expand their campaign. Pathfinder Adventure Path volumes use the Open Game License and work with both the Pathfinder RPG and the world’s oldest fantasy RPG.


























We're an Amazon Associate. We earn from qualifying purchases at Amazon and all stores listed here.

Want a Better Price Offer?

Set a price alert and get notified when the book starts selling at your price.

Want to Report a Pricing Issue?

Let us know about the pricing issue you've noticed so that we can fix it.