How to organize my self

[Delifisek]

Hello all,

I had some problems other than technical or design...

Simply I cannot continue... My development was stalled...

My coding platform is ready,  I do lots of design investigation read tons of RPG (gurps, batlefleet gothic, battletech) books to generate a desing. I setup a wiki for game design...


And ?

my problem is, everything look like some kind of dark, there where to many things to do, every day I start to do some coding. After some time I feel exhausted.

I cannot stop my self to thinking, damn how can I finish that game... Then my passion start to go away...

So ?

When you feel something like that, is there any way to rid of this...

Thanks...

[famulus]

My suggestion is to split your project up into a number of much smaller tasks.  Ideally, you want the tasks to be small enough that you can finish a few of them a day.  This will give you constant positive reinforcement from completing something while continuing to make progress on the larger project.

[Nox]

I wanted to post in a similar fashion

1) tick every little progress you do
2) make yourself a plan, rather detailed one (can start with main things and then add subtasks)
....not just that you see a progress, but you also see the end
3) split your goals into layers, don't try to make the whole game in one round, make a simpler one and improve and expand it then

Btw I think your English has greatly improved!

[Chris]

I do lots of design investigation read tons of RPG (gurps, batlefleet gothic, battletech) books to generate a desing.

Stop it. Reading/investigating upon design is a sure death mark for a project. Trying to fit things like GURPS into your simple game design surely will give you a headache

I setup a wiki for game design...

What for? How is it going to help you make the game faster? Are you making a game or are you teaching how to make a game? Doing these both at the same time is a veeeeery bad idea.

After some time I feel exhausted.

No wonder If I were to read all day about design or other crap, next update my game design wiki, then when I get to actually coding I would get exhausted after a few minutes too.

[lolninja]

Yeah I think Chris is spot on here, it might be worth scaling back your ideas and rolling with something simple but extensible to start with, then you can start dropping in GURPS and other complex rules system.

You'll be surprised how much steam/motivation a little "win" can give you.

[gnoh]

I have a small whiteboard with a list of big features I want to add, I then make index cards of the problem broken down.  Crossing things off the list and flicking through the old cards is definitely a motivator. 

one small step at a time gets you where you're going.

[Delifisek]

Yeah,

I think its time to stop whining, get coding...

In design stage, everything is looking good.

And when I start to getting things together I started to see bottom of the iceberg.

It seems I failed to break apart design elements to code pieces.

Anyway. Thanks for the support...

Sometimes hearing "everything will be fine" is much better than anything else...

Regards...

[dsheroh]

The first thing you do is make a guy run and shoot.

It doesn't matter whether there's anything for him to shoot at.  You don't need obstacles for him to run around or skills to control how well he shoots.  Just make him run and shoot.  Everything else can be added later.

Of course, if it's not a "guy running around and shooting" game, that doesn't apply literally, but the basic concept still works:  Decide on your most basic core activity and build just that.  Once it's working, find the next-most-important piece and add that.  Repeat until finished.  Don't try to build the whole thing, in all of its glory (and complexity), at once.

[Shrapnel]

I have never made my own game but I feel I'd really like to.  I can relate to Delifisek's post.  A game project seems overwhelming and I just don't know where to start.  I think some excellent advice has been given here, but it would be helpful to have some clarification on what is meant by breaking the project into subtasks.  This is because to me, I have a problem seeing subtasks.  If a work on part of the game, all I see is an incomplete game.  What would people recommend be considered separate tasks?  What order should they be worked on?

[Chris]

A game project seems overwhelming and I just don't know where to start.

1) Start with register/login/logout system.
2) Next upload it via FTP and post on some hacking forum and ask the people there to hack it, then read about sql injection and fix it.
3) Make a list of users (on logged already page only).
4) Make a profile of an user page (displayed after clicking the username from the list).
5) Make an option to send private message to selected user (from their profile page).
6) Make a separate admin only page, test if regular users can not access it, display there a summary of all users (count * from users).
7) Add a list of users on admin only page, make "delete user" option next to the username.
8) Make a page to let users change password, test if they can not change password of other users.
9) Make a variable for an user and make cronjob to increase that variable by +1 each minute/hour/day. Setup the cronjob on your webhost properly.