Here's the updated version!
Test build (Launcher.exe and Game.exe is in here):
The program consists of two files. Launcher.exe and Game.exe. Launcher.exe is the UI part. This is where you choose your resolution and window/fullscreen (which doesn't work atm ). Game.exe reads the resolution set in Launcher.exe and switches to it before executing nw.exe. So you don't need to run the launcher itself every time you want to run your game.
Both Launcher.exe and Game.exe will create a new folder "cfg" inside your build folder and fill it with some txt files if they don't exist already. You can edit these to configure the button texts, window title text, and the resolutions you want to make available to the user. Launcher.exe will check the resolutions listed in 'res.cfg' against the ones available to the system you're running on, so it'll only list valid resolutions (as reported by the system).
'ui.cfg' is where you can set the texts displayed in Launcher.exe to your liking. Pretty straightforward stuff. At the bottom of 'ui.cfg' you'll see the line 'Game.exe'. Set that to whatever you want to rename Game.exe to to point Launcher.exe in the right direction.
Please let me know how it works out for ya and what system you're running on
In 'launch.cfg' you'll see this:
nw.exe (change this if you want to call nw.exe something else)
1920 (current resolution as set by Launcher.exe)
2.50000000 (delay in seconds before switching resolution. Tweak to suit your game's loading time)
0.000000000 (time period in seconds to display a black screen while loading. The nw.js game window will display on top of it so you can safely leave it high if you want)