Jump to content
  • Advertisement

Archived

This topic is now archived and is closed to further replies.

Chicken or the Egg?

This topic is 5826 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

here''s somethen ive been tossing around in my head the past few weeks... is it better to write an engine before making a game, so that you know better how engines work, how to maintain/change/improve them, or is it better to use a premade engine to make a game so you know how a game works with an engine? the reason i named the topic "Chicken or Egg?" is because it reminds me of that question, which came first, the chicken or the egg. so heres my question, what SHOULD come first, the engine or the game and why? i haven''t been able to make a decision and i keep waivering back and forth between them.

Share this post


Link to post
Share on other sites
Advertisement
I think you should first design the game. After you have finished designing the game, then you should know what you need to implement it. That would be the point where you either look for an existing engine that supports the functionality you need, or create one yourself.

Share this post


Link to post
Share on other sites
Guest Anonymous Poster
I would say the game should come first. While you develop the game, try to make as much of the code modular and reusable as possible. Then when you''ve finished, identify the ''engine'' in your code and separate it from the game specific code. In theory you''ll be able to use it again for other games (you may be limited to particular types of games of course).

Share this post


Link to post
Share on other sites

  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

Participate in the game development conversation and more when you create an account on GameDev.net!

Sign me up!