>
> > The NW.js exporters could indeed be a lot better. Adding the steam dlls and the txt to every one of the builds is annoying and time consuming when testing. I know Scirra can't just distribute the dlls but I'd love if I could point my steamworks folder to Construct 2, so it could get the dlls from there and use the in the exported games. Also the appid txt file.
> >
> It would be nice if we could set up a folder in the export window for files like this and during packaging, C2 would copy it's content to the exported folder automatically.
>
I thought you could it already by just dumping whatever you want in NWjsForC2 win32 folder or any folder inside.
Anytime you export the NWJS version, anything inside will be included in the final release.
Including the folder and files setup you made beforehand.
It's true that you can go to NWjsForC2 folder and add anything there but the steam dlls must be inside the package.nw zip file, and it's C2 itself that zips the game files into it so there's no way of doing that.. so each time you have to test your game on Steam, you have to manually add the dlls to each OS' package.nw file
Also keep in mind that, if you also make DRM-free versions of your game (which is my case), even if you could add the steam dll to the NWjsForC2 folder, you'd have to go back and remove it manually anyway.