A Game to Make Games?

11/21/14

Yesterday, I let my most recent Github streak die. I was falling into the same pattern as with the last streak. Too many of the days was submitting a simple issue to the github project.

I liked the issues I posted, but it isn't actually work. Especially when all I'm really doing is remembering or finding a note somewhere else and just putting it in the issues area.

So, no Github streak fixations for me. I want to focus on doing actual work in some way.

So, I'd like to introduce my simple game idea:

AgileGame: The Roguelike Gamemaking Game!

Gamejam was a really good learning experience for me. Could I fit that experience into something as small as one hour? Per day?

I'd like to try, Stephan!

So, starting tomorrow, I'm going to try and make a game in one hour according to the rules of AgileGame.

"So, what're the rules?"

....

Let's find out!

• AgileGame's game starts with a repository
  • The repository has a game_engine submodule
  • Otherwise, the repository starts empty
• I randomly come up with a theme or goal
• I have one hour to make a game, once over:
  • I must revert to the most recent github push
  • All progress since then is lost

"So, what makes this a roguelike?"

....

• Code from previous games can not be used
• Unless that code was saved within game_engine

game_engine will be the only thing that gets saved from AgileGame session to session. During a play session of AgileGame, nothing outside of the game repository can be used as reference.

I get caught in lookup webs too often, I don't have time during a session of AgileGame to both research stuff and get things done. For example, Stephan, I just thought "Hey, could I literally make this a game? Like, a real web game? ... Could I make it so switching tabs or focus warns the player that the current session will automatically end?" Ten minutes later, I got back on track to writing this post. (The answer: I don't know, I decided to focus on this post. Probably yes.)

As stated yesterday, I want to properly separate the research from the thinking and doing. And also separate the thinking and doing a bit, but that's a whole nother can of worms.

"So, why aren't you starting today? Like, after this blog post?"

....

Maybe I should take away your talking privledges on this blog, Stephan.

Originally, I was going to start right after this post, but one, it's getting late, two, I want to play some games today, and three, I need to setup the bare bones game_engine and stuff to make playing AgileGame tomorrow need as little setup as possible.

Actually, wait, no, I take that back. I did sorta kinda do one. It's this blog post itself. I kinda didn't follow the rules, exactly, but those rules were made during this session, so whatevs.

Also, there's no real reason this has to be only about making games, it could just be a general development or prototype creation game. I'm focusing on games for right now, though, so let's make it game-specific.

Rules and functionality and even the name will change at my whims as I mess with this.