Jason S's page

Opal is a mix of roleplay and skill checks and is one of the most flavorful scenarios in Pathfinder Society.

As many have mentioned, the scenario shows you a culture you have never seen before, which was the highlight of the scenario. I wish more scenarios were like this, because it just didn’t tell us about the culture, it showed us the culture.

The big drawback to this scenario is that it runs long. My session ran 6-7 hours.

One of the things that PF2 isn’t doing well in its scenarios, is making skills checks fit into an awkward, very mechanical, non-creative, obstacle framework. The obstacle framework kills creativity and just doesn’t work most of the time.

Also, the edge point mechanic didn’t really work in the masquerade, my PCs earned too many edge points (12 edge points), meaning it was basically impossible to fail the dance since they needed only 18 dance points. I made them do it anyway. The edge points might have been better implemented as free re-rolls, or perhaps not at all. A highly skilled group was already going to succeed at the dance, the edge point mechanic just made it so that highly skilled group didn’t even need to do the dance.

At subtier 5-6, on paper the fights looked deadly, when in fact they were cake walks for my group.

The method for opening the vault wasn’t well described and my game stalled there after delivering too much damage to my PCs.

Again, I’m not sure how you do this scenario in 4 hours without a lot of handwaving and calling off battles when you know the PCs will win.

The custom art in this scenario was fantastic.

Overall: A very flavorful journey and one of the best examples of how trips to foreign lands should be in Pathfinder Society.

Seven is a skill-based scenario with limited combat and roleplay.

Seven is a short 2-hour scenario that is difficult for a GM to run well the first time.

There is no roleplay in this scenario. I advise anyone who runs it to allow a conversation with the students and the principal before they investigate. It will also help a lot with the story.

The mystery is really awkward and is not done well IMO. I wish skill checks were done more organically, for example, if you succeed on a craft check, you learn this. If you succeed at an Occult check, you learn this. But somehow, you get to pick between 4 skills (which in many cases made no sense) and then get information unrelated to those skills. The mysteries were also not mechanically relevant at the end, not even for reporting. Sigh.

The final encounter, and how it is meant to be run, is not explained well. As such, you’ll have huge amounts of variation as GMs try to do what was intended. For many groups, it will be a dissatisfying conclusion.

I had one group dislike this scenario and one (kids) group thought it was OK.

Overall: I like that Seven is a different type of scenario, but ultimately the limited roleplay, uninspiring mystery, and final encounter will make it dissatisfying for some players.

I can't believe this mini is my most used non-PC mini.

I use it mostly for zombie brutes. But it's a great fill-in for many different large opponents. The mini is so gross and creepy, everyone appreciates it.

Anyway I just wanted to give a thumbs up to this mini.

Never is a skill-based scenario with some roleplay.

A lot of the scenario is spent with the GM reading box text and exposition. And the players rolling skill checks that are specified at each location. As I've mentioned in other reviews, it's not a satisfying experience and is a really cheap and lazy way to make scenarios. Go here, read description, use skill XYZ, next.

The roleplay is mostly with the skull, is mostly exposition, and will vary from table to table. For us it was OK only.

The combat encounters were almost identical to any combat encounter you’d have in a level 1 scenario. Fighting creatures we’ve fought many times before. We’re in Quantium, arguably one of the weirdest and most advanced cities in Golarion. I felt the encounters could have used creatures not typically seen, or who were unique. At least skinned differently?

Again, I dislike the cartoony season 4 artwork and much prefer artwork from previous years of Pathfinder.

Wonder is a skill-based scenario with mundane encounters, and several interesting NPCs.

Before continuing the review, I just want to say that I really dislike the cartoony season 4 artwork. Please, stop, have Pathfinder use more realistic artwork like we had in season 3 and previous years.

This scenario featured too many skill checks. Random skill checks are not fun, and it feels like this is the direction that many scenarios are taking. It’s really a cheap and uninteresting way to make scenarios. Go to this location and roll X, Y, or Z skill. Yawn.

To make matters worse, this scenario had some of the most cliché and mundane encounters you could imagine for level 1.

At the end we failed (multiple times), it seemed we were dead, but everything was OK.

Crossroads is a scenario that is mostly investigation and roleplay punctuated by several extremely deadly encounters.

It’s essentially what every one else is saying. Although I rated it as 5 stars for my home game (I modified the scenario), it is probably 2 stars when it comes to a 4-hour slot.

The most obvious problem is that the scenario took 7 hours, and I removed the first encounter (as was suggested in the reviews).

This scenario is a sandbox (there are many ways to solve it) but the way that the scenario is written, it ASSUMES certain choices will be made. If you plan to GM this, you will need to spend a lot of time preparing it and understand the motivations of the NPCs and the choices the PCs have. It’s not super clear and a lot goes unsaid. This scenario isn’t a railroad, some GMs just didn’t prepare enough and/or have enough imagination.

