[quote:2gcxd6eu]on Windows the engine's executable file must have the name nw.exe for addons to work
Needed for modules containing C/C++ addons because they use parts of the engine to sustain their execution. (greenworks/setam4c2/robotjs....)
I've noticed that Ashley mentions in the greenwork plugin post that the game's exe must be named nw.exe for it to work, I also notice you didn't write anything about it, my game and steam overlay seems to work fine for me with a different exe name, but I'm not sure what was the original problem that required this action, can you shade some light on the subject?
I see, but it also says at the top that some of these issues only apply to version 0.12 and lower, we're on version 0.19.4 already, so that might not be an issue anymore. My point is that my game runs, steam overlay is accessible, achievements are being registered and pop is shown, so unless I'm missing something, I don't see any problem.
I think that Lof is onto something here, could it really be that more recent versions don't have this requirement anymore?
So far I've always been assuming the same because of the given information from the (outdated?) documentation about the use of addons.
Either MadSpy and/or Ashley, I would like to request a statement about this.
Is it still required to use "nw.exe" as the application name or are you guys perhaps "outdated" about the latest requirements of NW.js + Addons?
New Docs | Old Docs | Native Modules