Hello there, I'm inexperienced in making games and have been making unsuccessful attempts at for 3 years yet I still feel extremely lost in it. What should I do now?

3 minutes ago, Lunari said:

Hello there, I'm inexperienced in making games and have been making unsuccessful attempts at for 3 years yet I still feel extremely lost in it. What should I do now?

Could you share you experience in the last 3 years? How far did you get? What did you learn? What did you use in terms of languages, libraries, APIs, ect...?

Just now, Rutin said:

Could you share you experience in the last 3 years? How far did you get? What did you learn? What did you use in terms of languages, libraries, APIs, ect...?

I learned about how to use Unity and Unreal game engine(Wish that I can use Unreal instead of Unity but my shabby laptop won't allow it).

I know a moderate amount of c#and a little bit of c++.

I can't prototype a game at all, I've come close to it and currently I'm trying to make a prototype of a roguelike but my studies in shool have been in the way of it.

5 hours ago, Lunari said:

I'm trying to make a prototype of a roguelike

Unity have made a fairly decent tutorial series for a Roguelike here https://unity3d.com/learn/tutorials/s/2d-roguelike-tutorial this might be a good place to start with?

When you say "I can't prototype a game at all" what is going wrong? What's stopping you from finishing a prototype?

7 hours ago, Lunari said:

I can't prototype a game at all, I've come close to it and currently I'm trying to make a prototype of a roguelike but my studies in shool have been in the way of it.

This would seem more like a game design issue and less in your ability to program at this stage. I would suggest looking into making a design document with your projects. You can start with something more simple. The key here is to have a guide to follow, essentially a blueprint for your game to give you direction.

Aside from this, if you haven't made any smaller games you need to start at the basics. 2D/3D Pong, Breakout, Pac-Man, ect...

I'm not sure if you're doing this, but personally I cannot code a game by flying by the seat of my pants in a productive way. I either change things all the time, or waste a lot of time thinking on what is next. If I write my plan in a design document even at its simplest form, my productivity is much greater, and my clarity on what I'm trying to achieve is also more apparent.

3 minutes ago, Rutin said:

change things all the time, or waste a lot of time thinking on what is next.

? Not alone! But yeah: 

4 minutes ago, Rutin said:

If I write my plan in a design document even at its simplest form, my productivity is much greater, and my clarity on what I'm trying to achieve is also more apparent.

This ^^  Then you just need to be disciplined enough to stick to your document  

8 hours ago, CyberFlash said:

Unity have made a fairly decent tutorial series for a Roguelike here https://unity3d.com/learn/tutorials/s/2d-roguelike-tutorial this might be a good place to start with?

When you say "I can't prototype a game at all" what is going wrong? What's stopping you from finishing a prototype?

I usually get stuck in coding the game or I just lose interest.

6 hours ago, Rutin said:

This would seem more like a game design issue and less in your ability to program at this stage. I would suggest looking into making a design document with your projects. You can start with something more simple. The key here is to have a guide to follow, essentially a blueprint for your game to give you direction.

 

Huh, never heard of a design document before. Thanks!

8 minutes ago, Lunari said:

usually get stuck in coding the game or I just lose interest.

So the biggest problem and thus question is "Why do you want to make games?" Losing motivation is something that seems to get everyone from time to time so I suppose that's a personal thing to address but if you really want to make games, what makes you lose interest? Maybe there's a different side of game making you're interested in and would need to try to team up with someone?

As for getting stuck with the code, I'd recommend following a tutorial from beginning to end and just forget about the game it/you are going to be making through it and then focus on the code and understanding what the guy is say beyond 'write this here' now that moves, write that there, now that moves, kinda thing. You wanna try to understand why it works and then try doing it yourself without a tutorial until you no longer get stuck in coding it. 

8 minutes ago, CyberFlash said:

You wanna try to understand why it works and then try doing it yourself without a tutorial until you no longer get stuck in coding it. 

This is a very good point.  

20 minutes ago, Lunari said:

Huh, never heard of a design document before. Thanks!

Look into it. Think about building a house as an example... You wouldn't just grab random materials and start hammering away unless it's a plywood shak in the boonies. You would draft up a plan before starting so when you actual begin to gather resources and work, everything goes together more smoothly, and you have direction. Your design document is the blueprint for your game.  

6 hours ago, Rutin said:

boonies

Very sorry for posting off topic but why can't you receive messages?