You can get stuck if a certain NPC dies, and the scenario doesn’t explicitly tell you the alternatives and leaves it to the GM to make them up.

The encounters (as written) are not simple, can be extremely long and drawn out, and are potentially deadly. The problem is, there’s more than 1 encounter like this, and it doesn’t work in the time constraints.

Overall: If you have 8 hours to play this, I think it’s worth it. Everyone loved it. (9/10).

I'm giving this book 4 stars more for its potential and the framework surrounding Korvosa and the campaign. You can use Anarchy "out of the box" but IMO you need to tweak it.

The main problem with this book are the plot hooks. They're just terrible. The main plot hook that unites the PCs is revenge. Not only is this goal dead simple of accomplish, but it's over in one session, with nothing remaining to keep the group together. To keep this AP going, it's imperative that the PCs care about Korvosa and wouldn't want it destroyed. Instead, if you make the AP about revenge, it feels forced to keep the PCs together because in reality they would probably go their separate ways after XXX is dead. This is a significant weakness.

The other significant problem with Anarchy is that it wasn't made for Pathfinder. In 3.5, a CR 1 fighter was level 1 (and weaker than the PF version). In Pathfinder, a CR 1 fighter is level 2. If you look hard enough, there are fan based resources that can help.

I also felt that too much word count was spent on NPCs that didn't matter and had backgrounds that would never be known (Ex. Vancaskerkin).

Another criticism is that some of the mini games aren't relevant. Knivsies is cool, but not if it's easy to kill Devargo without bothering. Harrow points ... could have been better (I made them allow free rerolls).

Although that seems like a lot of criticism for this book, it has the outline to be a fantastic experience. You can basically put whatever "spin" on the locations and NPCs you wish. There is fun to be had.

The NPCs in this book are also compelling (if given a chance), which is a strength of this book. When I ran it, we did a lot more roleplaying than the book suggests.

So by all means, play Anarchy, it's great. But just realize that you'll have to do some work to make it awesome. 

Struck is a combat-based scenario that is very repetitious and uninspired. No roleplay, no investigation. And at no point was it challenging.

I was looking forward to the boss fight and thought it might present a challenge but he died in 1 round too. Sigh.

I agree with the incompetent review. One punch will leave the enemies crying for mommy.

Important information was missing from the scenario, such as what happens if the PCs rest 10 minutes? 20 minutes? 2 days? It also didn’t talk about light sources.

The scenario was easy to read, but several things could have been simplified even further. Such as the items that were given to the PCs.

Confirmation is a mix of investigation followed by a dungeon crawl.

The best part about Confirmation is the main NPC, Rains. He is cute, unwise, and can add fun to the party.

Paizo needs to understand what make a good renewable story. It’s not about changing monsters necessarily, it’s about subtle changes to the story, or what needs to be done.

The main problem I have with this scenario is that there is no theme around the encounters. It's just random creatures, thrown together. I really dislike this. The repeatable nature of this scenario doesn’t add anything for the player and makes it more inconvenient to prepare for the GM, adding word count where it's unneeded.

There was also some redundancy that added to the word count.

One last comment. If you want your scenario to be found, put it in a season. For months I missed this one because it’s at the bottom of the main page, uncategorized. Or perhaps put it in both a season and at the bottom of the main page, like you do with other introduction scenarios.

Overall: An OK scenario with a cute NPC. (7/10).

Trials is an equal mix of investigation, puzzles, and combat.

Whatever this scenario was when it was first released, is not what it is now.

Except for the final combat, the combats and challenges are relatively easy and even my group of children age 7-11 were able to figure everything out.

I thought the investigation was great, if roleplayed (instead of just checks), it can be memorable.

The puzzles were also fun and not overly difficult either, perhaps too easy.

The combat was also reasonable and without risk.

March is a combat based scenario with some skill challenges.

March is just a solid adventure. Having said that, some of the story was lost with convoluted explanations. I didn't understand the 2nd encounter until I asked the GM after the game.

I appreciated the quick scenery that was given, that would cause most PF1 groups to buff.

I've been playing mostly season 1 scenarios and I noticed that there was no explanation of challenge points or which subtier we should be playing. My GM didn't have it memorized and he needed to rely on me to figure it out. I think it should be included (we almost played at 18 challenge points instead of 10...).

I don't think the scenario is complete without doing the optional encounter at the end. Having said that, it is quite challenging and the scenario could run long.

Falcon is a skill-based scenario followed by a combat.

I’m not sure what the other reviewers played, but there was no roleplay whatsoever in this quest. Any roleplay was basically fabricated by their GM, who could fabricate roleplay in any campaign and any environment.

I also found the ending combat not particularly interesting or challenging.

Overall: An OK quest but nothing unique about it.

