How JavaScript beats GameMaker Language (GML)

You're viewing a single comment in a conversation. View all the comments
  • 3 Comments

  • Order by
  • I agree 3rd party isn't all bad and it's very necessary, but in Construct's case we have to rely on it to get our games out in basically any platform that's not web.

    My point is that no matter the performance boost you can have with JS, it makes no difference if I my games keep breaking because of old NWjs bugs, or if I can't release anything on consoles. In both these cases, this doesn't happen with GameMaker.

    Like I said I absolutely love Construct, but the minute we have to release something you start to notice how hard it is compared to any other engine out there - specially GameMaker.

      • [-] [+]
      • 1
      • Ashley's avatar
      • Ashley
      • Construct Team Founder
      • 1 points
      • (1 child)

      Like any platform NW.js has some bugs but usually they get fixed in updates. And if you stay on the same version, nothing actually changes so it shouldn't suddenly break overnight. Are there any active issues with the latest NW.js version?

      • Well, since it's been asked...

        For me, biggest NW.js export issues are incompatibility with OBS (very popular software to record footages from the game) and things like steam overlay.