A Starfinder Society Scenario designed for levels 3–6.
Summoned to investigate a new, exciting find near a frontier AbadarCorp colony, a group of Starfinder Society agents finds themselves exploring deep below the surface to inspect a recently uncovered set of ruins. However, they're not alone. The PCs soon discover not only that something is waking up, but also that there are some secrets best left undisturbed.
I played Waking the Past at low subtier using the four-player adjustment. Without having read any other reviews, my guess is that the scenario is one that people either love or hate. It has a particular gameplay mechanic that some will find pretty cool and exciting, while others will find it grossly unfair. This is a scenario for truly intrepid explorers only!
SPOILERS!:
I really like the backstory to Waking the Past, even if it's very reminiscent of the background of the antagonists in the classic Star Trek episode "Space Seed" (yes, the prequel to . . . "Khan!!!"). A group of pre-Gap extremists on Golarion were forced off-world for their views on human genetic purity and violent attacks on non-humans. This group, called the Twilight Throne, were powerful magic users and skilled scientists, and established new bases on a planet in Near Space called Thosum V. In one of these bases, an experiment to create a nanotech golem went very, very awry, as the creature eventually killed every sentient lifeform on the planet before returning to a state of hibernation in the base.
What the PCs in the scenario don't know, of course, is that they're headed to explore that particular complex. The story starts with a solid hook. AbadarCorp miners on Thosum V uncovered a sealed complex miles underground. Pursuant to their contract with the Starfinder Society, they've notified the group for an exploration team on the usual terms (the SFS gets historical insight, AbadarCorp gets any new technology or equipment). Venture-Captain Arvin delivers the briefing, and I like how the scenario establishes his prior connection with the elf overseeing AbadarCorp operations on Thosum V. The two are old friends, and cooperation is the order of the day (reverse foreshadowing some difficulties in the epilogue).
The journey from Absalom Station to Thosum V takes place aboard an AbadarCorp freighter. There's a brief mention of a character who is apparently important for a future scenario, but very little detail is provided. I tend to think these little bits turn out to be more frustrating for the players than exciting little easter eggs for discovery, and that it might be better to just start more scenarios at the mission site (with a briefing given remotely) than requiring a hand-waved trip every time. Another bit that's a little off in this scenario is that the scenario tells the GM the journey takes 3d6 days of travel through the Drift (the standard for a journey from the Pact Worlds to Near Space), but the ship also just so conveniently arrives (no matter what the dice roll is) during the five days of Goldfest, a big celebration on Thosum V. It would be better for scenarios to dispense with the "3d6 days" fiction and just tell the GM how long the voyage takes if it's plot-relevant (which it hardly ever is).
Anyway, there's a good little scene when the PCs arrive as the local miners think the Starfinders are going to shut down the dig and hurt the economy. This could have been fleshed out more, and would have given some additional opportunities for role-playing in a scenario that has very little. We also don't get to see much economic angst in Starfinder scenarios despite some of the setting themes of hyper-corporatization and limited social welfare programs. Anyway, the PCs do get to have a conversation with the AbadarCorp leader, Taxmaster Alazdra, but that's really not much more than another briefing.
The first encounter is original and fun. As the PCs are taking the lift down the miles-deep shaft to get to the complex, they're attacked by burrowing pests. After just a couple of rounds of battle, the fragile shaft will start to collapse, raining down rocks and threatening to crush the PCs unless they get out of there fast. It leads to a classic situation where the PCs are trapped underground with no obvious way out, which helps add to the tension of their exploration of the complex.
So, the complex: one thing in the scenario's favour is that, although this might at first glance seem like a traditional (space-) dungeon crawl, it's really more like an 80s slasher pic. There's an incredibly deadly, implacable adversary that seems invincible, and the only thing to do is run, hide, and hope to stumble upon a way to escape. Instead of a Jason or a Michael Myers, the slasher's role in Waking the Past is played by the aforementioned nanotech golem. This thing is CR10, has a +27 on attacks (doing 4d6+20 points of damage), is immune to almost all magic, and has regeneration 10 to bolster its 250 hit points. In short, its effectively unbeatable for PCs of either tier here. The concept of the scenario is that the PCs should quickly realise they have no hope of defeating the golem and should instead keep moving, exploring the complex as they go, desperately hoping for a way out. I think it actually works out pretty well, though I imagine many groups learn the hard (TPK-oriented) way that not every enemy is designed to be defeated. In addition, it's really important that the GM carefully read the monster's abilities, tactics, and the two sidebars about when it appears and how it operates. There's a lot of information to process here, and I wouldn't recommend this scenario for a novice Starfinder GM. I guess if nothing else, it does help that it's *really* hard for a PC to actually die in Starfinder due to the generous resolve point mechanic.
Apart from the nanotech golem, the complex contains a few clues (on cliched "one entry only" datapads) about the scenario's background, though the PCs won't learn much about the Twilight Throne or the fact that this golem wiped out all life on the planet. There's also a trap or two, the usual security robots, and some undead to fight, though the PCs need to be careful not find themselves stuck in an encounter when the nanotech golem catches up to them. The main goal is escape, and to do that the Starfinders need to push open the stuck "back door" of the complex which then leads to a long tunnel and the surface. I'm don't understand why the golem won't keep following them up there (given what it did in the past), and arguably the more "heroic" thing for the Starfinders to do would be to trap themselves in the vault with the monster to save thousands of lives on the surface. But, that's a digression, I guess.
The scenario has a potentially interesting epilogue, where Taxmaster Alazdra leans on the PCs to keep their discovery secret lest it interfere with profitable mining activities that employ hundreds on the planet, despite the incredible danger. The PCs can decide whether to reveal what they learned to the world or not, with some consequences for boons. I always like good moral quandaries to bring out role-playing.
As a quick side-note, I will say I really don't like the new art style for Season 2 scenarios.
Overall, I had fun playing Waking the Past, but I imagine it could be a quite divisive scenario. By the time the players figure out what they're supposed to "do" (run!), it may be too late. In addition, some of the scenario's flavourful backstory won't really come across to the PCs. On the other hand, I like to see different gameplay concepts, and experimenting with something different than dungeon crawling is a plus in my book.
I just played this scenario, and it was a lot of fun. Now, the GM running this *did* tell us ahead of time that it should probably have a "Survival Horror" tag. As such, all of the players went into this game knowing what sort of game we were getting into, and as such didn't approach this as a standard "murderohobos murder everything bad thing they see" sort of scenario. We were on edge trying to figure out how to get through and survive everything, while also trying to dig up some of the sort of stuff that Starfinders exploring would want to dig up.
It was nice as a change of pace. Of course, there have been a number of changes of pace in Starfinder, and in the last handful of seasons of PFS 1, so it's not alone.
First review got deleted by system, so this one will be a bit more brief.
I really like this scenario. The primary threat felt like it did a good job of communicating lethality, both through mechanics and description (GM matters here of course.) The other encounters were interesting, possibly one two many but otherwise fine. Only thing I find problematic is the loot component, which seems oddly tied to being picky about treasure while you're supposed to be prioritizing survival. Piecing a mystery together under duress, fun. Not getting credits because you played the way the scenario suggested, less fun. Also there is a stat check near the end that can be a problem for some parties, but creative interpretation (GM and Players) of an otherwise random item can get around that.
This has to be one of my favorites. Even knowing I have no plans to run it a second time! I ran this online.
This scenario does nothing to show just how dangerous the creature is, which will easily lead to players getting killed in like 2 hits. Also, all these little things scattered around that make the players think "hey maybe if I do this!", only for it to not work. Like the gas/nanite gun/ and useful weapons being around that are no use because hey guess what you're not hitting anyways. So it's so easy for this to go very badly, simply because players will see an enemy and, like all other scenarios, move to attack it.
I took the advice here and very plainly told my players ahead of time about how dangerous this scenario was, about how they need to think "survival horror", and even made sure to point out "hey you could hide. Hey, you wanna like to listen through the door or try to sneak a peek?" Describing them hearing the opening and closing of doors. Just doing whatever to make sure they were fully aware of what they were getting into, and doing my best to portray just how dangerous the creature is.
Because you have to. This scenario is such a cool idea, and I would love to see something similar to this in the future. Having such mean encounters (hey enjoy 2d6 damage no save) was so refreshing compared to a lot of other scenarios. I think it was maybe a little overkill with how strong the creature is.
I just wish SO MUCH that this scenario did something to portray how powerful this creature is. Or if those ideas the players are for sure going to think of (gas, gun) would actually work to slow it down. I want to reward them for clever thinking.
If you're GMing this, you have to go out of your way to tell your players how dangerous this scenario is, at least so they can get there heads in the right mindset of "SURVIVE" and not just "find the monster, kill the monster, loot place".
I really love this scenario, and it's easily one of my favorites. I hope we get something "similar" in the future, but with a bit better execution. This scenario is very easily doable, as long as you do what Starfinder so rarely do.
I feel that this adventure was basically perfect and so adventurous in terms of tone!
But having run it several times, nothing short of straight up INFORMING the players that this is a horror adventure out of character tends to get things through to the player that this is not your standard adventure.
And after mulling it over, I say go ahead and warn them. This Starfinder monster movie stuff is super fun if everyones on board, so get them on board!
Hmm, was curious about the low reviews and I have a question
about the one thing both of them complain:
Isn't it GM's job to make it clear when a monster is too powerful for the group? Like either just stating it directly or otherwise describing to them they realize its too strong for them in character? Unless creature looks really harmless I guess. Though I agree that it'd probably be better if scenario itself made it obvious how deadly the creature is, I think too many GMs in general have mentality of "If text doesn't say this aloud then PCs can't be allowed figure it out"
Arvin says, that he served in his "first few years in society" on Alazdra last mission.
Alazdra says that it was 30 years ago.
Lashunta mature at 20 years.
So, considering joining Society at 20 years and "first few years" be at leas 2 years - Arvin was at least 22 during Alazdra last mission and now Arvin is no less than 52 years (look at his picture)! Is that so - or there is some mistake?
Pathfinder Adventure, Adventure Path, Maps Subscriber; Starfinder Charter Superscriber
I gotta agree this Scenario was a little gem, perfect for Halloween. I warned them at the start "This won't be like any other scenario we've done before. But I won't fudge dice or hold your hands. If you want to die I will assist in that mission"
I feel I ran it perfectly as it was written to be. Half the party may have died but everyone had a great time.
