Dear Everybody,
I've been anxiously trying to puzzle this out in my head, but I'd rather admit my cluelessness than be disqualified for a flawed entry.
Do not use customized monsters or hazards that do not already have a stat block from a Paizo source if the effects of the variation cannot be summed up by adding one line to the stat block (such as a half-fiend troll, a goblin rogue 5, or an advanced spectre)--normally you would include a complete stat block for such a monster, and you won't have room to do so within the 1,500 word limit for your entry.
So hazards and traps have separate entries in the encounter format provided; does that mean that traps, haunts, and the like are not considered "hazards" as described in the rule above and we can thus create new ones for use in our encounter?
Thanks for any and all clarification.
Can't wait to see everybody's encounters!
-Mikael
Huh, I missed that bit in the rules about custom hazards. Although looking back at the last two years, there a couple of short custom hazards and haunts, and they weren't disqualified. Since that rule cites the lack of space, it leaves me wondering if you can fudge it on the customized hazards a bit, as long as you're not pushing the word count limit.
I also was a bit confused on that one, Mikael, and actually sent a note to SKR for clarification.
His response, which I'm assuming he won't mind me sharing:
"Well, the R3 rules explicitly say to NOT use such things if they don't already have a stat block from a Paizo source, unless you could sum up the change to an existing source by adding one line to it.
So I'd try to find a hazard that's close to what you want to do, then modify it with 1 line."
I think that's a bit of leftover text from the previous year's rules text, where you had to include a trap but didn't have to include a hazard; so that section is calling out that you shouldn't spend word count on a new monster or hazard.
For this year, you're not required to do a trap, so technically that wording should have been changed to "Do not use customized monsters, hazards, or traps that do not already have a stat block from a Paizo source." But the rules don't say that, so if you want to make a trap, you can make a trap.
But remember that the purpose of this round's challenge is to show that you can put together an interesting location, encounter, and map. I wouldn't devote too many words to detailing a trap, as the judges and voters want to see how you do with the rest of the challenge.
Thanks Sean.
As a follow-up question, is there a clear line (or good rule of thumb) between formal Hazards and mere interesting features of the terrain? Is it hit point or ability damage (all of the hazards in the GMG seem to inflict damage of some kind)? For example, if I write that some loose floorboards could cause the PCs to trip if they don't make a Reflex save, is that a Trap? A Hazard? Or just "a thing to watch out for"?
It looks like Paizo's modules just list that in the running text of the first paragraph of a room's description. Frex, PF#72 page 13 says:
"Detritus and filth clutter the ledge and cave floor, and those areas are considered difficult terrain for any creature smaller than Large. Due to their steepness and the slickness of the filth coating them, the cliff faces here require successful DC 25 Climb checks to ascend. The rock pinnacles are not smeared with discarded garbage and require only successful DC 15 Climb checks to scale."
And that's not called out as a hazard.
The Core Rulebook defines a hazard as "Hazards are location-based threats that have much in common with traps, but are usually intrinsic to their area rather than constructed."
So... it's a gray area. I don't think it hurts to list it as a hazard, especially if you're reusing existing mechanics.
The rules do not say you are required to include a custom haunt or trap. (The word "haunt" is not in the R3 rules at all, and "trap" is only used to show you where you'd mention a trap in your encounter, and is called out as an optional element.)