Do you prefer to have the stats in the body of the adventure, written right after  the mention of the NPC or monster, or collected together at the end?

I'm currently writing up my second Savage Worlds con scenario and I'm leaning towards the latter.  I like the idea of boldfacing anything that gets stats and then having those stats collected at the end, in a sheet the GM can tear out and cut up to have on hand during the adventure.

Also, it allows for the adventure to be easily ported to another system.  Someone can just take the stats page and convert it into their system of choice.

But I'm curious about what other people prefer.

Thanks!

In the body of the adventure unless your suggestion of a handout/tearout with all the relevent stuff on, is included.

Do you mean to say that the suggestion itself should be included (i.e. actually stating somewhere in the intro that the reader should go to the end for all the stats)?

Quote from: walkerp;240765Do you mean to say that the suggestion itself should be included (i.e. actually stating somewhere in the intro that the reader should go to the end for all the stats)?

Sorry, no. If all the stats are in the back, then i want that info to be detachable from the module - tear away or whatever. If it's just stats at the back of the module that i have to copy out or keep refering to during the module, i'm not interested. I would then want the statblocks to be in the text of the adventure where they are going to crop up.

Got it.  

I guess there are two modes, one when the GM is actually reading the thing and the other when it is being run.

I would definitely do it so that the stats are on entirely separate pages, laid out in such a way that they are easily referenced and possibly cut up.

It's going to be a pdf, so the physicality of it isn't an issue.

But your point is well made.

I wonder if it would be best just to have both?  The only problem with that is that it ties the body of the scenario to the system.  Not a dealbreaker, but I like the idea of systemless stuff these days.

Well, if it's a pdf then it shouldn't be a problem. Just print off the statblock pages and have them seperate to the body of the adventure for reference.

er- both. In the text, so I don;t have to look them up at the back as I'm going through the adventure, and then as a clump at the back, so I have everything at my fingertips when the dying starts.

If it's .pdf, it shouldn't be too hard to do A, B and C - At least, as long as you use a decent archive format.

7z seems to work well and is free.

Granted, that has other downsides, but even zip should work well enough.

It must be in the body of the adventure, in the relevant place.

Some modules cheat and contain bare-nones info in the body of the text, and contain full details in the Appendix (Freeport - Im looking at you!).

Quote from: Lawbag;240984It must be in the body of the adventure, in the relevant place.

Some modules cheat and contain bare-nones info in the body of the text, and contain full details in the Appendix (Freeport - Im looking at you!).

Why?

Not challenging you, just trying to figure out your perspective.  Because when I read a module, my eyes gloss over if the NPC description and stats are all there in the body.  I just want to know really quickly their role, behaviour and relative power level when I'm reading the module.  It's when I'm preparing to actually run it that I take the time to absorb their details and stats and then it's annoying if I have to keep flipping back and forth.

Also, I like the idea of decoupling the stats from the body of the adventure.  That way anybody can just create a separate conversion sheet and players of that system won't feel like they are wasting their time with all the stats in the main body of the piece.

For instance, there were quite a few D20 supplements that looked interesting to me, but I just couldn't get past the clutter of stats in them.

But that's me, so I'm curious as to why not having the full info in the body is a turn-off to you.

Thanks for your answers everyone.