Different Web Broswer

Part of this is ignorance on my part, but I have my game well underway, and noticed something strange when I exported to the node-webkit. I looked a bit online and found to test the game on multiple browsers, so I did.

Can someone explain to me why my game works perfectly in the browser I've been testing in, but the second I switch to a different browser, half of my events just flat out don't work? I've been using palemoon, but trying internet explorer, simple things such as changing a variable isn't working. I'm now getting the game to crash at certain points. Is it not possible to run large games using Construct 2 because of this issue?

It's most likely all your events are working properly. Perhaps you depend on some specific browser feature that isn't supported everywhere. You must test across browsers from the very start, because it's now very difficult to track down the cause of the issue or offer any help to you. If you were testing properly from the start, you'd probably know roughly which change caused the issues.

So I was able to fix everything in every browser, however some things are now broken when I export to Node-Webkit.

Sorry to be pesky about this, but I've checked my code quite a few times, and I'm still having an issue. Basically I'm trying to save a few arrays with both numbers and text.

I have 2 separate arrays, one giving me an issue and not saving the text, and the other works perfectly. The codes are the EXACT SAME aside from being a different array and I've now tested them and they work on Chrome, IE, Firefox, and Palemoon, but when I export to Node-Webkit, only one of the arrays saves the data appropriately.

Have there been issues like this using node-webkit?

Thanks!

It's hard to help unless you can share a minimal .capx showing the issue in isolation.

ome6a1717 Have you tried declaring your text as strings? i.e.

str(data)

Clearly declaring the data type often fixes a few idiosyncrasies across browsers.

Also check you're not setting your variables incorrectly as text or number, which can be an easy mistake to make.

Nathan you are a savior! Just adding str for the text array numbers seem to have fixed it. It's just strange that it worked in every browser until I exported it to a node-webkit.

Just curious, Ashley; what browser does the node-webkit use? Or is it based on which one you currently have set in your project?

Thanks guys!

Node-webkit is chromium based.

I do not know why your strings were not being recognized, usually having ""s around a data entry signifies it as a string and you don't need to announce it.

My strings weren't exactly Set Array to "text", it was set Array to Sprite.AnimationName. That could have been causing the issue.

Node-webkit is based on Chromium, effectively the same browser as Chrome. So it is usually very strange to have differences between Chrome and node-webkit.