Ashley's Forum Posts

  • I don't see any point to open sourcing it. It's just a tiny tool that does one very specific job.

  • It's difficult to comment. It could actually be completely unrelated to pathfinding, there's no evidence the things you mentioned are actually related. It's easiest to help if you share a Construct project file.

  • We just recently started adding some 3D features. Take a look at the latest beta releases! There's also this video which illustrates some of the possibilities.

  • Moved to scripting forum.

    To detect a touch/click on an object, use the normal "mousedown" or "pointerdown" event, convert the touch position to layer co-ordinates with cssPxToLayer, and then use containsPoint method to check if that point overlaps an instance.

  • You can't. Use local file saves instead. They are more reliable, as clearing your browser data will not erase your saved projects.

  • It's intentional that the local browser save option is hidden if the browser supports local file saves (which Chrome does) and there is nothing already saved to the local browser. Too many people accidentally lost their work clearing their browser storage.

  • In Construct, the 'On collision' event is internally implemented as 'Is overlapping, and was not overlapping last tick'.

    When using JavaScript coding, it's up to you to implement the same logic in your code.

  • If you're trying to access a global variable, since Construct uses modules, you'll need to refer to globals as globalThis.myGlobal rather than using the name myGlobal directly.

  • Swipe in from the sides to access the side panes. See Construct 3 on mobile in the manual.

  • It's often infeasible to work around browser issues. We don't know why or how they are going wrong, and all our existing code is there for a necessary purpose. So what could be changed? We could spend a few days making random changes and try to avoid it, but there is no guarantee we'd find a workaround, and no guarantee the workaround would actually work for everyone once established, because we don't actually understand what the problem we're trying to work around is. The only sensible thing to do is fix the underlying issue in the browser.

  • It was easy to do, so I've added it for the next release.

  • Regarding IAP. There has been bug fixes for the Google Billing Library in v3.0.1 (released 2020-09-30) and also in v3.0.3 (released 2021-03-12) which both could affect cordova builds afaik.

    Sure, all software libraries regularly update, and we periodically update the versions we use too. Minor updates like this tend to just be routine maintenance and so not something we have to rush updates out for. IAP also uses cordova-plugin-purchase internally, and we're up-to-date with the latest version of that (v10.5.0). It's not easy to update further than that Cordova plugin supports, but it's regularly maintained and it looks like they're already working on an update with Google Billing Library v3.0.3, so it will get updated in the end. This is all pretty normal for a software library.

    Regarding consent SDK (part of Mobile Advert plugin) there has been a lot of changes here

    I'm aware of that, but as I mentioned these changes are really difficult and time consuming to incorporate. It's on the todo list.

    Regarding Admob SDK (also part of the Mobile Advert plugin) Google has made a lot of changes for the different ads, most of which was released in v19.2-19.7.

    We actually already use v19.8.0, which only came out last month. I'm aware there's a v20 with lots of breaking changes - again it's difficult and time consuming to make all the changes necessary for this update, but it's on the todo list.

    In short, I'd like to point out that just because a new revision is out, e.g. 1.0.1 while we're still using 1.0.0, is not a sign of some kind of negligence about updating. It just means some regular maintenance has happened, and users of the library will update in due course.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Construct uses industry-standard JavaScript, identical to the language used in browsers or server-side tools like node.js. The language is not specific to Construct. What you learn using JS code in Construct will be highly transferrable to other places using JavaScript.

    However as with any tool or framework, there are various API methods specific to the platform, which you can find documented in the scripting section of the manual.

  • Both the IAP and ad plugins are maintained and should be up-to-date (apart from Mobile Ads not using the very latest version of the ads SDK, which AFAIK is not a problem for the time being).

    There are additional hurdles to some features - for example IAP subscriptions involves running a server to verify subscriptions. This is very difficult to support in software that's meant to run 100% client-side. Who runs the server?

    These plugins are also some of the most difficult and time-consuming plugins to develop. We're a small team with limited resources, and it's already painful the amount of time that gets sucked in to things like debugging ad issues (which often are just mistakes in events or people misconfiguring the AdMob side of things), and maintaining them to keep them up-to-date with changes. I know these addons are important to a lot of people. But they are not your only choices: there are already several third-party addons out there, some of them commercial, which provide lots of extra monetisation options - for example see addons in the Asset Store and the monetization category on the Addon Exchange. This is exactly what we intend with the addon system: to make sure you're not limited to just what we offer - anyone can make things like extra ad/monetization plugins, including covering lots of different kinds of ad services, which you can choose between.

  • Click "Learn more" and it will be permanently hidden.