Parchment is a quest mostly focused on skill checks followed by a combat.

There are several things I didn’t like about this quest:
1) Not knowing the Qadiran language didn’t factor in the quest or any skill checks. At worst it should have made the quest impossible, at best it should have made even trivial tasks much more challenging.

2) There was nothing unique to Qadiran culture or nothing to learn about it. They might as well have been wearing costumes in a generic fantasy setting.

3) There were too many possible skill checks for each location. It’s not important to cater to everyone, especially when the penalty for failure was very low in this quest.

4) The skills checks didn’t make any sense.

5) The combat was very run-of-the-mill.

Overall: I didn’t like the skill checks, they felt almost random. I didn't like that Qadiran culture was like every other generic culture. But most of all I felt like I could have just thrown this quest together myself on-the-fly.

Trail is mostly skill checks and some roleplay followed by a devastating combat.

I'm not going to run this scenario for my group, it's too deadly for my level 1 group: Two rogues, a wizard, and a druid. I ran the stats, they don't have the damage output to win.

Bandits is an escort mission and pure combat scenario.

I really enjoy the odd combat only scenario and I thought this scenario had a lot of great ideas in it. The combat could get tactical in this scenario, which I liked.

I thought the box text was very usable, which is not usually the case. I also like how encounters are laid out for GMs now in PF2.

Unfortunately:
- The environmental factors make PCs much less proficient than normal, and it’s out of their control. Some players won't like that.
- The combats can last longer than normal but are non-threatening.
- There are factors where you can lose treasure bundles, maybe even significant ones, and most players hate that.

Living Lodge is a mix of mini-game, roleplay, and combat.

It’s pretty much as the other reviews say, the mini game will take the session easily over 4 hours, our session went 6 hours. And that was basically with skipping 2 of the encounters. If you want the session to be 4 hours, I’m convinced that you need to skip the mini game.

Also, regarding the mini game, some people will love it and some will hate it (as you can see from the reviews). I had one player love it and 2 other players hate it, 1 was neutral. And I had it organized well.

The PCs finished the mini-game 10 days early, and they literally finished everything. So, the order (and priority) in which they decided to do things didn’t matter, which made the mini game a complete waste of time.

The handouts for this scenario were more for the GM than the player. The NPC handout was too revealing, and the mini-game handout also had too many details.

Also, I found several editing errors. The most glaring are the lack of skill modifiers for the NPCs involved in the mini game. I also found some errors in the stat blocks, one which mattered.

Scarecrow is a mix of investigation, skills, and combat.

Scarecrow is a fun time and it has surprising depth for a bounty and can potentially even have a moral decision to be made.

The only bad thing you can say about it is how long it takes. For roleplayers, it will take much longer than an hour. For us I believe it took over 2 hours. It takes time investigating five locations.

Overall: One of the best bounties. I've GMed this 3 times now and every game we come to a different conclusion and finale. Just excellent.

Blooming is a mix of everything.

It's a well written scenario, almost overwhelming, that supports multiple solutions to several problems and a sandbox approach to the scenario. It should not be run cold.

There were several great scenes in the scenario.

I've GMed it three times now at subtier 1-2 and had a blast each time.

The only downfall to this scenario is that it can run too long. My last session ran 4 hours but the previous sessions ran 6 hours each.

This scenario is a mix of investigation and combat.

This scenario actually has the potential to be really good (4 stars), but it suffers from several flaws:

1) The premise is nonsense: Like others have stated, Pathfinder Society has been devastated, we should be recovering bodies, not risking our lives behind enemy lines, just to retrieve the sign of an old inn, a statue (!?!), paintings, or ceremonial armor.

2) The flow is terrible: Too much travel, too much searching, too much investigation. There are details in the scenario that unless the GM reads ahead, makes notes, and simplifies, will bog the scenario down and bore the players. As a GM, this was not easy to prep.

3) The final combat is too hard: With my group, I had them down to the last PC, and I was holding back. This was subtier 1-2.

I want to give this more stars, there are some great details and creative ideas, but it could have done with some better editing, particularly with the scaling in the final combat. Having said that, this scenario could potentially be salvaged.

Lions is a simple combat and skill challenge scenario.

I guess if you are amused by goblin silliness, this might be for you.

The scenario can (and should!) be quite brief.

There is nothing wrong with this scenario, it’s just that generic replayable scenarios are not what I’m looking for in a game.

This scenario is basically an assassination mission.

It was over fairly quick, in less than 2 hours. For us was not particularly challenging. Maybe it would have been better if special tactics weren't used.

One of my favorite scenarios from PFS 1.

A great epic final encounter.

This scenario had several unique combat encounters suitable for high level play.

There was a roleplay section at the beginning that I didn't find to be very memorable. The location itself was though.

We played at subtier 12-13 on normal mode.