Paizo Top Nav Branding
  • Hello, Guest! |
  • Sign In |
  • My Account |
  • Shopping Cart |
  • Help/FAQ
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 Roleplaying Game


Pathfinder Society

Pathfinder Adventure Card Game

Pathfinder Society Scenario #3-08: Among the Gods (PFRPG) PDF

**½( )( ) (based on 14 ratings)

Our Price: $3.99

Add to Cart
Facebook Twitter Email

A Pathfinder Society Scenario designed for Levels 3–7.

The Pathfinder Society sends the PCs to the mountaintop mausoleum and monument known as Antios's Crown in search of a long-lost relic believed to be contained there, but all is not as it seems. Can the Pathfinders survive the denizens of the remote mountain complex and the sinister plot of a powerful cultists who plans revenge on the Society that has foiled their plans one too many times?

Written by Michael Kenway.

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 Pathfinder Roleplaying Game.

Product Availability

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


See Also:

Product Reviews (14)
1 to 5 of 14 << first < prev | 1 | 2 | 3 | next > last >>

Average product rating:

**½( )( ) (based on 14 ratings)

Sign in to create or edit a product review.

Wow this is a player abusive mod!

*( )( )( )( )

TLDR; Mod sucked, our GM great. Don't play if there's another choice. GM only if you have no ill intent in your soul (and are a generally kind GM by other peoples reckoning).

This mod was SO bad I felt compelled to write a review. The GM was very nice. He had suffered when he played it so he knew the players pain. I read the adventure through after playing it.

While it's true that there are many "not-often-used" rules that are "in the book". PFS (and many home games) tend to use a sub-set of the FULL RULES. I agree it CAN BE enjoyable when adventures use some of those parts of the rule set that aren't often seen.

However, this scenario is written and such a way that it begs the GM to abuse the players. There are rules in the GMG for the situations in the mod(traps, altitude and so forth), that the mod disregards the GMG in favor of the rules given in the mod.

"Mean" is a correct word to use when describing this adventure. It seems the author and most of the players/GMs that I've talked to or read about have a very different version of the word "fun" than the author does. PFS is supposed to be FUN first.

The basic theme appears to be: beat down the players with situations that are so uncommon or unannounced they won't be prepared for them. Then once they are beaten down use encounters that would normally be challenging. This results in what appears to be WILDLY over CR encounters (when counting in all factors and not use the CR of the creatures).

The amount of grey area wiggle room for the GM is very large. At a home game with known players and known GMs less of a problem. At a large con with very different players and GMs this could easily be a TPK (i.e. NOT FUN).

Imagine an entire adventure filled with six-armed, grappling monkeys that see in the dark and can breath water. That's bad. Also the encounter takes place in the bottom of a magically darkened, water filled mine shaft. VERY Bad. That's a bit of poetic exaggeration, but you get the idea.

This mod needed WAY more editing and thought ESPECIALLY with the rewards given. I wish I could give a zero star review.


Among the worst

*( )( )( )( )

This scenario is the most mean spirited one I've encountered since 5-20.
It introduces two custom rules that only exist to give the middle finger to PCs.

#1: Traps. Apparently, in this scenario traps can only be detected if we are using a scout. Regular perception checks and "we're looking for traps" doesn't work. For whatever reason one person has to go ahead of the rest of the group to "scout" to find traps. We only find this out after setting off a trap of course.

#2: High altitude. One of the party members had the boon from 7-06 that allowed them to function at high altitude without penalty. The GM said that the boon didn't apply because this scenario uses "custom altitude rules" not covered by the boon.

It was interesting how none of the creatures we encountered were suffering from the altitude effects like our party was. There was probably a 3rd custom rule covering that.

This is enough to give the scenario one star. Simply put, playing this scenario was a rotten five hours.

Note: I've read the other reviews for this scenario. None of them mention the custom rules. I'm not sure what to say about that.

Read up on altitude rules before you play this

***( )( )

Really. The altitude rules are not a secret, they're right there in the core book. You're told in the briefing you're going up a mountain. Put things together, and think on what impact it'll have on your party. It'll save you some grief.

