Nevermind, didn't read what your issue was correctly.

New .capx!

https://www.dropbox.com/s/ktfm9hd2f7j28 ... .capx?dl=0

Sorry for the late response! Just set the text box's height to 144 to match the correct line-object height ratio.

Good to know, thanks newt ! I guess I'll stick with what I have if the formula cannot be improved.

Here's a .capx!

https://www.dropbox.com/s/ktfm9hd2f7j28 ... .capx?dl=0

I'm thinking about a mask covering the bottom of the textbox, then when the textbox has appended a new line it will go slightly (character height) under so it is covered but seems like nothing was written, then tween it upwards with LiteTween?

So, I've been using lerp as long as I started with construct 2. I switched to 1-n^dt after reading this, which supposedly gives perfect accuracy without worrying about the frame rate, but it is still obviously time scale dependent. I've tried multiplying by timescale, and other variants, but no luck.

So just being curious, would there be a way of improving even more the "speed factor" of lerp so it would also support any time scale? And would the extra calculations hurt performance if many of these are called compared to the "vanilla" lerp?

Wouldn't having 20+ instance variables in 50+ instances constantly changing affect performance? This method made it more compact to design weapon stats too, but oh well ~

This is what I meant to do (I did it quite a while ago, but it works), with parameters instead of instance variables.

Ugh... The point of the system was to avoid creating more instance booleans/variables and make it compact. Isn't there a more clean workaround? Making a timer seems messy. I'll try it out, anyway. Thanks, blackhornet

Maybe using bullet would do the trick?

compare two values - distance(player.x,player.y,enemy.x,enemy.y)

if not agro-----------------greater than X

-------------then

-------------set enemy "agro" true

isn't agro

-----every X seconds

-----set bullet speed to X

-----set bullet angle to random (360)

is agro

-----move towards angle -

-----angle (self.x, self.y, player.x, player.y)

-----X pixels

Got a shooting system working, uses 13 parameters so I wrapped it up with a function instead of using another dozen of instance variables (do not know if this is a good idea). Works if it is given numbers, but it does not if given function.param(number). I've read both entries in the manual and looked around, but I cannot figure it out.

I'd appreciate any help!

Capx: https://www.dropbox.com/s/jp6a7sn0w37bu ... .capx?dl=1

Thanks for the demo, — ! I do feel relieved now, editing the title to solved.