For the child who loves adventure games and computers, this book combines typing a program with solving a fantasy mystery using clues hidden in vibrant pictures.
A parent might reach for this book when their curious, screen-savvy child expresses an interest in how video games are actually made or shows a love for retro aesthetics. It is a perfect project for a child who enjoys tinkering and hands-on learning. The Mystery of Silver Mountain is a unique 1980s artifact: part book, part computer program. Your child will meticulously type a game written in the BASIC programming language into a computer, then play the adventure they just brought to life. The book's vibrant illustrations are not just for show; they contain hidden clues essential for solving the game's puzzles. This process fosters incredible resilience, problem-solving skills, and a deep sense of accomplishment, all wrapped in a classic fantasy quest of good versus evil. It's an ideal collaborative project for a parent and a 10-14 year old.
Includes text-based descriptions of fantasy combat and encounters with monsters.
Sensitive Topics
The book contains mild, non-graphic fantasy violence presented in text (e.g., encountering and defeating goblins or other monsters). The approach is secular and frames the conflict in simple terms of good versus evil. The resolution is hopeful, as success in the game is achievable through perseverance and cleverness.
Ideal Reader
The ideal reader is a patient, detail-oriented 10- to 14-year-old with an interest in retro gaming, the history of technology, or the fundamentals of coding. It is perfect for a child who enjoys puzzles and projects, and who is motivated by understanding how things work from the ground up. This is an excellent choice for a parent-child bonding activity, especially if the parent has nostalgia for the 8-bit era.
Parent Prep
This book requires significant preparation. A parent cannot simply hand it to a child. The programs are for 1980s computers. A parent will need to research and install a suitable emulator (e.g., for a Commodore 64, BBC Micro, or ZX Spectrum) on a modern computer and understand how to use it. They should be prepared to help their child with the slow process of typing and debugging the code. This is a project, not a passive read. A parent has heard their child say, "I'm bored of my games," or ask, "How do you make a video game?" The child might be showing an interest in coding but finds modern tools or languages intimidating. This book provides a tangible, goal-oriented entry point.
Age Experience
A 10 or 11-year-old will need significant adult partnership for the technical setup and debugging, focusing their enjoyment on seeing the game come to life and finding clues in the pictures. A 13 or 14-year-old may be able to handle the project more independently, gaining a deeper appreciation for programming logic, problem-solving, and the history of computing.
What Makes It Special
Its hybrid, analog-digital nature is entirely unique in the current market. Unlike modern coding books, it doesn't just teach concepts; it provides a single, large-scale project where the child builds a complete, playable game from scratch. The integration of the physical book for finding clues makes the screen-based game a more holistic, interactive experience that bridges two different modes of play.
Read plot summary
This book contains the full source code for a text-based adventure game, written in the BASIC language. The reader's task is to type the program into a computer (originally a 1980s home computer, now likely an emulator) to make it playable. The game itself is a classic fantasy quest where the player navigates a world, collects items, fights monsters, and solves puzzles to uncover the secret of Silver Mountain. The book's lavish illustrations correspond to locations within the game and contain visual clues needed to progress.
This overview was generated by AI based on the book's content and reviews, and may not capture every nuance.
Discussion Prompts
1
When you were typing the program, did you run into a 'bug' or an error? How did it feel when you finally found the mistake and made it work?
2
Which illustrated clue in the book was the most difficult or cleverest one you found? What did you have to notice to solve it?
3
This game was made decades ago. What are the biggest differences between playing this game and playing a modern game on a console or phone?
4
The game only uses text to describe what's happening. How did looking at the book's pictures while you played change the experience?
