Modules: Made to Read vs Made to Run?

[BruceWright]

That reads as rather unkind, if you're unaware, and makes assumptions that your feelings in this area are objectively superior to others.

Then let me retract that phrasing and replace it with the objective statement that many companies including Wizards will pay writers based on word count, and leave others to draw their own conclusions on how that impacts the final product.

 

[Umbran]

I have to agree with @zakael19 here. I don't think the tradeoff you see is intrinsic or necessary. Modules can be both easy to run AND have that kind of complexity.

What's the example that proves your assertion correct?

To me it's the difference between long paragraphs explaining a faction's backstory, versus a standard template that lists a faction's key characteristics, it's relationships with other factions, and its goals.

1) Yes, but we are looking for both readability (for which prose paragraphs are best) and playability (standard templates being useful here) - you look to be prioritizing the latter, which isn't meeting the brief.

2) We are talking about many individual NPCs, with detailed (inter)personal histories, relationships, and motivations, not generalized factions with sketchily defined members.

3) You then have a choice - pull out all the faction information in one place, separate from the map and key (requiring frequent page flipping for reference, not good for reading), put all the faction information in every individual keyed area they appear (playable, but redundantly wasteful of print space, also not really readable), or put partial information in the keyed areas as you expect it will be needed (readable, but making reference difficult if you need the information at some other point), or some admixture (a readable and playable version of which is not certain to exist).

Information design for multiple intended uses at the same time isn't easy. Compromises and creativity are likely required. There's a reason why information design these days is a job-marketable skill, rather than a solved problem.

 

[Bill Zebub]

What's the example that proves your assertion correct?

Ha. Good one.

You're a smart enough guy to know both that I can't prove you wrong (as it were...) and that my failure to do so would not prove you right.

I can't, of course, provide such an example, because there isn't (as far as I am aware) an example of a module being done well in two different versions, one of each style. Any module that I were to propose in the terse, information-dense, easy-to-parse form in the style I prefer could easily be dismissed as "Yeah, but not as good as it would have been in long form." And even if I went through the trouble of taking, oh, let's say Marmoreal Tomb (god save me) and rewriting it in such a style, a naysayer could easily say, "You left out the word verdant. Now we might as well be playing a board game."

The argument can't be won by evidence. EDIT: At least, not in a way that would convince an already decided partisan. EDIT2: That wasn't a dig. I'm an "already decided partisan."

1) Yes, but we are looking for both readability (for which prose paragraphs are best) and playability (standard templates being useful here) - you look to be prioritizing the latter, which isn't meeting the brief.

Curious how you are defining "readability". I find standard templates and sentence fragments as bullet points to be very, very readable. More readable that walls of prose.

On the other hand, if you mean, "Curl up with a glass of boubon and a faerie dragon on my shoulder and enjoy a good book", then, yeah, sure. But contrary to your "we" that is absolutely not what I am looking for.

2) We are talking about many individual NPCs, with detailed (inter)personal histories, relationships, and motivations, not generalized factions with sketchily defined members.

Great. Then summarize each NPC with their personality quirks, goals, etc. Does not have to be in long-form prose.

I mean, sure there will invariably be some information loss (see "verdant" above). The question is whether that lost information would actually improve gameplay, as opposed to just being enjoyable to some readers.

3) You then have a choice - pull out all the faction information in one place, separate from the map and key (requiring frequent page flipping for reference, not good for reading), put all the faction information in every individual keyed area they appear (playable, but redundantly wasteful of print space, also not really readable), or put partial information in the keyed areas as you expect it will be needed (readable, but making reference difficult if you need the information at some other point), or some admixture (a readable and playable version of which is not certain to exist).

Information design for multiple intended uses at the same time isn't easy. Compromises and creativity are likely required. There's a reason why information design these days is a job-marketable skill, rather than a solved problem.

I 100% agree with the above. But true regardless of whether the faction is described in long form prose or a powerpoint presentation, no? Which suggests I am either missing something in what you are saying, or that you weren't understanding my position to begin with.

 

[Reynard]

What's the example that proves your assertion correct?



1) Yes, but we are looking for both readability (for which prose paragraphs are best) and playability (standard templates being useful here) - you look to be prioritizing the latter, which isn't meeting the brief.

2) We are talking about many individual NPCs, with detailed (inter)personal histories, relationships, and motivations, not generalized factions with sketchily defined members.

3) You then have a choice - pull out all the faction information in one place, separate from the map and key (requiring frequent page flipping for reference, not good for reading), put all the faction information in every individual keyed area they appear (playable, but redundantly wasteful of print space, also not really readable), or put partial information in the keyed areas as you expect it will be needed (readable, but making reference difficult if you need the information at some other point), or some admixture (a readable and playable version of which is not certain to exist).

Information design for multiple intended uses at the same time isn't easy. Compromises and creativity are likely required. There's a reason why information design these days is a job-marketable skill, rather than a solved problem.

You seem to be making the case that information can only be presented one way, which is obviously false. If a module (for example) has two (or more) uses, then it is reasonable and best to present that information in both ways. Most modern modules, especially those by WotC and Paizo, fail to do that, or do it so badly that they might as well not have tried (Avernus).