The First Negentropy Manuals
By Nelson McKeeby
A Game That Needed More Than Rules
By the time Campaign 80 began in September 1980, Negentropy already had a small rule system, but the rules were never going to be enough to contain the game I wanted to run. The formal mechanics were compact because their job was compact. The Five Rules and the game ladder handled uncertainty. They did not explain medicine, electronics, weapons, geology, alien biology, magic, equipment, or what kind of education a Troubleshooter needed. Those subjects were larger than the rules, and I did not want to reduce them to a collection of bonuses and special cases.
The solution was not to write one enormous rulebook. I began dividing the game into manuals. Each manual held a different kind of information and could grow without forcing every other part of the game to be rewritten. By the first months of Campaign 80 we were using a series of ring binders that contained both temporary handwritten material and cleaner typed pages. The binders were working books. They were used at the table, photocopied by players, revised after games, and expanded whenever play exposed another subject that needed attention.
This system became one of the most important structural decisions in Negentropy. The project grew by adding knowledge, not mainly by adding rules. A new problem could produce a new page. Enough connected pages could produce a new section, and eventually an entirely new manual. The modern Negentropy library is much larger and far more polished, but the basic architecture was already visible in those binders.
The Standard Manual
The Standard Manual was the closest thing we had to a conventional core rulebook. It contained the Five Rules and the general procedures that allowed play to continue when an outcome was uncertain. Its purpose was to give everyone a common method rather than to describe every possible activity in detail.
That distinction was deliberate. If a character wanted to repair a radio, grow food, identify a rock, treat a wound, or determine whether a bridge was safe, the Standard Manual did not need a separate chapter containing a game version of the entire subject. The manual established how we would judge whether the action was trivial, probable, possible, improbable, or impossible once we understood what the action actually involved. The subject knowledge came from somewhere else.
The small size of the Standard Manual could therefore be misleading. Someone looking only at the rules might assume Negentropy was a very small game. In practice the Standard Manual sat at the center of a much larger reference system. The rules were the connective tissue. The surrounding manuals, real-world books, maps, articles, and notes supplied most of the information that made decisions meaningful.
Character Forge
Character Forge dealt with what a Troubleshooter actually was. The original character record had grown from a school resume used for internships, so I thought about characters in terms of education, training, qualifications, experience, and the things a competent adult could reasonably know. Character Forge developed that idea into a shared reference.
The book summarized Areas of Knowledge and cited the outside books we used to control them. That last part was important. A Knowledge did not become true because I wrote a sentence about it in a game manual. If we were using engineering, medicine, weather, surveying, or electronics, the game could point outward to the manuals and references that explained those subjects. Character Forge therefore served partly as an index to a larger real-world library.
The first twelve-hour Campaign 80 game showed why that approach was necessary. Amy, Wayne, David, Jeff, Brandon, and Paul were all new to role-playing games, so we spent a substantial part of the day creating characters together. We used college catalogs to think through education and professional preparation. When we noticed that all of us were white and none of us was bilingual, we deliberately created a more varied team, including French, Mexican, and Ghanaian characters, and used Britannica and other references to make those backgrounds more credible. Team jobs also developed during that process because the players needed a practical way to understand how a group of specialists would work together.
Character Forge was therefore not simply a character-generation book. It was where the idea of the Troubleshooter as a trained person became operational. The character sheet did not tell a player everything the character knew. It established the education and competence from which the rest of play could proceed.
Nomiconus
Nomiconus was the manual for BEMs and PEMs, the strange organisms and entities that the players could encounter in the future. At first these creatures were much less systematically understood than they are in the modern project. Many were simply ideas for alien or unfamiliar adversaries, and some of the terminology was frankly ahead of my scientific understanding. XNA is a good example. I used the term because I wanted some BEMs to be biologically alien, not because I possessed a developed alternative genetics in 1980.
The existence of a separate creature manual nevertheless changed how encounters worked. A BEM could be recorded, compared, and studied. Information learned from one encounter could be preserved for the next. The manual could accumulate anatomy, behavior, habitat, vulnerabilities, and observations instead of treating each creature as a disposable combat obstacle.
That fit one of the things I wanted most from Campaign 80: players needed useful things to do besides fight. When the group went with a ranger to hunt a BEM, the scientific questions surrounding the organism were part of the reward. The more the team understood about BEMs and the alien biology I was calling XNA, the better prepared they became for later encounters. Knowledge itself improved survival. Nomiconus gave that knowledge somewhere to live.
Dwimmer
Dwimmer entered the game immediately before Campaign 80 because a player wanted magic and argued, in the spirit of Arthur C. Clarke, that sufficiently advanced science could appear magical. I accepted the idea, but I did not want to add a conventional list of spells. Some concepts came across from my Oasis game, including the Five Lanterns, while the rest was rebuilt to fit Negentropy's emphasis on understandable consequences.
The Dwimmer binder held the expanding magic rules as we worked out what that meant. Magic could move energy, organize or disorganize matter, and produce physical states that could actually exist. The practitioner had to understand and mentally describe the intended operation. Steel could be made tougher if the user understood what was being changed. Carbon could be arranged into diamond. Tissue could be healed through an understanding of healing. Ritual, dancing, potions, wands, or other focuses could be used to train and stabilize the practitioner's psychology so that a complex operation could be held in mind.
A separate Dwimmer manual was useful because magic generated a body of knowledge rather than merely another action table. As players discovered what could be attempted, the manual could expand. The relationship between knowledge, training, physical possibility, and the Five Lanterns needed room to develop independently of combat rules or equipment descriptions.
Logi
Logi was the equipment manual. Its origins went back to 1979, when I began thinking seriously about what Project Negentropy would actually place inside a Cylinder if the people sent forward could not later request a newer gun, better radio, larger vehicle, or replacement set of tools. Equipment selection had consequences because the Cylinder had finite volume and the team had to live with what had been packed.
The first Logi drew heavily on real equipment I could research. The French weapons associated with the former French naval serviceman I interviewed after seeing Jacques Cousteau's Calypso influenced the early arsenal. I used Joseph W. Smith's Small Arms of the World and other references to check weapons and develop game information. At the same time I was imagining X-Tech computers, radios, batteries, and other devices that could exceed contemporary equipment without becoming unlimited technology.
Keeping equipment in its own manual made practical sense. Logi could change when research improved a weapon choice or when play showed that a piece of gear was more or less useful than expected. It could contain ordinary tools beside advanced equipment because both were selected for the same reason: someone expected them to remain useful after emergence. The book was therefore as much about logistics and institutional judgment as it was about weapons.
The Miscellaneous Binder
Not everything immediately had a permanent home. We also used a miscellaneous binder for material that had not yet accumulated enough structure to justify a dedicated book. That binder was important because it allowed me to write first and classify later. A new idea did not have to wait until I knew exactly where it belonged.
This was necessary because Campaign 80 generated material quickly. A question raised during play might require an answer before the next session. I could write a temporary page, put it where everyone could find it, use it, and then decide later whether it belonged in an existing manual or whether it pointed toward something new. The filing system therefore reflected the way the game was actually being developed. Some information was provisional. Some had become stable enough to type. Some was waiting to discover what kind of subject it really was.
Handwritten Pages and Typed Pages
The binders contained both handwriting and typescript because those formats represented different stages of development. Handwritten pages were fast. I could produce them immediately after a game, during lunch, or whenever a new question occurred to me. Typed pages took more effort, so typing was usually a sign that the material had become stable enough to deserve a cleaner master.
That did not mean typed pages were permanent in the modern sense. The game was changing too quickly for that. I would type an update on the cover page when something changed, and players would photocopy the binder or add new pages to the copies they already possessed. A manual could therefore contain pages from several moments in its development. The cover update helped people determine what had been added or replaced.
In effect, we were doing version control with paper. There was no shared server, no revision history, and no automatic way to tell everyone that a file had changed. The binders, cover sheets, photocopies, and replacement pages were the distribution system. It was crude, but it allowed a group of players to keep a rapidly changing game synchronized well enough to continue playing.
Photocopying a Living Game
Players photocopied the manuals and added new pages as I produced them. This gave the game a strange physical life. There was no single immutable edition on everyone's shelf. A player's copy reflected the point at which it had last been updated. Someone who missed a few changes could have an older page until they received the replacement.
That made the manuals more like technical service documents than conventional game books. A page could be superseded because the research had improved, because a game exposed an ambiguity, or because a new adventure required information we had never needed before. The expectation was that the books would change.
The first months of Campaign 80 made that especially obvious. We had only been playing regularly since September, yet by December the manuals had accumulated enough new material that the structure itself was expanding. The campaign was not merely using the books. It was manufacturing them.
The First New Manual
The clearest example came in December 1980 when Wayne lost a character to a BEM and wanted his replacement character to be an elf. I already had long-lived people called Oldari in Oasis, where they lived in Mournewood, worshipped the moon, practiced slavery, and could themselves be enslaved. The easiest way to keep the game moving was to transfer that material into Negentropy and place Mournewood beyond the Rockies, far enough away that I did not need to define the entire region immediately.
That decision created a problem the existing Negentropy binders did not solve cleanly. The Standard Manual was rules. Character Forge was character structure and Knowledges. Nomiconus was BEMs and PEMs. Dwimmer was magic. Logi was equipment. The Oldari were a people with culture, history, biology, religion, and a homeland. They needed a different kind of book.
I already had that kind of book in Oasis. It was called Kindred, and it dealt with races. I transferred the idea into Negentropy. Kindred became the first new manual demanded by Campaign 80 itself. That was a significant moment because the game had crossed from adding pages to existing categories into creating an entirely new category of source material. The request for an elf had produced a new branch of the library.
Manuals Grew from Problems
That pattern became the normal way Negentropy expanded. The manuals were not planned as a publishing line and then filled according to an outline. They grew from problems encountered in writing and play. If players needed to understand an unfamiliar creature, Nomiconus grew. If they needed equipment, Logi grew. If character education needed clarification, Character Forge grew. If magic produced a new question, Dwimmer grew. When intelligent nonhuman peoples demanded a different treatment from monsters, Kindred appeared.
The result was modular because the underlying game was modular. A practical problem usually belonged primarily to one body of knowledge even though it could affect several others. A wounded Oldari might require Kindred biology, Healer knowledge, Dwimmer, and equipment from Logi, but those subjects did not have to be collapsed into one chapter merely because they could meet in one scene. Each manual could explain its own domain, and the game master could combine them when the situation required it.
This architecture also made research easier to incorporate. A better medical reference did not require rewriting combat. A new understanding of XNA did not require changing character creation. A revised weapon choice could be placed in Logi. The manuals gave new knowledge somewhere to go without destabilizing everything around it.
The Manuals Were Not Supplements
I did not think of the manuals as optional supplements in the way that word is often used for role-playing games. They were pieces of the same operating library. The Standard Manual could tell us how to adjudicate uncertainty, but if the adventure depended on electricity or disease, then understanding those subjects was part of play. The supporting manual or outside reference was not extra color. It supplied the model of reality against which the rules operated.
This is why the Negentropy library could grow very large while the mechanical system remained small. Complexity was allowed to reside in the subject itself. Medicine could be complicated because bodies are complicated. Engineering could be complicated because machines are complicated. A creature could have elaborate biology because organisms are elaborate. The game did not need to convert every one of those complexities into another numerical subsystem.
The manuals therefore served players who wanted to learn enough about a subject to make better decisions. They also served game masters by creating a common reference. If both sides understood what a pump, wound, radio, crop, or organism was doing, the Five Rules had something concrete to judge.
The Lunch Table as Editorial Office
The manuals were also shaped by the informal postmortems that followed games. Not everyone attended these discussions, and they were not formal design meetings. Often we would sit at lunch the next day and talk about what had happened. I would take notes.
Those conversations were one of the main ways play returned to the books. A rule that had been unclear could be rewritten. An equipment question could send me back to a reference. A player solution could reveal that the adventure needed information I had never prepared. Discussions about cinematic reality and concrete reality could expose where a dramatic assumption had collided with a physical limitation.
Because the manuals were loose-leaf binders, the result of that discussion could enter the game quickly. I did not need to wait for a new edition. I could write a page, type it if necessary, update the cover, and let players add it to their copies. The physical format matched the development process remarkably well.
A Library Built Around Play
The early manual system also helped me understand what kind of project Negentropy was becoming. The center of the game was not a single rulebook. It was a library built around play. Some parts told us how to resolve uncertainty. Some described characters. Some explained equipment, magic, creatures, or peoples. Outside references extended the library further into real science and practical knowledge.
That made it possible for the game to expand in directions I had not predicted. A player asking for an elf could create Kindred. A BEM encounter could deepen Nomiconus. A discussion of radios could enlarge Logi and Communications. A character background could send us into college catalogs and encyclopedias. The structure did not require me to know in advance which subjects would eventually become important.
It also meant that the game could accumulate history. A manual did not merely tell us how something worked in the abstract. It could preserve discoveries made during campaigns, terminology developed at the table, and decisions that had survived repeated use. The books became records of the game's growth as much as tools for running it.
From Binders to Sourcebooks
The modern Negentropy books are far more developed than those first binders, but I still recognize the original system in them. Master Control performs much of the work once handled by the Standard Manual and Character Forge. Nomiconus remains the home for extraordinary organisms and entities. Dwimmer remains a separate body of knowledge because magic still has its own principles. Logi remains concerned with equipment and what can actually be carried, maintained, and supplied. Kindred grew enormously because the Oldari were eventually joined by other peoples whose biology and cultures required books of their own.
Other subjects later became independent volumes for the same reason Kindred did in 1980. Once a body of information became large enough and useful enough, it deserved its own place. Medicine could become Healer. Mechanical systems could become Engineering. Field biology could become Naturalist. Investigation, arms, logistics, cultures, places, and campaigns could all grow without requiring the Standard Manual to become an encyclopedia.
The names and boundaries changed over time, but the architecture remained remarkably stable: keep the adjudication system compact, put knowledge where it belongs, and allow the library to expand when play demonstrates that a subject deserves sustained treatment.
The First Publishing System
Looking back, I think of the binders as Negentropy's first publishing system. They were not professionally published books, but they performed the essential functions. Material was written, edited, organized by subject, issued in versions, copied, distributed, corrected, and replaced. Players maintained their own copies and expected updates. New manuals appeared when the existing structure could no longer contain what the game needed.
The limitations of the technology shaped that system. Loose-leaf pages made revision practical in a way that a bound book would not have been. Photocopying made distribution possible. Typing created cleaner permanent pages while handwriting kept development fast. Cover updates provided a crude revision history. The entire arrangement existed because we needed a way to keep a rapidly expanding game usable with the tools available in 1980.
What began as a handful of binders became the basic model for a project that would eventually produce many books. I did not set out to create a library. I set out to answer the questions the game kept asking. The library was what happened when those answers needed somewhere to live.