This is due to a half-way spec change in Chrome 47. It's already fixed in Canary which means a future version of Chrome will work again, but I added a workaround for the next build as well.
This is a bug in NW.js: https://github.com/nwjs/nw.js/issues/4052
Closing this report as it needs to be fixed in NW.js.
Thanks, should be fixed in the next build.
Should be fixed in the next build. Because of the way Firefox handles this, in this case every attempt to access local storage will simply trigger "on error". At least it avoids the game crashing.
Closing, please follow the bug report guidelines and submit a minimal .capx only.
Closing, this is not a bug, probably just NAT issues. See the first multiplayer tutorial for more information.
Closing, please follow the bug report guidelines.
Closing, please follow the bug report guidelines and include a .capx.
Closing, please follow the bug report guidelines. If you just need general help using C2, please post to the "How do I" forum, the bugs forum is for reporting defects in Construct 2.
Closing, this is normally because you did not upload the project correctly, rather than any bug in C2. Check the browser error console.
Develop games in your browser. Powerful, performant & highly capable.
Closing, please make sure you use r217+ for the latest NW.js versions.
I think this feature is simply currently missing in the 0.13 branch (they're still alphas). Closing, this should be fixed by future NW.js updates.
Member since 21 May, 2007 Last online 27 Oct, 2026
The official blog for all things Construct and Scirra run by our employees!
Wider technology issues from Ashley's perspective.