Hi, AthenaOfDelphi, you replied at same time as me
My engine has been free/open source for almost two years now. And I already said in this topic, if there is no documentation for a project, why not ask the developer for documentation instead of reinventing the wheel?
Btw, Castle has all documentation you need, and mine too, just not online, if anyone would ask I could send it by email.
If you want to make games, please don't write engines. Otherwise you won't be making a game soon.
I'm not sure what kind of games you want to make, but really, making a engine is not the right path.
Make an engine only if you want to learn about this kind of stuff, otherwise pick up an existing solution.
And if you want to learn, and if you don't know much about this kind of stuff yet, take into consideration that this would be years of learning, not months. Just modern graphics programming has enough material to keep you occupied for years, and a game engine is more than just graphics.
I have no doubt that this project can be done, given enough time.
But of course, it is time spent that could have been spent making games with existing solutions.
Or contributing to an existing solution.
Think, in 2015 you can either have:
- An incomplete rudimentar engine, not suitable for serious projects
- Or a game made with current solutions
- Or existing solutions extended with advanced stuff, ready to make advanced stuff
Btw, this link is a good read for anyone who is interested in making games
http://scientificninja.com/blog/write-games-not-engines
Bookmarks