So I'm working on my fps game from last 5 months. I implemented everything on graphics including animation and static model rendering. I wish to complete my game and I want it to be a multiplayer game like Call of Duty/CS. I've implemented little physics stuff from bullet physics. Now I wish to study sound and networking and i think this is going to take huge time. What should I now? I want to finish my game and work on another project. How to make player die when someone shoots him? How to make gun fire? How to add multiplayer support to my game? I'm not an artist and I'm alone working on this project. What advice would you like to give me?

What advice would you like to give me?

Set realistic goals.

It sounds like you're either getting frustrated or just tired of working on the same project. Spending 5 months just getting rendering working is a little strange to be honest, unless you've been working at it VERY rarely.

What I would do:

-Decide if you're fine with adding a lot more code to your game, if you are, then sit down and figure out what your goals are with your game. If you're having trouble deciding what to work on then do the "what would I play" test, think about the order of things you can add to your game that will make it fun to play around with. Is the game going to have enemies to shoot? Well networking is probably second of importance then if you can't even shoot enemies or be killed yet. Is it all networked and only PVP? Networking is probably a higher priority then so you can start testing the actual mechanics.

-If you feel like you're gonna snap if you keep working on your game for much longer, then sit down and think how you could round the game off. You could probably do without sound for example, or some very basic sound, focus on adding the few features to the game to make it more like a game. If anything the worst part of putting months of work into a project is the temptation to just abandon it, at least make it so when you pop it open again in the future it acts like a game.

Personally I would focus on making the shooting game have actual shooting and defeating enemies before the other stuff, add stuff either in gameplay order or in the order that most interests you if you're working by yourself.

What advice would you like to give me?

Set realistic goals.

It sounds like you're either getting frustrated or just tired of working on the same project. Spending 5 months just getting rendering working is a little strange to be honest, unless you've been working at it VERY rarely.

What I would do:

-Decide if you're fine with adding a lot more code to your game, if you are, then sit down and figure out what your goals are with your game. If you're having trouble deciding what to work on then do the "what would I play" test, think about the order of things you can add to your game that will make it fun to play around with. Is the game going to have enemies to shoot? Well networking is probably second of importance then if you can't even shoot enemies or be killed yet. Is it all networked and only PVP? Networking is probably a higher priority then so you can start testing the actual mechanics.

-If you feel like you're gonna snap if you keep working on your game for much longer, then sit down and think how you could round the game off. You could probably do without sound for example, or some very basic sound, focus on adding the few features to the game to make it more like a game. If anything the worst part of putting months of work into a project is the temptation to just abandon it, at least make it so when you pop it open again in the future it acts like a game.

Personally I would focus on making the shooting game have actual shooting and defeating enemies before the other stuff, add stuff either in gameplay order or in the order that most interests you if you're working by yourself.

Thanks for the advice but I didn't had experience with DirectX Graphics API when I started the project. I was learning plus making the game at same time so it took that much time.

You shouldn't have to justify yourself - if you want to take 5 months doing graphics, then that is perfectly fine.

Exactly! How many companies do you see justify why they postpone games and then suddenly cancel them? Blizzard never justified why they finally canceled Starcraft Ghost. The reason is that they don't have to justify why they start and stop projects nor do they have to justify why it takes so long to make their game and the same goes for beginners and indies. Though, gamers would have you believe otherwise.

So I'm working on my fps game from last 5 months.

Maybe you can write up something like a blog that tells of the success and failures you have so other beginners looking to make a similar game can kind of see what they may encounter. Also include what challenges and hangups you encountered as you make it. Just a thought for you to consider.

Thank you for all this advice. I now understood that it is not important to finish the project but it is important to learn more and more. I already have a journal and a blog but there were very few comments so i stopped posting. But i think i will do it now again.

I now understood that it is not important to finish the project but it is important to learn more and more.

Well yes and no. It is important to learn more, but if you plan to either publish it or use it in your portfolio then finishing the project is very important. Those are really the only two reasons to finish a game to as close to 100% as possible. Otherwise just keep plugging away and learning.

I already have a journal and a blog but there were very few comments so i stopped posting. But i think i will do it now again.

Lack of comments is never a reason to stop. When you solve a problem and blog about it you may be the person that helps another beginner understand what they missed or may give direction to a directionless beginner. If you stop, then they may never find that 'Aha!' moment. Okay, that may be drastic, but it is an honest truth.

Wow. I've been working on my curret project for 8 years lol and I'm no where near anything Hehe and I love it.

first get your objects and all game things running, then look in to networking, but you may want to first make some small network chat app and get the fill of it first.

you may need to work on shooting since you stated how do I shoot stuff.

you will need to be able to move things in your game world, some math needed like vectors to move objects based on your frame delta.

what I did first was get the main graphics up and running, then get a sprite to move from one side of the screen to the other and go from what you learn.

So I'm working on my fps game from last 5 months.I'm not an artist and I'm alone working on this project. What advice would you like to give me?

The best advice I have for you is simply to remember that you will not get everything right the first time. Or the second. Hell, I've been doing this professionally for 14 years and every time I start from scratch I build something better than I had before.

The point is every iteration of your systems and the overall structure is a learning experience. Get it working, keep good notes on what kinds of problems you end up with, and think about how you might have designed things differently to avoid those problems. Same goes for the game design. It's unlikely that your first game will be awesome, so don't let that put you off. As long as you keep learning and moving forward you'll be fine.