Monthly Archives: March, 2014

Adventure Design Requirements

A-Z 2014 ANormally I’d probably title this “Scenario Design Requirements”, but I’m taking another run at the A-Z Challenge so “Adventure Design Requirements” it is.

Some time ago a friend gave me a set of three “Character Design Requirements“. She was playing in a primarily ‘Supers’ game, but with only a small change the guidelines work with most roleplaying games.

All Player Characters (PCs) should…

  1. Have a way to get to the action.
  2. Have a way to be useful in the action.
  3. Have a way to stay in the action.

Just as the players have a responsibility to ensure their Player Characters can reasonably take part in an adventure, the adventure designer has a responsibility to ensure the same thing. The guidelines above can be restated for the adventure designer.

All adventures should…

  1. Have a way for PCs to get to the action.
  2. Have a way for PCs to be useful in the action.
  3. Have a way for PCs to stay in the action.

As with the character design requirements, the application of these guidelines is not required to be obvious.

(more…)

Autocorrect Inspiration

Idea!

Idea!

Sometimes scenario and setting ideas come from the weirdest places.

Today on Facebook there was a conversation about the ‘biggest cataclysm in your campaign’. One of the comments included (something like)

William: “The Dim Sun lasted for months, ruining crops. This led to widespread death, famine, and petulance. […]”

Me: “Autocorrect? I think you meant ‘pestilence’.”

William: “I did, but people were pretty unhappy about it.”

Me: “I imagine so. ‘Mo-ommm! How come I got Black Plague and Billy didn’t?’ ‘Shut up and be thankful you got anything for Christmas at all.'”

William: “… now I need to play this.”

It doesn’t take much to spark an idea sometimes.

Echelon Reference Series Preview: Barbarian Index PDF

Echelon Reference Series: Barbarian Index

Echelon Reference Series: Barbarian Index

Last night I posted a PDF of the index of a layout draft document containing classes.

Here, I have the index of a working draft of the Echelon Reference Series: Barbarian book. Same rules for indexing, but different data, including many feats and their associated diagrams.

Many feat prerequisites and diagrams still need data cleanup. The “Barbarian bloodline” entries shown on the first page of the index should (and will be once the data is cleaned) “Basilisk (barbarian bloodline)”, consistent with “Aberrant (sorcerer bloodline)”. The “base Fortitude” entries shown here should probably be removed altogether (it’s almost like indexing ‘character’). In the right-hand column, “boasting taunt” and “Boasting Taunt (rage power)” should really be merged; “boasting taunt” is an artifact of the automatically-generated diagrams that has not yet been fixed.

I really should fix the script that automatically generates the diagrams. I think making it just a bit smarter would remove a lot of the cleanup I need to do now — I can tell from the data that it’s a rage power, I should just skip ahead to that part and format it as such. Then my diagram cleanup can focus primarily on layout rather than fixing data.

“Breaker (archetype)” and “Breaker (class)” should be changed as well. “Barbarian” is the base class, “Breaker (class)” here is actually the Barbarian class with the Breaker archetype applied. I think “variant class” would be a better label than “class”, since either one can be turned into the other — an archetype can be added to a class to make a variant class, and a variant class can have the base class “subtracted” to find the differences and make an archetype.

Thankfully, applying archetypes to variant classes is outside the scope of this post… though since you can apply as many archetypes as you qualify for (have the exchanged abilities for) it’s actually not that scary to understand, just kind of funky to apply.

However, while I am prepared to demonstrate the variant classes created by applying  archetypes (seeing them as variant classes makes it much easier for me to understand exactly what impact an archetype has), I expect to take it to only one step, not try to apply all possible permutations.

Tasks remaining for Echelon Reference Series: Barbarian:

  • Refine and complete covers.
  • Fix title page. I want it to look much the same as the cover page, but simpler graphics and some more (required) text.
  • Review and finish revising feat diagrams. There are many left to be done in the full feat set, but only a relatively small subset are needed for this book.
  • Review and finish revising class feature text. This is mostly changing language from third-person passive to second-person active — “the breaker [or worse, ‘the barbarian with the breaker archetype’] is able to” becomes “you can”. As with feats, it is safe to assume that the class feature applies to someone who has it, and is reading the text. Second-person largely gets around he/she consistency problems and tends to be more engaging, active language is usually similarly more engaging and most often shorter and easier to understand. This is mostly done for the barbarian class features, not so much for class features from other classes, so I’ll focus on the class features that apply to barbarians so I can get this out.
  • Class feature diagrams. I haven’t even started these, but considering how they interact they are probably a good idea. Many rage powers have other rage powers as prerequisites, and many feats have class features and class subfeatures (Rage Power is a feature, the Aligned Fury rage power is a subfeature of Rage Power) as prerequisites. Just as with feats, diagrams for the class features and class subfeatures will make the relationships easier to understand and thus the material easier to use.

As with yesterday’s post, click the image in this post to see the PDF, or click Echelon Reference Series: Barbarian Draft Index.

Echelon Reference Series Preview: Classes Index PDF

Echelon Reference Series: Classes Index

Echelon Reference Series: Classes Index

I’ve been kind of busy lately, so many projects in the works.

Here’s a sample from one that’s been going on for about a year now, the Echelon Reference Series. I’ve been working on setting up indexing options, to see what additional information I might need to help make this more workable. (I also found I need to rework how I set the index up — the way I was doing it allowed for only one index entry when I define the object, and that Clearly Won’t Do.)

When I actually make the Echelon Reference Series available I’ll be splitting it up by topic. This is mostly to make them digestible, both to people using them and to me in assembling them. There’s a lot of work involved, so keeping each to a single topic limits how much data cleanup has to be done Right Now.

Also, even the individual books are kind of big. The draft Barbarian book is a 184-page PDF.

I wanted to see what the indexing looked like, though, especially when there was more data available. I took all the core classes and all the class features I’ve captured — I couldn’t be bothered to remove the ones for archetypes or classes not present in the book — and jammed them into a single source file. A quick (read: five minutes, on solid-state drives) build and I had myself a 400-page PDF.

Since I was mostly interested in the index, and thought I’d share it, I stripped out the actual content to make the index available for examination. The image on this article is a screenshot of the first page of the index, click to get the PDF.

Or click Echelon Reference Series: Classes Draft Index.

Let me know what you think.