Scirra has recently announced and then released a new feature for Construct 3: Javascript coding in the editor. I was extremely hyped by this announcement and c...
Yes, I meant that. Why? C3 instances are already being ticked. What is it that you're trying to do that needs to be ticked in JS?
Well, if I want to write all of the game in JS, I need to be able to run some code on each frame.
But you can't make the whole game in JS, there's still sprites and stuff on the Construct side. What is also on the Construct side — is the ticking mechanism.
From what I understand, you're trying to extend Construct sprites with your own classes and make them a part of your model. But what's the benefit of it?
The ticking mechanism and all the routines related to it — are the engine. Why are you trying to invent your own engine inside of the Construct engine? Why don't you let Construct call whatever js functions you want to be run every frame?
I'm not sure we're on the same page concerning that whole JS thing.
Construct just introduced JS in the editor with the aim to eventually allow them to replace event sheets entirely. Aka making games entirely in JS.
My code is nothing final and only served as an example to what I meant in the proposal. I am asking to allow users to write their own classes and link them to C3 instances to write said code that would replace event sheets more effectively.
I don't want to write my own engine, far from it. I want the engine to extensible.
That would let Construct call js functions every tick, unless you meant call them from event sheets in which case, that would be "replacing event sheets entirely".