Ashley's Forum Posts

  • I deleted 3 other topics you made because they looked like advertising spam. See the Forum & Community guidelines and be warned if you make too many posts that look like spam you may be banned.

  • The message is stating both WebAssembly and WebGL (at any version) are not supported. It's because that version of KaiOS is based on Firefox 48 from 2016, which is now just too old to run modern web content. The message is correct that the device needs a software update to be able to run the content. Unfortunately whether or not you get one from the device manufacturer is another matter...

  • You can't import in scripts in event sheets. (Those are really inside functions, and the JavaScript language disallows import and export inside functions.) The syntax is also wrong for the module specifier (it should be "./brain.js").

    This is what the 'Imports for events' script is for - anything you import there will be accessible by scripts in event sheets. However the script you've included does not actually export anything (it uses a different module system), so you'll need to load it differently anyway.

  • Import them as project files and then load them with AJAX.

  • If a device only supports WebGL 1, Construct will just use WebGL 1. WebGL 2 support is optional. So you shouldn't need to change anything.

  • I'm not sure I understand. Any script you import to the main script is already automatically loaded.

  • I would advise to as usual file an issue following all the guidelines, as we generally need all that information to be able to investigate or help.

  • I don't think this is anything specific to Construct - you can just use the usual browser APIs for this. The code below will create a canvas element and insert it to the document. You'll probably need to use CSS to position it. 

    const canvas = document.createElement("canvas");
canvas.width = 300;
canvas.height = 200;
document.body.appendChild(canvas);

  • Currently worker mode "auto" will only switch to DOM mode if you use any script file or script block in an event sheet anywhere in your project. You can still change worker mode to "Yes" or "No" to force it to use one or the other instead of using "auto".

  • Try uninstalling the app, rebooting the device, then re-testing it. I think iOS caches app icons a bit too keenly and it may have remembered an old icon before you changed it.

  • I appreciate it's important to have lots of good documentation on coding in JavaScript for newcomers and more would be useful. The main limiting factor is just that good quality documentation is time consuming to write. The current in-progress "Learn JavaScript in Construct" tutorial series is a months-long project, and there's probably several other similar tutorial series we could potentially write on coding various aspects of different games. We'll work on it, but it will take time. In the mean time it would be great if any other users who've learned some useful things about JavaScript coding could share what they've learned in the tutorials system - part of the reason it's there is so everyone can share their own tips, tricks and guides, both for the event sheets and coding.

  • No, there are no new coding standards in iOS 15. Apple broke iOS. They do it all the time - unfortunately their software quality is not what you'd expect from such a large company.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • As of cordova-android 10.0.0+, builds are already AAB by default. All the other details should still be OK, I don't think the CLI changes that much. If you find anything specific that's incorrect please do let me know.

  • The "Learn JavaScript in Construct" tutorial is still a work in progress - there are several more parts to come and it will cover more of the things you've mentioned.

    The guide also already covers some things like how => is another syntax for functions. The most recent part does also cover (albeit in brief) how addEventListener is a standard way to listen for events in the JavaScript ecosystem: for example document.addEventListener("click", func) means func will be called every time the user clicks anywhere in the page.

    This is all the usual way things are done with JavaScript, including in browsers and other environments like node.js. So while there may be a learning curve as many of the patterns and APIs will differ from GameMaker, you're learning the real-world patterns used widely in industry, which is a really useful transferable skill.

    Further many of these patterns are very powerful and allow for complex and sophisticated code that can make things easy that are currently awkward in GML. For example async functions make it far, far easier to write async code. However that does mean, naturally, learning about how async functions work in JavaScript, but again this is all industry standard stuff so you'll be learning real-world programming skills, rather than one tool's specific way of doing things.

  • You can use the web export and publish it to the Microsoft Store using PWABuilder. That's what we did for Construct 3 itself.