Game: Unexplainable Glitches
Design (what I set out to do): I set out to make a fairly complex game including mazes, various monsters, a collecting/spending system, all topped off with a simple (but cool) story line. Obviously nothing near that happened. Realizing my inability to program complexly (at least I'm no where near labeled as "good" yet), I had to dumb the game down quite a bit. I was disappointed with the product, but that was what my skills could get me in the allowed time.	What Didn't Get Done:   Because I built it on Scratch the game area wasn't nearly as big as I wanted it to be, and that limited quite a number of things I wanted to do. I also didn't have time to fish out all the glitches. I wanted to add more levels; I had at least 5 programmed, but since one of my glitches was going between the levels, I had to delete quite a few of them. I also wanted to add in a title screen and some starting dialogue, but, again, due to glitches this was unable to happen.
Biggest Challenge:   THE GLITCHES. Computers are definitely dumb, but then they're even dumber when they can't process a simple command. I went through the programming time and time and time again, trying to figure out why this sprite appeared ahead of time or why this sprite was upside down or why this backdrop lagged... the list is really endless. When the project was presented to us, I had planned on using Construct 2, so the first 3 or so classes were spent trying to plan my game via that platform, so when I discovered that I was going to be using Scratch, it cut into some time I could have spent fixing glitches.	What's Next: No idea. Doing this game definitely helped me sort out ideas and realize the true complexity to building a game, so the next step would probably be to build something using Construct 2, taking my time and not feeling stressed about getting graded for it. If I did decide to fix up "Unexplainable Glitches," I would probably fix the glitches and build on more levels.