next »

[thatshelby]

There is a subculture of game developers on this forum that never finish games, that don't feel comfortable with releasing them, or are just unable to.

I haven't really released a game- just a couple of open source things off this site. I've tried many things to help me get over my subconscious fear of non-constructive criticism, so I keep trying to improve my game to meet new standards. I take different directions with the game, trying to add more content, changing the controls, making new features. Always adding, but never cutting. Perhaps this is the cause of the syndrome? I say no. I tried making a simple game. Maybe it was too simple, so I added. And then I cut. Where is the equilibrium? What is the right balance for content? Maybe the features of the game aren't necessarily the cause of this disease. Perhaps it's something personal. A fear of criticism, like I said. Motivation generally is high for me. I am motivated by the idea of finishing just one game.

How does one get over this? There are a million threads like this, and this may sound selfish, but I want to address the issue for myself and for those in my shoes.

Thanks for reading.

[ugriffin]

How does one get over this? There are a million threads like this, and this may sound selfish, but I want to address the issue for myself and for those in my shoes.

Thanks for reading.

Just release stuff, and learn from your mistakes... from what people complain about. Who cares about what other people think.

[thatshelby]

Thanks for the reply.

Another thing that comes to mind- most developers use tools like Game Maker or other simple-to-use tools that give you results, and fast. Maybe I'm thinking the game design process will go the same.



Psssst ~ Nice to see you on TIGs!

[_Madk]

What frequently happens to me is I have time and enthusiasm so I start a project, but then I stop having time (because, unfortunately, the entirety of my life is not spent in a place capable of supporting coding) and though I am capable of sticking to my code once the excitement has waned, if I don't have time to work on it for a while I start forgetting important things, like that I was making a game in the first place.

This is why I love Ludum Dare - it gives me an excuse to sit at my computer for 48 hours straight with only brief breaks for sleeping, eating, and urinating, and it is during this time of unhindered, unmatched focus and people generally just leaving me the hell alone for a while that I can actually get things done.

Christmas break from school has yielded similar results in the past, because I'm at home undisturbed for a couple weeks straight.

When it comes to losing enthusiasm, just keep working until you get your second wind, or until the game is done. Whichever comes first. Getting the game done will almost invariably come first.

When it comes to just not having time, the ideal solution should be to make more time. If this is not an option, as it often is not, find something else to do until you can. I usually play some video games or read a book. You may wonder to yourself how you can have time for things like this and not for programming - it's because when programming anything substantial, and I'm speaking from my own perspective here, the second most vitally important thing to have is an impressively long stretch of time in which disturbances from things that are not your game will be minimal (ideally stretching over a month or so). The single most important thing is, quite plainly, a medium through which to program, probably a computer. This time scale of course pertains to nonprofessional development. I'm not professional (though I intend to someday be) but I would imagine that as a professional your work hours would be your concentration time.

[doompuppet]

Before release - Ego-stroking notes of anticipation.
After release - Soul-crushing glitch complaints.

[ugriffin]

Before release - Ego-stroking notes of anticipation.
After release - Soul-crushing glitch complaints.

This.

Sir, you've just reduced game development to two, wise lines. I salute you. 

[Paul Eres]

you make a list of features or things the game needs to have to be considered finished

you don't change that list (sometimes called feature-locking the design)

you release it when that list of features are all implemented

[Player Ʒ]

The syndrome of never going to happen is called Episode Three Syndrome. Just to clarify the difference.

[Xion]

for me it's pretty much everything madk said. Work hard as fuck on something for a few weeks of free time, then lose that free time, then lose my place in the development, then lose enthusiasm due to not knowing shit any more, or finding a bug I don't know how to fix because everything is foreign.

[thatshelby]

you make a list of features or things the game needs to have to be considered finished

you don't change that list (sometimes called feature-locking the design)

you release it when that list of features are all implemented

Very smart idea, and I'm surprised I didn't think/hear of it before.

[Gabriel Verdon]

Learning through experience is the best way.

[Rob Lach]

Ugh, this totally defines me.

[Dugan]

you make a list of features or things the game needs to have to be considered finished

you don't change that list (sometimes called feature-locking the design)

you release it when that list of features are all implemented

Very smart idea, and I'm surprised I didn't think/hear of it before.

yep - and at the end you can always apply a change control process, in case you have some new ideas you want to add to the game.

eg: Each idea could be considered in terms of `value` it would add versus time to implement versus risk of breaking the current game in some unknown manner etc etc.

You have to really step back from your project though and be very strict to make sure you dont get sucked into never ending feature creep.

[Paul Eres]

i guess that'd be okay but i think that if someone has trouble finishing games they shouldn't risk even that. or perhaps do a 'if i want a new feature that i don't have on the list i'll have to cut out one of the features i *do* have on the list in sacrifice'

[Mipe]

Making games is overrated. It is much more satisfying to crush the foolish developers with large amounts of bug/glitch reports.