Sorry your browser is not supported!

When you thought of a new game or program idea how do you go about produceing it

do you...

just rush in, start and see how far you get

or do you...

write down every little detail as to what your going to do befor you even touch a computer

or do you...

write down what you need i.e. functions, resources. and then write your code acording to what youve writen down.

This is how I do... it's very amatour though, but I'm not a prof and I make games mostly for fun so:

I first get an idea . Then I try to see if my idea is original or not. If not, then I try to get a game which almost matches my idea... Like Doom or Final Fantasy for exemple, if I thought in a FPS or a RPG .

Then I write in a paper what the game will do, and where it will be diferent from the games I'm baseaded . I create the main caracters, also in papers, plot and everything

Then I go to code it . I realy make a pizza on it... If it's just me coding, then I skip most of the comments... Usually, I use varibles which does not need comments, like "score#" and things like that. I do the stuff really hard coded, just I can get it to work. The caracters are nothing but boxes.
If I can feel what I have done has a future, so I proceed... Make the coding nicer and better commented ( u might need someone to join the team and code too ) and see what can be done to speed up, decide if functions/gosubs and everything u tired to do and start to play with textures and modeling That's it . Althought I don't think it works, once I never could acomplish a game with a team... I have lots of fun .

Well, I don't spend a great deal of time on the planning - I just come up with an idea and then leap straight into it.

However, I start with the 3D models and textures and also begin making 'preliminary' coding. For example, my latest game barely has any solid coding yet, but I've already made a particle engine, random name generator, an MP3 finder/loader and a whole lot of 3D models. While I'm making these models, I begin to come up with new ideas for the game (some of which get written down) and how I'm going to implement certain things.

When I think I've got enough models, I make the game with what I've got. Once I've got it working that far, I begin to add more and more to it (usually planned stuff anyway) until it's finished!

Likewise, my coding is so haphazard and confusing that only I can understand it (only just, at the best of times).

That's how I made Sherman and that's how I'm making my new game! Hope any would-be recruits aren't reading this...

me myself, I come up with an idea think about how i could make it, then start writeing code

I make the resources when i need them, so if i needed a picture of a ball i would make it and then continue with the code

I write a list of functions required and get the actual program working first then once thats done I add in the menu systems

then sit back relax and think to my self "AHH!!! once again i have produced a work of art"

as for what i'm making at the moment, thats a secret, but it's a utility and i hope it will be useful.

first, I write what I will need.. an exemple ? for my game, I need :
- 3d objects
- sounds
- 16 matrix with 3d objects on them
- pictures

then I look what I can do myself :
- 16 matrix with 3d objects on them

next, I tell my friends what they can do ( 3d objects, pictures, and find sounds )

then I begin to make what I can do myself, and randomize a matrix and position objects on it with a random command isn't hard enough for me : I build a programm to make the matrix and to position object on it

and only when I have what I can make ( and a few uglies 3d objects to begin ), I begin to programm.
I make one thing after the other ; even if I have greats ideas, I don't "burn a step" ( french expression )
and a council : for the beggining, use a maximum of gosub, one for the camera, one other for the IA, ... if you don't do it, your code will be a mess greater than my room