ARPANET's First Multiplayer Colossal Cave Adventure
Will Crowther (original), Don Woods (expansion), network play community (1977)In 1977, Will Crowther's Colossal Cave Adventure—text-based exploration of Kentucky's Mammoth Cave system—spread across ARPANET. Something unexpected emerged: users at different nodes started sharing maps, coordinating puzzle solutions, building collective knowledge bases. Universities would see terminals clustered with students mapping caves together, arguing about optimal paths, celebrating discoveries. The gathering wasn't imposed—it emerged organically because people were drawn to the same compelling mystery. Lake over Earth: joyous gathering above receptive foundation. The game became multiplayer not through technical design but through social transformation. Two strong lines (fourth and fifth) bringing about the gathering—the king approaches his temple, people gather not by force but by shared purpose. Religious forces (the compelling mystery) combined with human leadership (experienced players guiding newcomers) created genuine community around imagined caves filled with dwarves and treasures.
Practical Integration
People are gathering around something you've built. The project's gaining momentum, the community's forming, the network effects are starting. This is what you wanted. Now comes the hard part. Here's the classical text's warning: gathering together creates vulnerability. That ARPANET adventure community? Also saw the first instances of griefing, spoiler sabotage, competition over scarce resources (terminal time). Not everyone gathered for pure reasons. Some came to disrupt. The lake rising above the earth—if it gets too high, breakthrough and flooding. In your context: your open source project gets popular. Suddenly you've got issues, pull requests, demands, complaints. People gather around your work—some to contribute, some to extract value, some to criticize. You need to renew your weapons: establish governance, set boundaries, create moderation systems, define contribution guidelines. Not because you're hostile, but because you're prepared. Or at organizational level: the team's growing, the product's scaling, the user base is expanding. This requires infrastructure—not just technical, but social. Define the center clearly. Who makes decisions? What are the values? What behavior is acceptable? Prepare these while you still can, before the pressures of rapid growth force reactive decisions. Gathering together is success—but only if you've prepared for what gathering brings. Build the temple before the congregation arrives.