I have to work with multiple game engines, like

  • Cocos2d
  • Unity3d
  • Galaxy

While working with multiple game engines, what practices should I follow?

For instance, we made a game with Cocos2d and released it on the AppStore. Now we want to port it to other platforms using Unity.

What would be the course of actions to follow?

  • 2
    \$\begingroup\$ Could you be a bit more specific? Are you having specific problems that need to be solved? Are you using these engines in one project or do you happen to have multiple projects using one engine each? \$\endgroup\$
    – mrbinary
    Oct 4 '12 at 12:04
  • 1
    \$\begingroup\$ Do you mean multiple game engines for one game? \$\endgroup\$ Oct 4 '12 at 12:08
  • \$\begingroup\$ @mrbinary, I have edited my question as your criteria \$\endgroup\$ Oct 4 '12 at 12:09
  • 1
    \$\begingroup\$ OK so this is more about porting a game to a new engine. I think you should rework your title a bit. \$\endgroup\$ Oct 4 '12 at 12:11
  • 1
    \$\begingroup\$ I think this is a bit too broad for the site. I can't imagine there is a correct answer to this question. \$\endgroup\$
    – House
    Oct 4 '12 at 16:31

I'd suggest finding a common denominator of these engines. That is, if you will use a physics engine, find one that has ports already made for other environments you use. If you use a MVC approach, use a MVC framework that is either ported to other environments (pureMVC is quite popular) or that works in a similar way as other MVC frameworks you can use in other environments.

In the end it is best to decouple view components specific to game engine from rest of the code, so when porting the game you can focus on a specific part of the source.

  • 3
    \$\begingroup\$ Wow, that was quick. Better untick this as an answer, this will motivate others to answer too. \$\endgroup\$ Oct 4 '12 at 12:25
  • \$\begingroup\$ Okay. I have untick the answer. I want more answers. After that i will choose the best answer. \$\endgroup\$ Oct 4 '12 at 13:12
  • \$\begingroup\$ -1 MVC will not help at all, if you port between different languages, as asker does. Besides MVC is an anti pattern when it comes to games, particularily on low end devices \$\endgroup\$ Oct 4 '12 at 19:02
  • \$\begingroup\$ Hello @MaikSemder, I didn't recommend to use MVC, I just pointed out that it would be easier to port actionscript game using pureMVC to a javascript game using pureMVC, than porting robotlegs to pureMVC and than restructuring whole code not to use injector class. I will not go into a religious war about patterns and anti-patterns, though. \$\endgroup\$ Oct 4 '12 at 19:32

Not the answer you're looking for? Browse other questions tagged or ask your own question.