Morning all - I've just read the blog post about NW.js in construct 3 getting updated, particularly to fix the Mac permissions problem. That's great news - as a C2 user, it's an impending problem I've been trying to figure a way around.

Ashley wrote:Construct 2 is still going to be actively maintained, but mainly for bug fixes and maintenance. In general, any new features or major changes will only be made in Construct 3.

Hey, thanks for the reply!

I think I understand — the Mac export problem doesn't fall under maintenance, so won't be addressed.

Not a criticism, but C2 is advertised as being able to publish to Mac, and it's part of the reason I bought it. But I just can't get Mac NW.js working with the currently prescribed method. And in turn, I can't bring my game to that platform.

So if there's any way to get NW.js -> Mac on the to-do list for C2, it'd be really helpful. Or some kind of step-by-step tutorial for the "open on windows" permissions workaround — it's entirely possible I'm just not doing it right.

Ashley wrote:Construct 2 is still going to be actively maintained, but mainly for bug fixes and maintenance. In general, any new features or major changes will only be made in Construct 3.

Hey, thanks for the reply!

I think I understand — the Mac export problem doesn't fall under maintenance, so won't be addressed.

Not a criticism, but C2 is advertised as being able to publish to Mac, and it's part of the reason I bought it. But I just can't get Mac NW.js working with the currently prescribed method. And in turn, I can't bring my game to that platform.

So if there's any way to get NW.js -> Mac on the to-do list for C2, it'd be really helpful. Or some kind of step-by-step tutorial for the "open on windows" permissions workaround — it's entirely possible I'm just not doing it right.

I did not know that there is a problem with NW.js for Mac, that is a blow to me because I already have 50% (too much to change engine) of my game and I want it to work on Mac.On the other hand I have not investigated that thread and maybe there is some solution, I hope.

"On Mac OS X, there are actually several files inside the app package that need to be executable. The easiest way to preserve the permissions is to copy the exported project using OS X instead of Windows."

For people who don't have that option, Is there a list somewhere of the files that need to have their permissions set?