Ashley's Forum Posts

  • Presumably, raids is null or undefined, so you cannot use raids.filter. Make sure it's actually an array. This is just normal use of JavaScript, it has nothing to do with Construct specifically.

  • It should already make WebAPKs. That's just an internal detail of the "add to home screen" feature.

  • "On start of layout" is a trigger. It does not run during the normal execution of events.

  • From the page I linked to:

    A given directive in a request does not mean the same directive should be in the response.

    You have to put the header in the response, not the request.

    • Post link icon

    The issue of the payment model has been discussed to death already, and this looks about to get personal (previous post deleted), so closing.

  • Yes, by far the easiest way is a HTML5 export (which also works offline).

    NW.js for Linux is build for the x86 chip architecture (as used by most PCs), but the Raspberry Pi has an ARM chip. So NW.js would have to be recompiled for the ARM architecture. That is a big and very complex project, and I don't know if anyone has tried that yet.

  • No, you'll have to use JavaScript code to do this I'm afraid. Construct's event system doesn't cover this kind of use case.

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads

  • Thanks for the feedback and I'm glad you're enjoying C3!

    Nevertheless, I'm very sorry that you still haven't corrected the problems due to the canvas

    I'm not sure what you're referring to here. Could you explain some more? Obviously we'd like to correct any problems where we can, but some things are fundamental limitations or otherwise out of our control.

  • The iframe is part of the parent page. If the iframe page is on the same origin (i.e. domain), it should be able to remove itself from the parent page via accessing its parent window. However if it's on a different origin it is not allowed to do that for security reasons. Instead you could use postMessage in JavaScript to get the iframe to tell the parent page to remove the iframe.

  • If your game did not pause at all, it would continue to waste battery and system resources, resulting in alienated users, poor reviews, and then eventually the browser or OS would kill it anyway to save the user. So it's a pretty good thing that it does pause automatically.

    • Post link icon

    This has been discussed to death already, and the short version is we have no plans to change this right now.

    Something I do want to point out though is I think a lot of people don't realise that I was the sole developer on Construct 2. Being the only developer working for years with a one-time payment model while people are crying out for more features, it became pretty obvious there was no way we could have done a fraction of what everyone wanted under the previous model. With Construct 3 we were able to hire more developers, making it possible to do way more, such as a completely rewritten runtime with vastly improved performance, an ongoing mobile app build service, timelines, scripting, a big batch of new plugins and behaviors, and loads more. If you're looking at those things and wishing you could upgrade, then I think you should recognize most of that would not exist at all if we had stuck to the old model.

  • The main cause of the app crashing is an incorrect configuration. (Unfortunately Google's code does not elegantly handle such misconfigured cases and tends to just crash the app.) Make sure everything is set up correctly as described in the documentation.

  • You can save your project as a folder and then use that with existing version control tools like SVN and Git.

  • It seems there was an oversight and the project property for "Viewport fit" was missing from the manual, so I just added it.

    In short you should only need to change the viewport fit to "cover". You may also need to adjust the game to fit different screen sizes too.

  • You probably need to adjust the Cache-Control HTTP header on the server response.