So, I made up my mind

In the , I was talking about my hello world game, but is quickly becoming a PET PROJECT, and I have decided to FINISH IT.



Of course that means a lot more than just programming and adding stolen sprites, it means I need to make my own graphics (which I been doing with certain degrees of success) and a LOT MORE!.




The tools I'm using:



*to make the sprites.

*to make the sprites sheets and corresponding plists.

*for the virtual joystick (I forked the project but haven'tmade any changes, original author )

*for the glue that binds all together



This question has interesting points about keeping a game pet project rolling:



These tips apply to any hobby software project, and not just games.



* SET TINY MILESTONES. Having a goal like "item system works in my RPG game" is all well and good, but that implies a whole lot of under-specified functionality that you probably didn't even know you needed. What about "graphics environment set up"? Or, "A sprite is displayed on the screen."

* DO A LITTLE BIT EACH DAY. Marathon sessions are great and all, but you're trying to squeeze a long-term commitment into an already crowded life. If you do a little bit each day you are making measurable progress and establishing a structure within which you can achieve your milestones.

* SCALE YOURSELF BACK. Whatever your grand vision is, try and figure out what the smallest achievable portion is and do that. Making an RPG? Start with one quest and no NPCs. Making a platformer? Start with one level and no enemies.

* PROTOTYPE EARLY. Before you sink a bunch of your hard-earned hobby hours into a game, figure out if it'd be fun first. There's nothing so dispiriting as working your ass off on something for dozens of hours only to find that the basic concept sucks.

* DEVELOP SOMETHING ITERABLE. My favorite hobby software projects are the ones where the basic concept allows for later tinkering. Is your game like that? Can you ship something and then revisit it later and add cool stuff?

* DON'T BUILD AN ENGINE OR A FRAMEWORK. You don't want an engine, you want a game. Don't worry about the framework-y, reusable bits until after your game is shipping. Once you start on the second game, then you can go back to your first and see if there's anything you could bring over. That's not to say that you shouldn't use sound software development praxis, but don't start by writing a Sprite class until you know what you need your sprites to do -- you'd be surprised how little it'll turn out to be. Start with a Hero class, then a Monster class, and then -- oh look! -- there's some common stuff!

* SHIPPING IS A FEATURE. You're never going to finish your game, you're only going to abandon it. ( = What is the minimum amount you can do before you're not completely embarrassed to show your game to someone else? Chances are, you can do less than that and still have a game to be proud of.



Answer by:
Full Post