programming student but game development newbie

Started by
4 comments, last by Steve Guardiola 11 years, 9 months ago
Hi all, been having some problem lately and hitting the same wall over and over again, i know most of the basic for c++ and Java, however have not developed any game yet.

This is the problem i am having, im not sure how exactly how to start programming games myself, i have tried reading tutorials and books, but every time i try to start my own work, i get frozen and dont know how to start.

So lately i have begun drawing and writing all my ideas and drawings in a notebook, is mostly how the game will look and some level and interface design.

But now i want to learn how i could design the programming process, i have also read Object oriented programming books, so i am trying to think of classes and variables i might need, but because of my low knowledge of gaming program dont know allot of it.

So i want to know is there a process, flow chart, some kind of design that could help me write what the code will contain, then when i type it in i can figure out the process on how the procedure of the class will be done.

At the moment i am obsess with isometric game design, and there isn't allot on this topic.


Just wanted to get it off my chest, i noticed that i come up with better ideas and learn more when i share my frustration or talk about it.
Advertisement

So i want to know is there a process, flow chart, some kind of design that could help me write what the code will contain, then when i type it in i can figure out the process on how the procedure of the class will be done.

It seems you are stuck on the design process of the game code? Have you learned UML? This is typically how programmers develop a high level view of their game. It's not necessarily required, but it will save you a lot of hassle if you do so. So you should probably try learning that.

Another suggestion I can offer is reading about game design, check out the book, A Theory of Fun for Game Design.

[quote name='stevega' timestamp='1340599924' post='4952561']
So i want to know is there a process, flow chart, some kind of design that could help me write what the code will contain, then when i type it in i can figure out the process on how the procedure of the class will be done.

It seems you are stuck on the design process of the game code? Have you learned UML? This is typically how programmers develop a high level view of their game. It's not necessarily required, but it will save you a lot of hassle if you do so. So you should probably try learning that.

Another suggestion I can offer is reading about game design, check out the book, A Theory of Fun for Game Design.
[/quote]

UML, thats exactly what i was looking for, i forgot to add that i have read the art of game design and currently reading Level up!, but UML is exactly what i was looking for, something i could learn and write it on the notebook and then when i put it on the IDE i just need to add what i wrote in whatever language i would be working on.
I'm in a similar position. Right now I'm going to school for Computer Science and I love to program, but I've just started learning game development.

If you learn well visually, check out these videos on youtube. I don't think the owner of the channel has uploaded a video in a while, but I really like his playlists for gamedev.

Those should get you started making your first game if you want to start with simple 2d stuff. I've also wrote an article on my blog about my first game and what I learned from making it. You can click the link in my sig if you care to check it out.

Good luck
Just start small. Guess the number text game, then some Pong, etc.

You are frozen, because pretty much everything is new to you, from the structure of the whole game to its details. That's why you have to start small, so you only have to tackle with less problems at a time.

I think the best way to get over the frozen state is to struggle yourself through the whole process of a very simple game. And forget the isometric for some time. That is way too much at once, and the problem is that you need to implement a bit of every aspect of an isometric game (rendering, fairly complex game logic, loading, content handling, I can't even name all) to have something to test and play with.

And an opinion: forget about object oriented design for starting. It's just one approach of software design. And it's a total overkill for a very small game (IMVHO), with which you should start. IMHO OOD and learning to make games is too much at once (by learning I mean getting over that "frozen" state). We can see this all the time here. The poster is struggling with classes in a game that has about 3 things in total, when a simple 30 line program would be perfectly enough.
ty so much for your opinions , greatly appreciated.

This topic is closed to new replies.

Advertisement