This is Bananattack.

Tag: gamagame

Making a game out of progress does not help progress on making games.

Posted by Overkill on May 18, 2009 at 12:11 am under Uncategorized

Yeah, so, a couple posts ago, I mentioned Gamagame (The Game Making Game), which was supposed to be a fun way to keep tabs on what sort of progress I have left.

Unfortunately, it eventually got in the way of real progress for making games, along with school and the paid webwork I was finishing up.

So my idea to help me more efficiently make work on games eventually ended up with me become much, much, less effecient, as I got horrible horrible ideas to make a twitter app instead of making games like I was supposed to.

And even before I was obsessed with making a webapp for my progress tracking, the premise of the progress game was a bad one. It was penalizing me for not getting work done, which is fair, but it was based on “progress points” allocated earlier in the week. The thing is, later, I might realize one of the tasks requires a lot more work, and so it can’t be done for a very long time. So those would be wasted points. It didn’t focus on the big picture, so tasks would be arbitrary things, which might not even be relevant to actual game progress.

Anyways, I don’t care to talk about anymore. Gamagame, good bye.

I am going to make progress through traditional methods. Well-crafted design documents, implementation requirement documentation, and to-do lists. Prepare for further announcements, as I discuss recent game development.

Tags: ,

No comments (make one!)


Temporal Stasis

Posted by Overkill on April 3, 2009 at 6:00 pm under Uncategorized

I’m putting this project on hold temporary, since I have exams. I also want to participate in Thrasher’s 24h compo idea tomorrow, and I want make a twitter app to automate Gamagame.

I will return sooner or later though. Later!

Tags: , , ,

No comments (make one!)


Resonating

Posted by Overkill on March 29, 2009 at 11:09 pm under Uncategorized

So I had earlier abandoned Resonance for another game idea, thinking it was the right thing to do. I figured that Resonance was too complicated, and would require too much work to get anywhere. In a way, I was right, but now I realize that I was also mistaken in these judgements. It was complex, but not to the point of disrepair. It just needs some loving and nurturing.

Upon review I know of several ways that I can make this idea work better. In addition to that, I have a lot of existing code for Resonance, that simply needs moderate updating to work with new ideas I’ve acquired.

I’m thinking of reducing the complexity of Resonance quite a bit, so that it’s more fun, and more structured for use in story and level design. Level design is something I desperately need to improve, but I think I’ve finally formulated some ideas to remedy that. Once I’ve verified that they work for me, I’ll be glad to share them to everyone reading this.

I know how vague this sounds right now, but I intend to turn my development around. Sticking with a project has always been difficult to me, but I think Resonance has many things that I consider good for a full game.

School is consuming my time, and it’s confusing my thoughts. I don’t write things down and plan enough, and this is why I have been all over the place with my development time. I end up adding things to engines which ultimately I don’t even need, or making my life needlesssly challenging by reinventing the wheel. I distract myself with various tiny details rather than working toward a bigger picture.

So Resonance it is. What I need for the game will determine what I spend time on. I have yet to develop a full list of what I need, only ideas.

Thus my immediate task: To jot down what Resonance had before, and what Resonance needs to become a feasible project while not compromising on fun.

Oh and I might also sink some time into making a simple site for this silly Gamagame challenge I’ve imposed upon myself.

Anyway. Until the next incoherent babble post, farewell!
 
 

Summary (as of March 30, 2009)

Productivity Points: 15/21 (-4 for days since post, +5 for deciding on the game idea)
Tasks for the Week (Must sum to 10 points):

  • Describe how to scale back the old game system by reducing complexity. (4)
  • Decide on how much code can be reused. (1)
  • Come up with a rough story outline (2)
  • Come up with actually concrete designs for the first level of the game. (3)

Tags: , ,

No comments (make one!)


The Game Making Game

Posted by Overkill on March 26, 2009 at 5:35 pm under Uncategorized

