Open trescenzi opened 12 years ago
It's an interesting idea, but I feel it leaves too much to be desired. As an example, you mentioned branching and commiting -- it seems really hard to explain that to a world like this.
I also thought bugs spawned only from your code, and then attributed to the final bug -- I didn't think any already existed.
I was thinking we'd keep it exactly what it was -- coding. It can then alternatively be treated as a "learn git" tool, while also being a ridiculously fun game.
Too many of the concepts seem foreign to any idea other than Developing.
I'm still open to this story if you really like the idea of adding a non-developer background for the game.
we were talking earlier, just copying ideas down here --
I was thinking we should make it ABOUT programming, just building blocks instead of typing code.
So, our programmer, given an impossible deadline, rushes to code. Late in the night, he literally gets SUCKED IN! The only way to escape is to finish the project, and clean the bugs.
Ok so I think we need a "Story" in the sense that we need a way to explain what is going on in the game and why you are doing what you're doing. I don't think it needs to be complex but I do think it is necessary to provide motivation for the player. Here's what I came up with over the course of my Japanese Lit class :p
The game is set in a distopian future in which there is a shit ton of trash and most cities have been devastated by war. People have fled to the far corners of the Earth and have built "bugs" that are designed to remove and clean up the trash (yea I guess it does kinda sound like wall-e but that's fine by me). You control an A.I. that used to be the master of a city. Under it's command are a bunch of robots and it plans to use the robots to rebuild the city, collect resources and get rid of the bugs.
So the reason I like this idea:
Things still missing: Why branching and committing does anything. I'm still trying to figure that bit out.