In #2-14 when the moorlocks attack with the nightmare vapor, I'm unsure of exactly how to handle the save DCs with multiple doses.
Do the PCs make six saves as the six vials crash to the ground, exposing them six times (in high tier)? Would those saves be at DCs 20, 22, 24, 26, 28, and 30? Or would they all be at 20, +2 for each FAILED save?
Or would they just make a single save at DC 30?
If they stay in the cloud of poison, they'd have to make DC 30 saves to not be effected, assuming they're not already affected from the initial attack, right?
If the vials aren't shattered exactly simultaneously, then it works as follows.
Step 1: Each Player rolls 1 DC 20 save. If he passes, repeat this step for the second and subsequent saves, returning to this step after each successful save. On the first FAILED save, deal onset damage and proceed to step 2. If all 6 saves are passed, this sequence terminates.
Step 2: Having taken the onset damage, the player turns to the remaining doses and begins making saves against them. The save is now DC 22, as he has one dose of poison in his system. If his saves pass, he continues making DC 22 saves against remaining doses until he has passed all remaining saves, returning to this step after each passed save. On the second (and subsequent) FAILED save, proceed to step 3.
Step 3: Deal onset damage. Then, for every failed save after the first, increase the DC of all remaining saves against the poison by +2 and increase the duration by 50%. Return to step 2 after increasing DC and duration.
If the vials are shattered exactly simultaneously, then it's as follows:
Step 1: Each Player rolls 1 DC 30 save. If he fails, he takes the initial onset damage and is poisoned for (normal duration +50% x5). The saves during this duration are all DC 30. If he passes, he is not poisoned. End of sequence.
For the poison cloud afterwards, it's debatable if it counts as a concentrated dose of the poison. If you think it does, that's a DC 30 save each round to avoid either a) onset damage and being poisoned, or b) onset damage, +2 DC and +50% duration if already poisoned. If you think it doesn't count as a concentrated dose, it's as above, but only DC 20.
Poisoned characters then have to save during each of their turns to avoid ongoing poison damage, at the DC set by how many doses they have in their system, and for a duration based on the number of doses.
The initial save can be describes as 'Does this dose of poison enter my system?' If the answer is YES, then check 'Am I already suffering from one or more doses of this poison?' If the answer is NO, deal onset damage and the character is poisoned. If the answer is YES, deal onset damage, +2 DC to the existing poison, +50% duration to the existing poison.
Paizo Blog on poisons may also help.
Hullo. This scenario seems interesting and has plenty of variety so I'll be running it on Wednesday. However, the write up includes some rather confusing if not outright problematic parts, so I need some help.
Let me just list my questions/problem areas here:
1. In the initial encounter inside the Phitoness' hovel, the PC's face the possibility of being buried alive. Should this happen, how long does it take for the party to dig their allies out? The only reference to being buried that I could find was in the cave-in hazard:
In 1 minute, using only her hands, a character can clear rocks and debris equal to five times her heavy load limit. The amount of loose stone that fills a 5-foot-by-5-foot area weighs 1 ton (2,000 pounds). Armed with an appropriate tool, such as a pick, crowbar, or shovel, a digger can clear loose stone twice as quickly as by hand.
The PC's won't get buried by a tonnage of stone so how long should the digging take?
2. C1 tells us that Each minute of travel, the PCs must succeed on a DC 20 Acrobatics check to avoid slips and slides toward the bottom of the shaft. Those who fail end up prone in area C2 and suffer 2d6 points of damage from the rough landing (DC 20 Reflex for half).
However, there's no explanation on how long the descent could take. It's a 100 ft. slope downwards and not a combat encounter, so should I use the local movement (mountains, trackless, so 1/2 speed) rules? That way, assuming a walk speed of 20 feet, they could travel 200 feet/minute, which the trackless mountain terrain would halve. Anyone?
3. How about the rest of the dungeon then? The map isn't too helpful and I need to know or at least get a rough guesstimation on how long does it take to travel from C2 to C6. Reason being the environment: the main event of the scenario is an ice cavern in high altitude terrain. If the trek takes long enough, I'll be asking for Fortitude saves vs. hypotermia and altitude sickness.
4. I don't understand the combat area or the morlock warden tactics in C3. Are they trying to block the PCs escape or entry? Upon finishing a strike, they scurry back up the walls, trying to get enemies to chase them, but how? There's no ceiling height listed. Very confused. I'd appreciate examples from people who have run this.
5. Frosty lurker? Moar like equipment muncher! Am I supposed to ask for saves even if the equipped items have no listed hp's or hardness? What happens if they get damaged?
6. Cailleach's tactics state that she turns ethereal, uses her sleet storm ability, and if possible, grabs Eya and drags her about the caverns, taunting the PCs and trying to get them to split up in order to attack them individually, . Two questions: Sleet storm while ethereal, yay or nay? Grapping Eya, but going where? I assume anywhere that's tactically sound, but it could just mean a safer spot inside area C6.
Thanks in advance. Help me make the coming session cool. Severe cold cool.
So, that was that: A decent session all-in-all.
I decided that it would be a big waste to not give an update on how I solved at least some of these issues. I remember searching for earlier threads concerning them and finding quite a few people had had similar problems. That might include you, the one reading this message. So let's not waste your time, like I wasted mine looking for the answers.
I hope. I mean there aren't clear cut solutions here afterall!
1. The burial problem
Dying is not fun, most of the time, and while the hermitage is made of granite slabs, high level adventurers should stay larger than life. What I did then, was first ask for Str checks(they got a crit success), then have them dig each other out. Every minute, a PC could move enough slabs to save one ally. Escalation of manpower had them in the clear pretty soon and the trap only cost them a couple of channels.
2. The slope
Nothing to it, really. The mountain environment lists that a trackless exploration area halves the movement speed. Then it's only a matter of asking who's the slowest in the group and going by that. Mine was 20, so descending the slope took 2 minutes.
Winged it, had them roll Fortitude vs. severe cold contact just before the boss and altitude saves on the way to the chasm. The distance between the hut and the dungeon was missing, but the Campsite section mentions half-day rations etc, so winging the time wasn't difficult.
Picked a 15 feet high ceiling to preserve sanity. To hell with the tactics(and you, Crom), the area was so full of morlock(mor-locked?) that the tactics didn't survive any kind of contact anyway.
5. Overgrown coolant bubble
After an hour of grueling morlock mayhem my players decided to forego the optional encounter for, well, more morlocks, but I did decide beforehand to just ignore any damage the oozenaught might cause to such gear that didn't have any rules on durability. Just imagine what would happen when a blinged out monk grapples it...
I decided to run as written and, on grabbing Eya, treated the situation as a tactical retreat: Once the players saw their prize gone, they started looking for the hag(and the loot). After a minute had passed(10 rds worth of ethereal movement for Cailleach), they heard a shrill laugh from the stalagmite cave. There the battle resumed, with the hag invisible and in cover. Much better.
Righty then, next up: The Golemworks Incident. Plenty of threads on the boards about that, luckily