Should I or not?

[DetectiveRawr]

Should I start making a game after learning C++ as a beginner video game programmer? or Learn both of them during the same time? I did started out small by creating 2D games on game maker yoyogame.com but I didn't quite reach to the scripting part. Some people recommand me to start a game with SFML + MVSC++ but the complier,MVSC, is complicated for a beginner!? so I started code::blocks instead.

[naraku9333]

You can use SFML with code blocks.

[DetectiveRawr]

Well that didn't answer my question lol.

[naraku9333]

There is no real answer, some say start with console until you are very comfortable with programming concepts, some say jump right in. It depends more on you, check out an SFML tutorial, if you feel like you can understand it then go for it.

[zb0S216C]

DetectiveRawr wrote:

"Should I start making a game after learning C++ as a beginner video game programmer?"

You'll never finish learning C++; 20 years can go by and you'll still not know everything. I recommend that you get to the point where you're comfortable with:

- Pointers & references
- Classes
- Inheritance
- I/O

When you're comfortable with them, start learning a graphics library, such as SMFL^[1] or Allegro^[2]. When you're comfortable with the graphics library, you can start to develop your game.

DetectiveRawr wrote:

"I did started out small by creating 2D games on game maker yoyogame.com but I didn't quite reach to the scripting part."

That's experience; use it.

DetectiveRawr wrote:

"Some people recommand me to start a game with SFML + MVSC++ but the complier,MVSC, is complicated for a beginner!? so I started code::blocks instead."

The Visual C++ IDE is considered a steep learning curve for beginners. Code::Blocks, on the other hand, is much easier to use, and it's cross-platform.

References:
^[1] http://www.sfml-dev.org/
^[2] http://alleg.sourceforge.net/

_Wazzak

[DetectiveRawr]

Ok now this is what I'm looking for, ty.

[DetectiveRawr]

You'll never finish learning C++; 20 years can go by and you'll still not know everything. I recommend that you get to the point where you're comfortable with:

- Pointers & references
- Classes
- Inheritance
- I/O

Only those 4?

[Moschops]

If you do those, you won't need to ask someone else what to do next. You'll pick something yourself.

[DetectiveRawr]

ok I'll note those 4 as the top 4 important things I'll focus on.