Adventure is an old game and one that has been known by many names: ''Adventure'', “Colossal Cave”, and the simplistic abbreviation “Advent”. As games go, it is indeed a classic, having sparked an entirely new tangent of game development in the early days of the gaming industry. Its effects can still be felt today.
I sat down this morning to write a review of a game. At some point, I figured I'd tell about its strengths and weaknesses. In the end, I'd probably assign it a value in stars or thumbs or joysticks or some other arbitrary measurement of quality. However, assigning a letter of quality to this game is nearly as anachronistic as seeing The Illiad on Oprah's booklist; it is simply inappropriate and demeans the true quality of the work. So instead, I'm going to tell you what this game has meant to me, a little about where it came from, and how it shaped the Quake III world in which we live today. We've come a long way from the early days of text adventures—or have we?
It was 1989 and I was 10. The end of the eighties was upon us, and we all looked with trepidation to the coming decade and the closing years of our millennium. The Bangles played “Walk Like an Egyptian” to hordes of onlookers not interested in the nostalgia of the moment. The economy was in a deep recession, and with the Cold War and movies like War Games, people were naturally wary of what the coming years would bring. The Berlin Wall fell that year, and we all wondered what more the future would bring. Well, I didn't wonder. I was 10, what do you expect?
Instead, I was concentrating on my own life. Already the budding geek (before the term became a compliment), I went out and hunted my butterflies (tilted my windmills) and enjoyed life. I had a Commodore 64 at the time, and thought it was the coolest thing in the world, but it never affected me. It was fun, certainly. I knew how to program simple things in Basic. I could make balloons float around on the screen. I knew that if I typed “SYS 64738”, the whole thing would reboot. But it never grew beyond a tinker toy to me—it never awakened my inner geek.
That changed, of course. My father bought me a game package he had pulled from the bargain bin. It was a set of two 5.25-inch floppies from Broderbund (the covered wagon people) entitled “Golden Oldies Volume 1.” Loading it up, I was surprised to find a collection of four “classics” of the day: Adventure, Eliza, Life and Pong. My mother decided she liked Eliza the best and would continually attempt to convince the poor thing that she was a beach ball or something similar. I found my passion in Adventure, a little game that transported me into a world filled with scary little dwarves and myriad treasures, all for the taking, if the young spelunker was up to the challenge. Needless to say, I never beat the game. I rarely drew maps, and when I did, I routinely forgot which direction was east. I had managed to memorize a large portion of the game, but in retrospect I don't think I ever truly got it. Maybe it was because I was too busy experiencing the world to really want to win. (Or more likely, because I was young and stupid, but leave me to rose-tint my world however I want, please.) Eventually, my old copy of Adventure developed bad sectors and I put it to rest.
Several times later in life, I would rediscover these games I loved. I did eventually get to play Zork (a version of Adventure) for the Apple II, and found it richly gratifying, but too similar to the game I left behind. Other games I loved: King's Quest, Quest for Glory and the early Sierra masterpieces. Somehow, even with their fancy four-color pictures and their beeps, they never transported me to a world in the same way my first Adventure did. I rediscovered Adventure when I finally turned to the “dark side” and was given a 386 and a modem to play with. It was just as I remembered it, except free from a local BBS. I played and played and mapped it a little, but I still never beat it. Life had a tendency to intrude and I put it away again, a cherished childhood game to relive later.
I was happy to rediscover my game in the BSD Gamespack (/usr/games/) that ships with many Linux distributions, including Red Hat. It was like meeting a childhood friend again on the street. Now I'd like to introduce it to you.
The game of Adventure has a long history, dating back to the earliest days of modern computing. In the beginning (1972), there was Will Crowther. He was a programmer, caver and role-player (Dungeons and Dragons, in particular). Faced with boredom (the motivational force behind many a good program), a desire to create something for his daughter and his assorted talents, he set out to create a game based on his explorations of the Mammoth and Flint Ridge cave systems in Kentucky. This game included many of the features of the later versions and included descriptions and room names taken directly from the caves in the real world.
A couple of years later, Don Woods discovered the game and added a number of fantasy elements to the plot including pesky dwarves, a dragon and whatnot. His primary inspiration was fantasy literature (such as the Lord of the Rings trilogy), and Adventure was never to be the same again.
Many other coders added bits and pieces after that point. This may be one of the earliest examples of open-source gaming. The game Adventure could be one of a dozen or more variants, each with minor scoring differences and occasional major additions. By and large, all Adventures are created equal.
|Dynamic DNS—an Object Lesson in Problem Solving||May 21, 2013|
|Using Salt Stack and Vagrant for Drupal Development||May 20, 2013|
|Making Linux and Android Get Along (It's Not as Hard as It Sounds)||May 16, 2013|
|Drupal Is a Framework: Why Everyone Needs to Understand This||May 15, 2013|
|Home, My Backup Data Center||May 13, 2013|
|Non-Linux FOSS: Seashore||May 10, 2013|
- RSS Feeds
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Using Salt Stack and Vagrant for Drupal Development
- Dynamic DNS—an Object Lesson in Problem Solving
- New Products
- Validate an E-Mail Address with PHP, the Right Way
- Drupal Is a Framework: Why Everyone Needs to Understand This
- A Topic for Discussion - Open Source Feature-Richness?
- Download the Free Red Hat White Paper "Using an Open Source Framework to Catch the Bad Guy"
- Tech Tip: Really Simple HTTP Server with Python
45 min 27 sec ago
- Keeping track of IP address
2 hours 36 min ago
- Roll your own dynamic dns
7 hours 49 min ago
- Please correct the URL for Salt Stack's web site
11 hours 1 min ago
- Android is Linux -- why no better inter-operation
13 hours 16 min ago
- Connecting Android device to desktop Linux via USB
13 hours 45 min ago
- Find new cell phone and tablet pc
14 hours 43 min ago
16 hours 12 min ago
- Automatically updating Guest Additions
17 hours 20 min ago
- I like your topic on android
18 hours 7 min ago
Enter to Win an Adafruit Pi Cobbler Breakout Kit for Raspberry Pi
It's Raspberry Pi month at Linux Journal. Each week in May, Adafruit will be giving away a Pi-related prize to a lucky, randomly drawn LJ reader. Winners will be announced weekly.
Fill out the fields below to enter to win this week's prize-- a Pi Cobbler Breakout Kit for Raspberry Pi.
Congratulations to our winners so far:
- 5-8-13, Pi Starter Pack: Jack Davis
- 5-15-13, Pi Model B 512MB RAM: Patrick Dunn
- 5-21-13, Prototyping Pi Plate Kit: Philip Kirby
- Next winner announced on 5-27-13!
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?