|
| 16 people marked this as a favorite. |
After GMing PFS at conventions for 2 years and 50 tables I have built up a long mental list of things I do to prep a scenario for convention play. This list has remained relatively stable throughout this year so I decided to write the list down for 2 purposes:
- to see if I could optimise and streamline it for faster and easier prep
- to create a formal checklist
I am posting it here in the hope that it is useful to others and that there are suggestions for improvements in the process or tools to use.
- Print out scenario text pages, and put in a lightweight binder.
- Use a highlighter or colored underline to highlight all skill checks in scenario text
- Use another color to highlight all faction mission notes in scenario text
- Use another color to highlight all notable scenario text, plus reference information such as terrain, ceiling height, light level.
- Using Combat Manager/PRD/PFSRD - Save and print out all stat blocks that are not fully listed in scenario
- Lookup all monster special abilities and traits. Make notes and print out large text blocks.
- Highlight all key features of creatures and make notes for things you may miss. For example note power attack bonuses next to attacks, and flag other combat maneuvers such as step up or lunge. Note defensive abilities and items prominently next to defensive stats, such as DR, SR, ring of Force Shield, Ring of Counterspells.
- Review tactics and work out what you will do and what you need to know for round one.
- Note any items they have that affects combat.
- Using PRD/PFSRD/combat manager: lookup all feats you aren't sure of.
- Using PRD/PFSRD/combat manager: lookup all abilities/spells you aren't sure of and make notes. Noting in short: range, radius, effect, non-standard casting time
- Note any build errors you find and work out what you will do about them. For example an NPC has a feat he doesn't qualify for or the tactics mention a spell that can’t be used. (Assume if you don’t find any build errors that you missed them. It is nigh impossible to create multiple NPC characters without making mistakes, especially higher level ones.)
- Note any environment conditions that affect the encounter: obstacles, terrain, lighting, ceiling height, etc.
- Once you have reviewed the above and know the constraints you are working under then work out what leeway you have to make the encounter more intelligent, fun, harder, softer.
- If any elements are new to you or it looks too weak or too deadly then do a dummy run of round one of combat to look for issues or options.
- Think about any PC abilities or PC types that might sideline an encounter, e.g. Sleep Hex.
- Read entire scenario to identify story elements, any potential holes, any stall points or any story thread weaving required. Note any elements that need to be brought out or hinted at.
- Identify every NPC and give them a basic personality, typically by aligning them to someone you know either from real life or fiction. Though it may be bad form to base it on someone actually sitting at the table ;-)
- Read every faction mission and work out where and how to surface it in the scenario and any potential issues with it.
- Try and spot any assumptions that might break the story if they don’t come true and how to work around them. For example does any outcome depend on encounters being resolved the traditional way rather than via enchantment spells or social skills.
- Print 3 copies of faction missions and any handouts, cut out and file
- Print out 6 chronicle sheets per session planned plus one for GM credit.
- Print out reporting/tracking sheet if required.
- Print and fill out initiative cards for all creatures (location, subtier, number, name, init, AC, HP)
- Print blank initiative cards for PCs (fields: name, level, classes, HP, AC, Perception, specials)
- Create event/scenario on Paizo or get event number from coordinator
- Create and print out sign-up sheet where required for that particular convention
- Pre-fill chronicle sheets with event name, event ID and GM ID to save table time
- Print out images from the scenario for scene setting (using print screen and Paint.Net).
- Complete any enemy spellbook spell lists and print off as handouts
- If it is to be run in a short slot, prepare a handout of mission goals and key NPC names.
- Print or pre-draw any complex maps or key parts of maps
- Identify any flip mats or alternative maps you can use (and any you want to buy)
- Identify the minis required and find them. Find proxies or print paper tokens for any you don’t have.
- Read the wiki for all locations and people listed in the module
- Print any scene setting images from the wiki
- Identify any scenery or props you could use to add some depth and fun. Particularly where it is necessary to identify who is carrying a particular item. For example an important key, scroll, wayfinder or other scenario maguffin.
- Read and contribute to the GM thread any errors, concerns, questions, or notable table points that came up.
- Write a review of the scenario. Do this before you run it as it forces you to think through the scenarios strengths and weaknesses. Then update after you run it. This is the primary way you can influence authors to write the kind of scenarios you want to run or play. Be constructive and use spoiler tags.
|
Looks like a pretty thorough list. I also print out the stat blocks and highlight them, etc to prep for usage, but I dont just do the stat blocks. Similar to your looking up feats, spells, etc, I create a whole document for each scenario I am running, containing all the stats I need printed, feats, spells, abilities, items, and obscure rules the scenario may contain that either I dont know off the top of my head, or I think a player might question me on.
For example, here is everything in my notes for To Scale the Dragon, which I prepped for last weekend.
Cold Weather stuff
Hypothermia from water
high altitude rules
Avalanche rules (I forgot the rules for being buried alive)
Mummy Rot
Blindness/Deafness
Calm Animal
Charm Animal
Command
Dispal Magic
Hold Person
Spiritual Weapon
Belt of Mighty Con (The Amulet of Health)
Gem of Brightness
Ioun Stones
Bull Rush
Remorhaz (plus another copy of the stats with the Advanced template)
Improved bullrush feat
Awesome blow feat
Broken condition info
Weapon/armor hardness/hp chart
Dog sled rules were on separate handouts
|
| 1 person marked this as a favorite. |
ZomB, I don't know how you handle information when PCs make monster knowledge checks, but if you're played In Wrath's Shadow you may appreciate this.
You alluded to this, but on occasion I try to have pictures printed for any unusual monsters appearing in the scenario.
Something else I do is cut out any Knowledge checks by type/DC and make them into handouts for players. I think players should get to share the fruits of their skill with the table rather than the GM.
|
|
Looks like a pretty thorough list. I also print out the stat blocks and highlight them, etc to prep for usage, but I dont just do the stat blocks.
I used to do that. I _think_ I have got to the stage where I can be as thorough without the time consuming cutting and reformatting of text.
For example, here is everything in my notes for To Scale the Dragon, which I prepped for last weekend.
** spoiler omitted **
Good point.I missed "lookup scenario relevant rules" off my checklist.
|
|
Very nice ZomB, that's GM 201 material.
Thanks. Though now you have got me wondering. What does GM 301 look like?
The great thing is once you achieve that level of prep, you are set to GM the same scenario 5, 10, 15 times with minimal effort. You just have to have a good filing system :)
Indeed. I would expect to run every scenario I prep at least twice, and as I pretty much only GM at cons that is usually not a problem - except perhaps for PaizoCon(UK) scenarios.
|
|
ZomB, I don't know how you handle information when PCs make monster knowledge checks, but if you're played In Wrath's Shadow you may appreciate this.
Noted in case I need any of those.
You alluded to this, but on occasion I try to have pictures printed for any unusual monsters appearing in the scenario.
That's worth adding to the list.
Something else I do is cut out any Knowledge checks by type/DC and make them into handouts for players. I think players should get to share the fruits of their skill with the table rather than the GM.
I experimented with this and found they weren't used that much, so decided it was a "nice to have" rather than core prep.
I will add an "extra mile" section to the list.
|
|
Yup. I started being so thorough after a couple of unpleasant overrun issues. Being this prepped makes it more relaxed when running back to back at cons.
There is one day con that has two 3.5 hour slots and with this prep and limiting it to 5 players means I can run both slots without too much stress.
|
My prep includes a summary page for each encounter with relevant skill checks and NPC stat blocks, with notes for tier and (for season 4) number of player adjustments. If the encounter includes a caster, I make a spell summary sheet with all ranges and variable effects calculated, so I can just glance at it and not have to do the math in the middle of the fight.
I also print out any handouts (including faction missions) on card stock so they last longer.
If the scenario has a non-flip mat map that is large or detailed enough to be difficult to hand draw, I copy out the image (thankfully the pdf's are layered such that the traps and room numbers are left behind when I select the map itself), scale it up so that the squares are 1", and then chop so that I can print it out, also on cardstock. For dungeons, I crop the rooms and halls so that I can lay down pieces by sightline in the most likely path through the place. (This also lets me pick up the parts they have left behind, reducing the table clutter.)