Thanks Lucid, I understand it, just don't think it will be useful for anything. Things like health bars are already easy to do with variables, just subtract/add.
this is what I meant by health bar:
you could make a much cooler more complex one, but I wanted to keep it simple. your health goes up the higher your mouse is on the screen. Also, you can resize the health bar, change the screensize, etc, and this same code will still work, with no changes whatsoever
here's tulamide's example again, but using a few extra lerps in some other ways. You can change the global variable 'numberofballs' in start of layout, and you'll notice they always perfectly space apart and behave correctly, and the color blend works perfectly regardless of position. Something like this would be impossible without lerp, or some mathematical equivalent:
It's nice plugin, but I prefer to don't use plugins if goal can be reached with events. I think there must be way to do it with pure Construct
everything in construct is a plugin. every object and behavior is created with the same sdk. the only difference is some are official plugins made by ash, davo, and rich, and some aren't. I can definitely respect wanting to understand the math well enough to do it without the new plug, and tulamide already showed how, but avoiding using the faster way once you do understand it is kinda pointless, imho. Especially since in circumstances where it takes more than one construct expression to achieve it, the plugin will always be faster, both in the time you take to write and read your own code, but also in the execution speed, as the c++ within a plugin runs faster than construct's interpreted expressions. that speed difference won't matter in most caps, but good to know anyway