Fixed in v.1.1.0.
Now working in Construct versions up to r181-2. The newer versions should also work fine. They changed how the conditions are stored in r175, so I adapted the plugin to it.
Thanks for the report. Confirmed. Will figure it out soon.
Works fine in the latest stable version though: Release r171.3 stable
You don't pass anything TO construct. You use "Value" expression of the plugin to get the value of whatever you want in your code. See the manual and the examples.
Please see readymag.com/valerypopoff/valerypopoff-js-plugin What you need is "Value" expression.
What do you mean "it doesn't work if we changed the plugin's name". What plugin's name? Change where?
readymag.com/valerypopoff/valerypopoff-js-plugin
Send me the project file that reproduces this and I'll look into it
It's not a bug. This plugin doesn't support workers
Fixed it in v.2.2.0
On it
Yep, I'm on it
Who told you there's variadic parameters in this plugin?
Not yet
The new 0.8.0 version is out. Variadic actions and conditions are now deprecated
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?
Member since 7 Aug, 2016