The NW.js version of the editor is being retired
Update May 2022: Historically we distributed files that allowed running Construct 3 in NW.js. The download files for this were provided in this post. However support for this is being removed. Please switch to using Construct in the browser at editor.construct.net instead.
For testing NW.js features in your project, you can still use the Remote Preview for NW.js tool below.
All other NW.js features are still supported, such as exporting your projects with NW.js. Only running the editor in NW.js is being retired.
In the past browsers lacked many desktop-style features like accessing local files, integrating with external image editors, and associating with the .c3p file extension. Over time pretty much all of this has now come to Chromium-based browsers. For example since Chrome 86 local file & folder saves are now supported using the Chrome browser. Other features like copying and pasting images, and as of Chrome 102 support for associating the .c3p file extension, mean that there are basically no good reasons left to use Construct in NW.js.
Meanwhile we have a lot of complicated code to support some NW.js features, there have historically been lots of difficult bugs that only happen in NW.js and don't happen in browsers, the NW.js editor has been effectively unmaintained for some time now, and only a very small number of Construct users still use the NW.js editor. Therefore we have decided to retire the NW.js editor and only support Construct in the browser.
Using Construct in NW.js is now deprecated. Support will be removed in future. You should switch to using Construct in the browser now to avoid ending up with broken software later on.
As of Construct 3 r296+, a warning message will appear when using the editor in NW.js indicating that support will be dropped.
The code for NW.js specific editor features will be removed in the next release cycle (the first beta release after the next stable release), around June or July. Beyond that point we cannot guarantee that the editor will keep running at all in NW.js: it may stop working at any time and we will not fix any issues or provide any support for it.
Remote Preview for NW.js
This tool allows you to test your project with NW.js features when using the editor in the browser. Download it here: nwjs-remote-preview-2.zip
Follow these instructions to use it:
- Download the file linked above.
- Download the version of NW.js you want to use from nwjs.io/downloads.
Note: We recommend downloading the 'SDK' version because it provides the browser dev tools, which are useful for development. The 'Normal' version does not include dev tools.
- Extract both the package file and a version of NW.js to the same folder (so both nw.exe and package.json are the same folder).
- Run nw.exe. You may need to approve a security prompt, or wait for an antivirus scan.
Remote Preview for NW.js loads preview.construct.net in NW.js. This works the same as it does in the Chrome browser, but the features of the NW.js object will work since it's running in NW.js. You can start a Remote Preview in the editor, and then load it in Remote Preview for NW.js.