Apart from that, I thought this was an okay adventure but with some flaws. The encounters were challenging and varied, with enemies you don't run into often or at all. There isn't much story though, and the final guy looks like a total random insert into the story. It'd be a total surprise except for the title of the scenario, but otherwise its a complete coincidence that he also happens to be at the place where we're going.

Just a WTF

**( )( )( )

This was lethal for 6-7. If you can avoid doing that tier, do so. Even the 3-4 had unnecessary moments. At the same time, I weep for any of you who have to play this now like I did because you are pretty much guaranteed to never get your second prestige with the new secondary conditions that were written. There is absolutely no way our party could have avoided this, and we had a dedicated character who was built for that kind of condition. And we still couldn't do it. As well, that end DC was absolutely ridiculous for a 3-4 tier. If you don't have someone with feats and skill ranks dedicated to Perception, be ready for disappointment.

Just a lot of unnecessary. The entire table groaned when we found out what we'd lost out on because we couldn't make the DC 25 Perception or what the secondary condition was.

On top of that, the editors need to read these more carefully for missed words and sentence structure.

The only upside is that it was a quick scenario.

Among the Worst

*( )( )( )( )

As much as it pains me, I do believe the title of this review adequately sums up my opinion about this scenario. The only thing I liked about this scenario, was the fact I was playing it with friends. Let’s start by commenting on the plot. Wait, what plot? I’m sorry, but the storyline is pretty much non-existent. At best, you could call it very weak. Next up I’d comment on role-playing opportunities with the various NPCs, but I regret to point out there’s absolutely no possibility for that as well. And let’s not mention the very weird secondary objective. That one itself signifies issues with the scenario as that just screams ‘well, it’s better than nothing… ‘ and is just pretty weak.

Instead the scenario seems to be a bunch of combats mashed together in a seemingly random order and a few traps. That could be quite fun, but again I feel like the execution is over the top. You know things are bad when even the GM suspects the author of wanting to kill player characters. Without going into details, there’s just too many debuffs really. Some debuffing is fun, but this was too much.

Now, there’s always a chance you fail a save, but it's an issue when this results in having only one out of four partymembers being able to fight simply because he’s immune to something. Let’s be honest: that’s just no fun for everyone involved, especially since it’s a combat scenario. I know, it happens, but when over half the party is unable to participate in half of the encounters, something is wrong.

Even worse and I admit to being a bit biased here: I was only able to do something in one of the four encounters, purely because of the debuffs that were out of my control. In the end, I’m left with a feeling that I contributed nothing worth mentioning. I could see that everyone around the table was unhappy, annoyed or disappointed with how the scenario turned out to be. Luckily we could still make jokes out of character to keep our spirits up, but we have to be reasonable here: we’re playing this game to have fun and this simply didn’t happen.

The only bright spot of this scenario, if I really had to try and find one, was the first fight. And that was simply because I liked that enemy, as I had never faced something similar before. As such, and I’m almost sorry to say this, I recommend everyone to stay clear from this scenario. You should only play this scenario if you want to smash things and a have a very hard time while doing so.

1 to 5 of 14 << first < prev | 1 | 2 | 3 | next > last >> Gift Certificates
On Sale and Clearance!

©2002–2016 Paizo Inc.®. Need help? Email or call 425-250-0800 during our business hours: Monday–Friday, 10 AM–5 PM Pacific Time. View our privacy policy. Paizo Inc., Paizo, the Paizo golem logo, Pathfinder, the Pathfinder logo, Pathfinder Society, GameMastery, and Planet Stories are registered trademarks of Paizo Inc., and Pathfinder Roleplaying Game, Pathfinder Campaign Setting, Pathfinder Adventure Path, Pathfinder Adventure Card Game, Pathfinder Player Companion, Pathfinder Modules, Pathfinder Tales, Pathfinder Battles, Pathfinder Online, PaizoCon, RPG Superstar, The Golem's Got It, Titanic Games, the Titanic logo, and the Planet Stories planet logo are trademarks of Paizo Inc. Dungeons & Dragons, Dragon, Dungeon, and Polyhedron are registered trademarks of Wizards of the Coast, Inc., a subsidiary of Hasbro, Inc., and have been used by Paizo Inc. under license. Most product names are trademarks owned or used under license by the companies that publish those products; use of such names without mention of trademark status should not be construed as a challenge to such status.