Jump to content

  • Log In with Google      Sign In   
  • Create Account


Member Since 11 Mar 2013
Offline Last Active May 09 2013 09:52 PM

Posts I've Made

In Topic: I want to make a 2D game engine! Where do I start?

09 April 2013 - 04:34 PM

If your goal is making a 2D game engine, but no game, then cool. But if your goal is making a 2D game, then make the game, not an engine. Engines aren't really used for 2D games much, and focusing on the engine and over-engineering it leaves you without a finished playable project at the end.


Regardless, it doesn't matter what language you use, or what libraries. Use the language you already know best, and the libraries you are already familiar with, and work with those. Unless your goal is learning a new language or a new library, and not completing a game. wink.png


Is your goal: (pick one)

A) Making a game

B) Making a game engine without a game

C) Learning a new programming language

D) None of the above


If A, let us know what language you already are most familiar with, and someone can recommend a good 2D graphics library for that language.

If B, let us know what language you already are most familiar with, and someone can recommend a good 2D graphics library for that language and some architectural articles or books.

If C, learn Pythonsmile.png

If D, could you elaborate on your actual 1 (one) primary goal for this project?


Note: There's nothing wrong with wanting to make a game engine as a goal - it's really fun to do - just realize it comes at the expense of actually making a game.

Many beginners think they need an engine to make a game, but that's not true, and they end up tripping over their 'engine' and failing to produce a game. This is the only point I'm trying to get across. The idea of an engine is appealing, but misleading, to game developers.


Engines come out of games before games come out of engines. Engines are the reusable components of pre-existing games wrapped up in a consistent and easier to use interface for future games - but focusing on the engine without a solid game in mind leads to an engine that isn't usable for any real game with heavy alterations - unless a developer has already made a half-dozen real games, in which case the real-world requirements of engines are already in his mind.

Making an engine instead of a game is putting the cart before the horse - from finished games come the knowledge and re-usable pieces to make engines.

Okay I'll tell you what I know. So I know: javascript, C++, python, C and ruby. And I'm more familiar with javascript, C++ and python. My main goal is to make a game engine, which is b. cause I mainly wanna learn how a program can make another program especially how a game engine can make a game. I only know 2 library pygame and SFML for c++.

In Topic: Hey I've learned C++ and SFML, but I can't find a book or tutorial

13 March 2013 - 01:26 PM

Well Thank you everyone! I might go well with this! I'm gonna take a look to this tutorial and scratch on a sheet of paper many ways to do collision or whatever until I found one which make sens!

In Topic: Where should I start with game development?

11 March 2013 - 10:07 PM

this can be helpful:



If you take an engine , make sure to read the license!