Every once in a while, but with some regularity, someone will ask for module recommendations, often as a way to get into old school or classic play. I am somewhat conflicted regarding the best response to such requests because, while there is nothing fundamentally wrong with modules, and they have some particular utility, modules are also limiting, often have poor handling, and are poor examples of the form’s potential.
My inclination is to instead suggest that referees, even new referees, create a simple custom scenario. This is unnecessarily intimidating, partly due to some unfortunate ingrained assumptions, including seemingly upward comparison to professional offerings with illustrations, cartography, edited prose, and so forth. In reality, crafting a satisfying classic scenario is often less complicated than the process of building a player character in a contemporary system, but has become obscured by a shroud of world building complexity and the detritus of expectations related to literary story structure. There are a few examples of procedures that a referee can follow to create a scenario, such as Moldvay’s double spread in 1981 Basic D&D (pp. B51-B54) which explains how to create an adventure. The recent Old School Essentials SRD provides similar information, available for free online (adventure scenarios, designing a dungeon, designing a wilderness). Other resources exist as well, though often buried in other materials.
These resource are useful, but still often seem to be pitched at the wrong level, lacking sufficiently concrete set of recommended actions, or attached to bland thematic content. As an example of the kind of referee rules that I think would be an antidote to module recommendations, I want to highlight two recent blog posts about crafting megadungeons:
The Two Week post in particular is a practical and clear example, though perhaps still slightly intimidating for a starting referee. Unfortunately, the trappings of a megadungeon is probably mildly counterproductive, despite the likely truth that following Nick’s megadungeon building guidelines would probably be easier and more enjoyable than skimming B2, or just about any published module scenario. (In reality, the observant and experienced reader will also note that a megadungeon is really just a series of linked scenarios that happen to be subterranean.)
If you are aware of any other similar scenario building procedures worth highlighting, drop them in the comments. Procedural rules rather than something like a collection of tables would be most useful. I am sure I am neglecting some other good resources. This is also a call for what to include in a game’s referee book or section.