Ashley's Forum Posts

  • All my old games use web storage and only run on r251.2

    Web Storage was replaced by Local Storage about 7 years ago. It happened in Construct 2, before Construct 3 was even out. If you keep using retired features for years and years, you will inevitably run in to problems. This is why you should make an active effort to move away from deprecated features.

    Having said that, we haven't touched the Web Storage plugin ourselves for years, so I doubt anything changed on our side. I wouldn't be surprised if some browser change broke it - perhaps browsers are finally removing it, as it was replaced by better storage solutions years ago.

    You're probably best off just using the Cordova CLI and doing your own builds locally with a custom configuration. The build service is configured to work with the latest release, and if that ends up breaking old releases, we probably can't do much about it.

  • FWIW the default language is decided based on what the browser says your preferred language is. So maybe check your browser settings to see if the preferred language is what you want it to be.

  • Staying on old versions will probably cause as many problems as it solves. All the bugs, compatibility fixes, updates for specification changes and so on are in the latest release; if you stay on an old release you miss out on all of those and so will start to accumulate already-fixed bugs that nobody can help you with. Especially with Android, sooner or later the target SDK version requirement for the Google Play store will increase, and then APK builds by old releases of Construct will not be allowed to be published to Google Play as they still use the old target SDK version.

  • Old versions are not maintained. Even if we issued an update, it would be a new version, and so you'd have to upgrade to the latest version anyway. Why can't you use the latest version?

  • r251.2 is about 9 months old, released last June. Have you tried the latest stable release r285.3? I just did a test build there and it worked fine.

  • It worked fine the past few years. Cordova does not always need an update to support bumping the target SDK version.

  • Please only post in English as per the Forum & Community guidelines. I've Google translated the post.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • As ever, please report any problems to the issue tracker following all the guidelines.

  • By default the runtime runs in a Web Worker so there is not direct access to the DOM.

    If it's a small and simple amount of JS code, it might be better just to use the JS coding feature (which switches to DOM mode by default).

  • These days every year the required target SDK version increases to be able to publish to the Google Play store. If we did nothing, then when the deadline comes it would no longer be possible to publish to the Google Play Store. We increase it well in advance to make sure there's plenty of time to sort out any compatibility issues that come up.

    I think something went wrong with it for this beta update though. As ever any issues should be filed to the tracker.

  • It only affects mouse and touch input. It does not affect collisions.

  • A recent update to the Polish translation has resulted in 130 errors. The list is available here: dropbox.com/s/5bsilbfnlopfxsw/pl-PL-2022-03-22.txt

    They will all need to be corrected before the in-progress translation in the Construct editor is updated again.

    Please do not use machine translation, like Google Translate, when translating Construct 3. It is an inappropriate tool that results in poor quality translations. These translations will then fail later quality reviews and have to be re-done, resulting in wasted effort and taking longer before the translation is ready.

    Learn more about the translation guidelines in the forum thread How to help translate Construct 3.

  • Do you mean using the Browser.Language expression?

    This just directly returns whatever the browser thinks the language is (via navigator.language). So if it's wrong, it's the browser that's providing the wrong value, not Construct.

  • It looks like a bug. Please file an issue.

  • If those are the only two files you need, can't you just make a tiny cordova plugin that adds those tags? It seems like there shouldn't be any need to fork an entire plugin if all you need to do is add a small change to config.xml - you could use the original plugins on npm and include your own tiny plugin to add those tags, and such a tiny plugin would be trivial to review and update on the build service.

    Also I'm not really clear why this is specifically needed for C3 - don't the original plugins already add those tags? Why is this different in C3?