Ashley's Forum Posts

  • Try clearing your browser cache.

  • As ever, we get far, far more feature requests than we can possibly act upon, which is part of the reason we have the addon SDK in the first place. If you want to submit an official feature request, you can do so here.

  • Your code also confuses object types and instances. I'd suggest going through the Learn JavaScript in Construct tutorial, or the quick-start guide, or using TypeScript which will catch such mistakes for you.

  • When you choose to use a third-party addon, you are trusting the developer of that addon for long-term maintenance. If they give up on it for any reason - which they are perfectly entitled to do, especially if it's free - then it won't be supported any more. You should bear this in mind when choosing to use third-party addons.

    The entire purpose of the addon SDK is to allow other developers to implement more features than we have the resources to do ourselves. It is not generally feasible for us to officially reimplement any particular third-party addon, and besides doing so defeats the purpose of the SDK.

    The Addon SDK v2 ought to have the technical capability to support this - it supports all officially supported APIs from the old SDK, and if any are missing, we will prioritize implementing them.

  • It all works for me - the key is to put the code with the call to registerProcessor in a separate JavaScript file in the 'Files' folder, and load it with audioContext.audioWorklet.addModule("audioWorklet.js"). Here's an example.

    digitalsoapbox please note from the Forum & Community guidelines:

    Be polite, respectful and welcoming

    Be supportive of the products we all use and the team behind it, and make sure feedback is constructive (no pun intended.)

    Having a persistently antagonistic, cynical, combative, sceptical or complaining attitude. For example, no software is perfect, but if you continuously claim that our products are absolutely terrible in every way, you may quickly wear out your welcome.

    Deliberately trying to provoke a reaction.

    Your recent posts have repeatedly gone against these guidelines and are not acceptable. I am closing this thread and please be warned that if your posting continues to go against the Forum & Community guidelines, further moderation action may be taken.

  • You do not have permission to view this post

  • I would advise to file any problems to the issue tracker, as we have a process designed to help identify and resolve problems there, and issues only mentioned on the forum are easily lost and forgotten.

  • If this only happens in preview or remote preview, try clearing your browser cache. There were some server-side changes for the new preview system. They should have already come through by now, but I guess old or rarely used devices might not have updated yet.

  • There has not been any intentional change in support. If you think there is a problem with the latest release, please file an issue.

  • They're designed for things like conversation trees or finite state machines, where a visual 2D layout lets you more easily track how things progress over time. The 'Sniff and fetch' visual novel example shows the kind of thing it's designed for. If you try to use JSON or arrays or some other data structure for this kind of thing, you can't so easily follow the different branches. You can also do things like put in back-references which are trickier to express in formats like JSON.

  • Generator functions return iterables (and inside the function body they can use yield). An iterable is basically anything you can write for (const thing of iterable) or [...iterable] with. (The definition is a bit more complex but in practice that's what it means.) As ever there's lots more info on MDN.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • It should just work. You don't need to do anything special. For example if I create a new project and import a project file image.png, then putting <img src="image.png"> in a HTML element object will show the image.

    On further reflection, I'm not even sure the discussion is still about the Addon SDK v2 and encapsulation. It seems to have broadened out in to an extensive discussion about the overall design of Construct. You may discuss that if you wish, including being critical if you really see things that way, but it isn't really relevant to this thread any more, which is specifically about the process of migrating Construct to a new addon SDK and the reasons for doing so.

    I suspect this thread has outlived its usefulness anyway, and that further discussion will no longer be productive. We try to lean towards allowing people to freely express their views on the forum, and I'd point out this thread started in May so there have been about 4 months of largely unrestricted discussion with everyone offering their (sometimes strong) views, but discussions like this end up producing more heat than light. As per our Forum & Community guidelines, under "reasons we may lock threads", we do state a couple of reasons that are happening here, such as chaotic changing of subject and repeating the same discussion points in a never-ending thread. On that basis I am closing this thread.

    I'm still happy to support any developers who have questions about how the new Addon SDK v2 will work and how to use it. However please start separate threads for those queries, or for any other general discussion points. I am not particularly willing to continue to discuss the rationale for the move to the Addon SDK v2 any more as I've already made our case ad nauseam in this thread; I will refer any future questions to my existing answers here, and if you are not persuaded then I suspect nothing I say will do. My previous post will probably suffice as my last remarks on the subject, as in summary we are moving from an unsustainable SDK that will end in disaster, to an industry-standard approach used by all professional software. I am fully aware of the disruption this will cause but I believe it to be absolutely essential for the long-term future of Construct, and so I am asking for the co-operation of addon developers to help the transition go as smoothly as we can manage. We have also introduced LTS releases - the first one came out today - in part to allow for more time for the transition to happen. This idea mainly came from feedback in this thread and elsewhere, so we are listening and thinking about what we can do to try to make things go better where feasible.

    I will keep the original post updated with the current status of the Addon SDK v2 for informational reasons. Any other key updates I will post separate sticky threads for in this SDK forum.