So, after agonizing a lot last week, I came up with an idea. A ridiculous idea that started as a joke. One so ridiculous, it just might work for real development.

Let me present to you a challenge. I call it Gamagame.

Gamagame is a one-player game where the player (literally) plays the role of a game creator!

Starting off
The player starts by deciding what sort of genre and the expected play time of their game project. The player will then be thrown into the world of making games. There are plenty of adversaries and events to overcome in the Gamagame world, and it is the duty of the player to conquer them.

Basics

  • The player starts with 14 Productivity Points. This amount is lowered by inactivity, and rewarded by constructive activity. Details on how to gain and lose points is described below.
  • The player can have a maximum of 21 Productivity Points initially.
  • When the player has 90%+ of their Max Productivity Points, he is “kicking ass”. Streaks should be noted.
  • When the player is above or at exactly 30% Productivity Points, he is “okay”.
  • When the player is below 30% Productivity Points, he is “crawling”.
  • When the player has 0 Productivity Points, the project is considered “idle”.
  • When the player has -7 Productivity Points, the project is called “frozen”, and Gamagame should probably end before it becomes shameful. It can be continued though in an attempt to rescue it.
  • When the player has -14 Productivity Points, the project is called “buried” with no chance of rescue, and Gamagame ends with shame.

Getting Points

  • The player gets 5 points for coming up with the initial game idea.
  • After the initial idea, the player splits assigns a bunch of tasks for each week. These can be broad categories for later weeks, but should be solidified ideas when getting closer in time. The player rate each task for the current week, with 10 points to divide between all tasks for that week. Fractional points may be given. The point rating assigned is the reward of productivity points the player gets upon completion.
  • The player can announce their intent to get extra work done (that is, tasks for later weeks), for a fixed 2 extra productivity points at the end of the week. The points for the extra tasks themselves aren’t rewarded, only the fixed 2 point reward at the end of the week. Failing to do anything by the end of the week after intending to do extra means that 3 points are lost.
  • The player can put Gamagame on hold for as long as they want, if there are distractions like work, school, or various life events interfering. No productivity points will be lost. But all delays should be counted, and for every 14 days spent on hold, 3 productivity points should be lost.

Penalties and Project Progression

  • For each day on the project, 1 productivity point is lost.
  • When the project is considered 50% complete, the penalties double, and max productivity points goes to 42.
  • When the project is considered 75% complete, the penalties and rewards both double (penalties are then quadruple the base), and max productivity points goes to 70.
  • These can be adjusted if they’re too ravenous, but make a note of it, and don’t intentionally cheat the system.

Teammates

  • If the player is to enrol other teammates, don’t include them in your game score or anything (especially don’t make them play this silly game unless they’re as crazy as you).
  • If they complete one of YOUR tasks, you get points for that, but don’t deliberately put their tasks under your tasks for the week.
  • The only other effect team members have: any teammate who ends up doing nothing or qutting costs you 3 productivity points when you realize this.

Ending Gamagame

  • Gamagame is won when the project is 100% complete and released.
  • The player loses upon forfeiting Gamagame, or by being “buried” shamefully for having -14 productivity points.
  • Keep track of how many wins, loses, and shames you have. They could indicate a problem with how you’re developing games!

 
 
Also note the fixed reward of 2 points for doing extra tasks each week. This is to somewhat prevent being sidetracked, and to ensure that new ideas are considered ahead of time and waited on, instead of being thrown in for no reason. 2 points alone isn’t enough to save you in the long run anyhow.

Anyway, let’s begin craziness!
 
 

Summary (as of March 26, 2009)

Player Info
Name: Overkill
Productivity Points (-1 per day of inactivity): 14 / 21 PP
Status: Okay

Game Info
Game genre: Sidescroller + shmup (possibly a Shmuptroidvania, we’ll see)
Expected play time: 3 hours

Here we go! Now to hopefully not lose at yet another thing. May my craziness be a rewarding thing.

Tags: , , ,

No comments (make one!)