0 Favourites

using Construct 2 as a Reference code to Game Maker?

  • is that even practical to use Construct 2 as a Reference for Game Maker

    like translating construct 2 code into game maker manually?

  • is that even practical to use Construct 2 as a Reference for Game Maker

    like translating construct 2 code into game maker manually?

    You're asking on the Construct 2 official forum on how to convert to GameMaker? Really?

    This is something that should be directed to the Gamemaker forums.

  • If you mean by "reference": make prototypes quickly and then re-implement them with other engines: yes, that works well. I do that with Unity.

    If you mean some sort of automated conversion: nope.

    You also have to be super careful to not try and re-implement stuff the same way as in the other engine, that never works. You have to respect each product's philosophy and optimization procedures.

  • is that even practical to use Construct 2 as a Reference for Game Maker

    like translating construct 2 code into game maker manually?

    That seems to be impossible unless GameMaker decides to program/reprogram their engine that can be able to convert C2 project files into their own but that is unlikely considering that the 2 engines have the same purpose, to make 2D games and for that to happen Scirra will have to share their program code so that GameMaker Team will have a blueprint of the idea but in the marketing world, no one would share their program code or product design to a competition.

  • Construct 3

    Buy Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Buy Now Construct 3 users don't see these ads
  • The very few reasons to even attempt that would be duplication of code in other games to a different game engine for deniability of theft.

    And that's not very nice, to say the least.

    If you plan to start afresh your own game in a different game engine, it is always wiser to code back from scratch your entire game so you can maintain and understand the engine characteristics.

    After all, all programming logic and concept works pretty much the same.

  • by Reference i mean Referencing the Construct 2 code like setting up the foundations so that when i make the game on Game Maker i Have a Code to Look upon when i get lost

  • How well do you know Game Maker ? And how well do you know Construct ?

  • i know you can ... or you could import scenes assets from GM to C2 but im pretty sure its not possible the other way around.

    but i think never was the code translated. unless you try manually replicate it in the GM language.

  • C2 and GM are different, so you might easily get stuck because some code works with C2, but doesn't work with GM.

    Also, why can't you just make the game with C2?

  • by Reference i mean Referencing the Construct 2 code like setting up the foundations so that when i make the game on Game Maker i Have a Code to Look upon when i get lost

    That actually doesn't make sense just choose one game engine and stick to it. Gamemaker and Construct2 are totally different. Game Maker uses a condensed version of C++ and Construct2 uses javascript.

  • You can use any program/coding language as a reference for anything else. It'll never be one to one because of syntax differences but the logic/algorithm is the same.

  • You can use any program/coding language as a reference for anything else. It'll never be one to one because of syntax differences but the logic/algorithm is the same.

    We use event we don't actually code until we get into making larger games. It doesn't make sense to go back and forth between tools, the developer should just pick one.

  • Call events what you will, but they are the way to code the logic in C2. Regardless you can still use a c2 project as a reference to create the same thing in another tool.

  • i should stick to Construct 2 for now

  • I agree with R0J0hound and PixelPower . While you can carry your logic between languages and engines, you should not develop your game twice. If you want to use 2 engines, I'd say creating a prototype in one and the full game in the other is the preferable approach. But IMHO it's better to learn one engine to the professional level if it fits your needs.

Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)