Why Adventures Became Sourcebooks
By Nelson McKeeby
The Adventure Was Never the Whole Product
Negentropy adventures evolved into sourcebooks because the game itself demanded more information than could be contained within a single adventure outline. From the outset, a scenario transcended mere sequences of encounters. When players entered a town, I needed to know the inhabitants, their dietary habits, trade practices, the existing authority structures, the functionality of machines, the languages spoken, and the potential knowledge gained through inquiries. Similarly, when players traversed a region, I required weather conditions, road networks, potential hazards, settlements, native animals, and the individuals knowledgeable about the country. Furthermore, when an adventure introduced a BEM (Beast of Extraordinary Magnitude), the creature’s attack value alone wasn’t sufficient; examining it could hold equal importance as combat.
This natural progression stemmed from my writing style for Negentropy. While the rules were concise, the majority of the project consisted of articles, manuals, notes, maps, equipment descriptions, characters, and locations. The game ladder addressed uncertainty, but the world provided the substance. Consequently, an adventure needed to encompass sufficient substance to enable the Game Master to respond to questions when players ventured into areas I hadn’t anticipated or focused on as background.
Campaign 80 Exposed the Problem
Campaign 80 highlighted the issue almost immediately. During the first session, we didn’t proceed from one pre-planned encounter to another as I had initially intended. Instead, one player emerged from a Cylinder, freed the rest of the team, and the group embarked on an exploration of the radio spectrum. I had five potential adventure directions in mind, but the players’ decision to conduct a more thorough radio search allowed me to introduce the Alpha India signal.
That meant the material surrounding the adventure had to be playable before I knew which part of it the players would select. Alpha India, Free Trader, Sacred Places, Chuhopi Carbine, and Rangers all existed as potential developments. Four of those lines were not wasted when the players chose Alpha India. They remained part of the world and eventually appeared elsewhere in the first campaign cycle. Preparation had transformed into worldbuilding that could endure even when it wasn’t used in the session I initially envisioned it for.
The Manuals Encouraged Subject-Based Separation
The first Negentropy manuals reinforced this approach. The Standard Manual contained the Five Rules and basic procedures. Character Forge dealt with characters and Areas of Knowledge. Nomiconus held BEMs and PEMs. Dwimmer contained magic. Logi contained equipment. A miscellaneous binder caught material that hadn’t yet found a permanent home, and Kindred became the first additional manual created because Campaign 80 produced a subject large enough to warrant one.
That organization taught me to separate information based on its explanation rather than forcing everything into a single adventure manuscript. If an adventure introduced a new weapon, it belonged to Logi as much as it belonged to the scene where the players found it. If an adventure introduced a creature, that creature belonged in Nomiconus. If a new people entered the setting, their culture couldn’t remain confined to a few lines of encounter text forever. The adventure generated the need, while the manuals provided a place for the information to continue existing after the adventure concluded.
A Place Needed to Work After the Players Left
The same principle applied to settlements. A town built solely to deliver a quest becomes useless once the quest is complete. I wanted towns to remain places. The people who lived there needed ordinary work, relationships, institutions, problems, and reasons to care about things beyond the Troubleshooters.
Damhold became an early example of how player decisions could turn background setting material into a functioning community. While searching for Alpha India, the players chose to help maintain the town dam. That decision required me to work out who possessed the technical knowledge to keep it operating, where replacement materials could come from, and how the settlement depended on the power it produced. The dam consequently became connected to the town’s economy and government because failure would affect everyday life throughout the community. Damhold could then support later stories because its problems continued to exist after the original search for Alpha India had ended.
The modern Alpha India book retains that approach. Damhold now operates as a community whose authority, economy, security, and relationships with outsiders grow from the conditions established around Redrock Dam. People encountered during the original adventure remain useful because they have responsibilities within that community rather than functions limited to one plot. A later visit can therefore begin with whatever has changed in Damhold since the characters were last there, allowing the settlement itself to generate the next problem without rebuilding it for another adventure.
Information Became Reusable Game Material
This realization marked a shift in my perspective, where I ceased to view background information as separate from game material. For instance, a description of Gothic agriculture could reveal the available food, the labor required, the value of a harvest, and the reasons behind a village’s strong reaction to damaged fields. Similarly, a description of a trade route could determine the goods that appeared in a market and the news carried by travelers. An article on local religion could explain the reasons behind disagreements between two communities regarding land or burial practices.
This information could serve various purposes in gameplay. A farmer’s practice might become an investigation clue, a supply problem, a political issue, or simply a detail that enhances the believability of a conversation. A road description could serve as navigation, logistics, weather exposure, trade, or even an ambush site. Once I had researched and written the material, there was no reason to limit its use to the initial adventure that first required it.
Sourcebook writing became economical in a way unrelated to shortening the books. The research could be reused, and a well-written article expanded the Game Master’s ability to handle situations without introducing new rules.
The City State Model Reemerged
My early interest in Judges Guild’s City State of the Invincible Overlord also influenced the adventures in this direction. What impressed me wasn’t a single plot but the accumulation of streets, businesses, inhabitants, institutions, and brief descriptions that a Game Master could draw upon when players encountered unexpected situations. This material didn’t dictate the story; it merely made it possible.
Negentropy required a similar quality on a larger scale. A settlement, region, faction, or trade system became easier to manage when I had sufficient knowledge to answer subsequent questions. The answer didn’t have to be a page of scripted dialogue. A few well-developed facts about a person’s desires, an institution’s functioning, available goods, or local geography could suffice to keep the game moving.
This is one reason why the sourcebook function and the Acts-and-Scenes function complement each other so effectively. Acts and Scenes provide the adventure’s structure, while the sourcebook material supplies the world surrounding that structure. When players step outside a prepared scene, the sourcebook ensures that the setting remains vivid and engaging.
Adventures Introduced More Than Plots
As the project expanded, adventures became one of the main ways new parts of the setting entered play. I found that information became much more useful when the players first encountered it as part of a problem they were trying to solve. The adventure established why a place, institution, technology, or people deserved attention, while the sourcebook material explained enough of its workings for the Game Master to use it again after the immediate problem had ended.
This was especially important when introducing a new culture. Meeting that culture during an actual dispute forced me to explain why the people involved behaved as they did and what assumptions guided their decisions. The resulting material described a functioning society because the players needed to understand its behavior well enough to decide how they would respond.
The same method worked with technology and unfamiliar organisms because each entered the game through use rather than description alone. A vehicle first became important because someone needed it to accomplish a particular journey, which immediately established the conditions under which it was useful and the limits that could create trouble. A newly encountered organism likewise became more than a catalog entry when the players had to observe its behavior under pressure and decide what they could learn from the encounter.
Consequently, the adventure became a catalyst for expanding the setting. The story provided a reason to research a subject, and the resulting source material remained valuable even after the story concluded.
Why Modern Adventure Books Explicitly State It
Modern adventure books now explicitly state the principle: each adventure in the series serves as a sourcebook for the Negentropy universe. A module can add lands, settlements, languages, customs, factions, hazards, maps, equipment, vehicles, creatures, medical issues, engineering challenges, trade goods, mission procedures, or optional rules. These additions remain part of the game world even when the adventure isn’t being played as intended.
I didn’t initially formulate that publishing sentence when I started Campaign 80. The principle evolved from practical use. The binders kept whatever an adventure taught us. Later campaigns reused people and places. Old adventure lines became later campaigns. Players returned to locations for reasons unrelated to the original mission. Eventually, it became evident that an adventure manuscript served two purposes simultaneously: a playable situation and a reusable body of setting information.
Alpha India as Both Adventure and Reference
Alpha India stands as the most prominent modern example because it directly descends from the first campaign line. The immediate story revolves around strange signals, Damhold, the search for the Alpha India installation, and the eventual encounter with Master Control. This forms the adventure spine, and a group can follow it from Act I through Act V.
Around that spine lies a substantial sourcebook. The Game Master gains insights into Damhold, Gothic agriculture, Chuhopi contact, Markan religion, Rangers, Redrock Dam, Imperial interests, VLF and ELF communications, the Alpha India facility, equipment, and everyday goods. Much of this material can be reused without the Master Control’s intervention.
A later campaign could revisit Damhold due to various reasons such as a vehicle needing repair, fluctuating grain prices, Rangers discovering another BEM, increased Imperial pressure, or the dam’s renewed danger. The original adventure may have concluded, but the place itself continues to evolve.
“Sacred Places” showcases the political aspect of adventures. Unlike traditional adventures with hidden monsters, this one revolves around a complex web of suffering communities, wrongdoings committed by factions, and Imperial institutions seizing opportunities in the crisis. The Troubleshooters can investigate, negotiate, rescue captives, expose crimes, support one side, withdraw, or make a settlement that satisfies no one completely.
Such an adventure cannot rely solely on encounter statistics. The Game Master requires knowledge of Blackhawk, Gothic political life, Chuhopi relationships, South Fort, Imperial institutions, religion, travel, trade, local authority, and the motives of people who will continue living in the area even after the Troubleshooters depart. This setting information plays a crucial role in adjudication as decisions can alter existing relationships.
The modern book also portrays its named characters as reusable individuals with roles beyond the immediate crisis. This is precisely what I mean by an adventure transforming into a sourcebook. An individual introduced for a specific investigation can later return due to factors like trade, law, religion, grain, frontier politics, or personal history that bring them together again.
In essence, the people involved in the scenario could outlive the narrative itself.
This concept gained significance for me because recurring characters create a sense of continuity in the world. An innkeeper who exists solely to spread rumors is a mere function. A merchant with established routes, debts, suppliers, adversaries, and familial obligations can reappear years later for reasons unrelated to their initial encounter. A Ranger encountered during a BEM hunt may later become the person who possesses knowledge of a perilous route. An Imperial official may become an ally in one situation and an obstacle in another.
Writing these characters as sourcebook material provided the Game Master with ample material to reuse them without revisiting the original plot. The adventure elucidates the pressures they face at a specific moment. The sourcebook delves into their identities, enabling the Game Master to generate new stories based on different pressures.
The same principle applies to organizations. A church, guild, military unit, trading house, village council, or scientific institution should endure the adventure that introduced it. Once its procedures and interests are established, it can independently generate future challenges.
Similarly, equipment should not exist solely because the characters have reached a location where the author intends to reward them. A weapon, radio, vehicle, medical device, tool, or trade good should have a genuine purpose in the world and a place within the systems responsible for its manufacture, maintenance, transportation, sale, or use.
An adventure might be the first time players encounter a particular item, but the sourcebook material provides comprehensive information about its true nature. This allows the Game Master to make informed decisions about where else the item might appear, who possesses the knowledge to repair it, whether ammunition or parts are readily available, and why a community values it.
This approach also safeguards the setting from the incessant escalation of adventure treasure. A new book doesn’t necessarily need to introduce a more powerful gun simply because the previous adventure already had one. Instead, it can introduce a loomcloth, field satchel, battery lantern, tool roll, boat, crop, medicine, or trade practice whose utility arises from the specific situation. This way, the world expands horizontally rather than every supplement attempting to raise the power level.
Creatures, Ecology, and Evidence
BEMs made the sourcebook function indispensable because a creature could become an object of study. If the players killed an unknown organism, the encounter might only be the beginning. They could examine its anatomy, collect samples, identify its feeding behavior, compare it with another organism, and use the resulting knowledge later.
A traditional monster entry typically answers the question of how difficult something is to fight. Negentropy required answers to additional questions. Where does it live? What does it eat? Is the observed specimen normal for the species? Does it reproduce locally? Is it XNA-based? What environmental clues reveal its presence? What parts are dangerous after death? Can local people recognize it?
Once these questions are written, the creature entry becomes sourcebook material even if the original encounter is never run again. The Game Master can place evidence of the organism somewhere else, use its ecology to alter a region, or let players recognize a later specimen because of what they learned previously.
Adventures Also Tested the Sourcebooks
The relationship moved in both directions. Adventures produced sourcebook material, but play also tested whether that material was actually useful. A description that sounded complete while I was writing could fail immediately when a player asked the one practical question I had not considered.
This practice was already evident during the Campaign 80 lunch discussions. We would discuss the previous game, I would take notes, and the manuals would undergo revisions. Subsequent adventures continued this process on a larger scale. If players repeatedly sought information that was missing, the next version of the material could provide it. Conversely, if a seemingly important rule never gained relevance, it might warrant less space.
This approach made adventures a form of field testing for the setting. They demonstrated whether the world could address questions under pressure. The most valuable source material was not merely detailed; it was detail that players could transform into decisions.
A Sourcebook: Empowering the Game Master
One practical advantage of sourcebook depth is that it grants the Game Master more opportunities to accept an unexpected player idea. If the characters decide to deviate from the main road, visit the market, inspect the dam, engage in conversation with a priest, hire a boat, examine a deceased animal, or spend two days learning about the ferry’s control, the Game Master has options to explore.
Without supporting information, the simplest response to an unexpected choice is often to block it or improvise something so thin that the players can sense the world’s unraveling. However, with sufficient source material, the Game Master can readily accept and follow the choice. While this may not immediately advance the original plot, it can unveil new problems, individuals, or valuable insights into the setting.
This design principle is also evident in the inclusion of five potential adventure lines in the initial session. I did not require the players to select Alpha India. Instead, I needed a well-prepared world that provided meaningful directions for any question they pursued.
A Sourcebook: Reducing My Dependence
There was another practical reason for writing more of the world down. In the earliest games, I was the sole author of almost all the material, so I could often recall answers from memory even when the answers weren’t explicitly stated in the copied rules. However, this approach becomes problematic when other Game Masters begin using the setting.
A sourcebook serves as a solution by transferring some of the world’s details out of the original author’s mind. It provides another Game Master with sufficient information to comprehend the functioning of a place, the desires of a faction, the common equipment, and how a local issue fits into the broader setting. The primary objective is not to dictate every answer but to establish a framework that allows for the creation of new answers without contradicting the essential elements.
Therefore, the adventure serves as an educational tool for the setting. By running the scenario, a Game Master gains a deeper understanding of the people and systems through practical experience. Consequently, the same material can be repurposed for original adventures because the book has provided more than just a plot.
Why I Prefer Reusable Problems
This also influenced the types of conflicts I wrote. A single villain can be defeated and removed, but a damaged dam, trade rivalry, religious dispute, dangerous ecology, political frontier, transportation problem, or uncertain alien biology can continue to generate situations even after one immediate crisis is resolved.
This doesn’t mean that every adventure must remain unfinished. Players should have the opportunity to achieve goals and influence the world. The crucial distinction lies in the fact that solving one problem doesn’t erase the systems surrounding it. If the Troubleshooters save a dam, the town still has a dam to maintain. If they resolve a dispute, the communities still have a relationship. If they identify a BEM, the ecology that led to the encounter continues to exist.
Sourcebook material preserves these systems, ensuring that the consequences of an adventure have a lasting impact. A subsequent campaign can revisit the same system after the immediate crisis has altered its condition, its participants, or the choices available to the players.
The Adventure Became a Gateway to the Library
As the modern Negentropy library expanded, adventures increasingly became an accessible way to explore a vast array of material. A group can embark on an adventure like Alpha India without delving into every cultural, military, technical, or regional sourcebook beforehand. The adventure provides sufficient information about the immediate world for gameplay, while related books can delve deeper into specific subjects when the group desires further exploration.
This structure mirrors the original manuals in a new format. The Standard Manual never required the inclusion of Nomiconus, Dwimmer, Logi, or Kindred in full because each body of knowledge could exist independently. Similarly, modern adventures adhere to this principle by providing enough local information to function independently, then expanding outward into a library of specialized books.
This approach ensures that the core game remains approachable without making the setting superficial. A Game Master can utilize only the necessary information for the current campaign and add depth when the players make that depth relevant.
The Rise of Adventures as Sourcebooks
Negentropy adventures evolved into sourcebooks because players consistently treated the world as an investigable and exploitable entity. They inquired about various aspects such as food, machines, roads, languages, politics, creatures, religion, trade, medicine, and equipment. They even chose to maintain a dam when they could have continued traveling. They meticulously examined radio bands, leading me to select an adventure that I hadn’t initially planned for them. They learned about BEMs, which subsequently made later encounters safer. These choices necessitated information that remained valuable even after the immediate scene concluded.
The modern books now openly convey the lessons I learned through play from the early binders: an adventure can introduce a new part of the universe and make that material available for every subsequent campaign. Acts and Scenes provide players with immediate tasks, while the sourcebook offers the Game Master a place that persists even when they decide to pursue other activities.
Therefore, I don’t view sourcebook material as mere padding around an adventure. In Negentropy, it is what enables the adventure to endure the interaction with players.