What are your development priorties?

Moderator
Posts: 592
Joined: 2002.12
Post: #1
More questions as I'm curious about the way everyone else thinks and behaves.
No poll this time as the poll is not flexible enough to all ordering of votes.

When you develop a game or, to a lesser extent an application, what order of priority do you give to the following:

* Basic engine
* Place holder graphics
* Final graphics
* Title screen
* Audio effects
* Music
* Gameplay
* Configurability
* Private Editor
* Public Editor
* In game help
* User guide
* Promotional website
* Optimisation

Following on from that, do you take the same factors into account when you try somebody else's program in alpha / beta stages? i.e. do you mention that the graphics could be better when it is clear it should only be place holder graphics at that stage?

To kick things off, this is my order of priority:

1. Basic engine
2. Place holder graphics
3. Gameplay
4. Private Editor
5. User guide (first draft, evolves as game progresses)
6. Title screen
7. Final graphics
8. Promotional website
9. In game help
10. Configurability
11. Optimisation
12. Audio effects
13. Music
14. Public Editor
Quote this message in a reply
Member
Posts: 320
Joined: 2003.06
Post: #2
1 Basic engine
2 Place holder graphics
3 Gameplay
4 Title screen
5 Private Editor
6 Audio effects
7 Music
8 Promotional website
9 Optimisation
10 Final graphics
11 Public Editor
12 In game help
13 User guide
14 Configurability

I try to get gameplay happening ASAP which usually needs an engine and some placeholder graphics. Then for everything to start off structured properly I need the title screen and level editor. Then sounds are added as they're needed.

Optimization is done only when needed, and I won't give any help or user guide, beyond a couple of in-game things telling you what your keys are. That will be added right before shipping.

The last 4 things on my list are all polish as far as I am concerned. Need to finish the bodywork first.

Chopper, iSight Screensavers, DuckDuckDuck: http://majicjungle.com
Quote this message in a reply
Member
Posts: 338
Joined: 2004.07
Post: #3
1. Basic engine
2. Gameplay
3. Place holder graphics
4. Audio effects
5. Private Editor
6. Music
7. Promotional website (including dev. blog)
8. Title screen
9. Final graphics
10. In game help
11. User guide
12. Configurability
13. Optimisation
14. Public Editor

As far as testing, I'm a nitpicker when it comes to gameplay. I try not to pick on graphics/sound until it gets to the beta stage, unless it's something that either looks final or is really, really annoying Wink

Justin Ficarrotta
http://www.justinfic.com
"It is better to be The Man than to work for The Man." - Alexander Seropian
Quote this message in a reply
Member
Posts: 257
Joined: 2004.06
Post: #4
I'm pretty much the same as Reubert. I like getting the basic engine with some placeholder graphics running around before I start fleshing out the gameplay though I'd usually put in sound effects and music before making the title screen.

The brains and fingers behind Malarkey Software (plus caretaker of the world's two brattiest felines).
Quote this message in a reply
Oldtimer
Posts: 834
Joined: 2002.09
Post: #5
* Basic engine
* Gameplay
* Place holder graphics
* Configurability
* Private Editor
* In game help
* User guide
* Title screen
* Audio effects
* Music
* Optimisation
* Final graphics
* Public Editor
* Promotional website

That said, I just love to replace the placeholders. To see a game jump dramatically in beauty over the course of just a week... Yum.
Quote this message in a reply
Moderator
Posts: 385
Joined: 2002.08
Post: #6
1. Gameplay
2. Basic engine
3. Configurability
4. Place holder graphics
5. Private Editor
6. Optimisation - usually required multiple times, no?
7. Audio effects
8. Public Editor
9. Final graphics
10. User guide
11. In game help
12. Title screen
13. Promotional website
14. Music


Quote:Following on from that, do you take the same factors into account when you try somebody else's program in alpha / beta stages? i.e. do you mention that the graphics could be better when it is clear it should only be place holder graphics at that stage?
I try not to, unless there are technical problems with the graphics being displayed. That's very annoying to hear about known problems in a build - I usually just want feedback on whether the game is *fun* and any big horrible bug reports.

KB Productions, Car Care for iPhone/iPod Touch
@karlbecker_com
All too often, art is simply the loss of practicality.
Quote this message in a reply
Moderator
Posts: 1,560
Joined: 2003.10
Post: #7
1. Basic engine
2. Gameplay
3. Placeholder graphics
4. Private Editor
5. Audio effects
6. Title screen
7. Configurability
8. Final graphics
9. Optimization
10. Public Editor
11. Music
12. User guide
13. In game help
14. Promotional website

Yes, I'll generally take these things into account when I'm testing someone else's game. I try not to bug them about implementing things that are obviously a lower priority, or should go in later.

- Alex Diener
Quote this message in a reply
Post Reply