Maniac Mansion Design Notes

Jul 16, 2014

While cleaning out my storage unit in Seattle, I came across a treasure trove of original documents and backup disks from the early days of Lucasfilm Games and Humongous Entertainment. I hadn't been to the unit in over 10 years and had no idea what was waiting for me.

Here is the first batch... get ready for a week of retro... Grumpy Gamer style...

First up...

A early mock-up of the Maniac Mansion UI. Gary had done a lot of art long before we had a running game, hence the near finished screen without the verbs.

A map of the mansion right after Gary and I did a big pass at cutting the design down.  Disk space was a bigger concern than production time. We had 320K. That's right. K.

Gary and I were trying to make sense of the mansion and how the puzzles flowed together. It wouldn't be until Monkey Island that the "puzzle dependency chart" would solve most of our adventure game design issues.

More design flow and ideas. The entire concept of getting characters to like you never really made it into the final game. Bobby, Joey and Greg would grow up and become Dave, Syd, Wendy, Bernard, etc..

A really early brainstorm of puzzle ideas. NASA O-ring was probably "too soon" and twenty-five years later the dumb waiter would finally make it into The Cave.

I'm still amazed Gary and I didn't get fired.

One of the things I always liked about LucasArts adventure games was that you could never get stuck in a dead end (I remember not being able to finish Hitchhiker's Guide to the Galaxy because at the very end, Marvin asked me for the only tool out of 17 that I had failed to pick up before the door locked behind me).

Presumably diagrams like the ones above helped you avoid this sort of thing. But did you use any formal techniques, or tricks to make sure the player couldn't get stuck?

One that I've noticed is to use an object that will be crucial in Chapter 3 to hide the key for getting out of Chapter 1. Any others?

Ron Gilbert
Maniac Mansion was full of deadends and crappy puzzles. The "no deadends" philosophy evolved after (and maybe because of) Maniac Mansion.

It was the Puzzle Dependency Chart that finally allowed us to avoid those issues, as well realizing it was just "bad game design".

Hi Ron,
I have always been meaning to ask you since you never commented on this bug in any of the speeches you've given about Maniac Mansion in recent years.
I remember that in the C64 Version you were able to actually walk up the plant even while it was small if you were clicking just the right spot on the hatch. You just couldn't exit the room. Similarly you could walk "up" the garage door while it was closed by just clicking on it enough. Do you remember this bug and/or what caused it?

I love those design notes. They're a fantastic insight.

Thanks, Ron.

Imagine an urban version of Monkey Island 2 where you have to travel to four American cities and collect map pieces.  When the fragments are combined, they list the directions to one of Ron's storage units.  Resting on the floor is an envelope that contains the design document revealing The Secret of Monkey Island...also a fragment.  The credits roll and the game copies a file to your Desktop.

Only when enough copies of the game are sold and completed, can the Internet finally piece these files together.  Some copies of the game produce duplicate pieces just in case someone neglects to share.

Four years pass and the final piece has finally been collected.  The news breaks the Internet for two days.  When the servers come back online a single message is blinking across millions of monitors around the world:  "Be sure to drink your Grog."

The glitch with the plant was the only reason I was ever able to win the game! I was never able to get the plant to grow with the radioactive water + soda.

@Rosstin: You must remember that wrong. You cannot actually go through the hatch while the plant is small.

Hello Mr.Gilbert. I am a big fan of his work since I was a kid and played on my Commodore Amiga this great Maniac Mansion.
I am currently preparing a program about this game for my spanish youtube channel and I wonder if you could work out some questions about the game:
  When did you exactly start working on the concept of MM with Gary? I have understood you started at Lucasfilm Games in October 1985 with a three months to make the Koronis Rift conversion to Atari 800. Do you think it was around february or march 1986?
When you started with MM you guys already went to The Stable House at the Skywalker ranch or continued on Computer Division Building in San Rafael?
Did MM development and Labyrinth: the computer game development happened at once?
Why do you think Steve Arnold trusted you and Winnick to create your own project being newcomers?
Did you participate in the 1989 enhanced ports of MM? Do you know why they changed the color of the skin of the Edison family?
Thank you very much for your time, I hope I have not bothered you with so many questions. Thanks again for sharing this incredible design notes.

Mike McP
These are awesome.  Thanks for sharing!

Disco? Ed hates you if you don't dance?!

Bobbi Sox
Just what the hell were you supposed to videotape Weird Ed doing? And did it involve the hamster?

mm_design_2_thumb.jpg Love that! It's a bit like how I felt when I first saw the Star Control 2 source code. I was like - oh so this is why this game is so great, they obsessed over making the game great and beautiful rather that then code clean and readable!
I'm currently working on some C# code and I pretty much abandonded all OO-principles and patterns, doing it all C-style. Now that it's getting "ready" I'm using the Extract Method refactoring and adding few objects where needed to get things bit more clean. I feel that doing things stricly OO-style all the way tends to interfere too much when doing bottom up feature design in the code. But that's just me.

Let me rephrase that. Given the complexity of the game it's clean and readable but there's so much hardcoded things that it was just overwhelming and modding certain things that appear simple on surface without more complete understanding would just break it.
what is two + two + two?