At the moment the Timer behavior can time down to 10 milliseconds. I have run into many problems where having an object be deleted in less than 10 milliseconds is vital.
The timer limit at the moment:
Example
Say I have an enemy. The enemy is supposed to shoot at the player. The enemy’s ammo should be destroyed as quick as possible after hitting the player without being automatically destroyed. If I wanted the enemy to fire a laser, then the laser sprite would build up on the player for as long as the timer allows before destroying it. This would allow the player to be hit multiple times more than intended.
If the Timer behavior could go into milliseconds, the laser sprite would be destroyed before the player got hit multiple times.
This minor Feature would be very helpful for the ‘De-Bug’ system. Also, if I made the ammo sprite solid then then it would push the player before it got destroyed.
That is all, please add this feature to Flowlab.
Thank you,
Hey @JUSTPLAINOP - there are a couple of issues at play here:
First, I think high-precision timers are not the way to create the game mechanics you are describing in a reliable way. I don’t think I fully understand your explanation, but you might want to consider more direct ways of making sure things happen in the order you want.
Second, Timers can only activate while the logic is executing. Trying to activate timers faster than the frame rate just means the logic will run on the next frame anyway, so higher precision here still won’t help you.
I don’t see the need for a timer at all. Something that a lot of people do it overuse timers way too much, but with proper frame ordering most all code can be done without them. The only time I use timers is when I what a noticeable delay like 3/10 or if I’m making something purely for testing so I won’t keep the code anyways.
If it gets automatically destroyed, the player won’t get hit at all. I want the ammo to hit the player but not build up and hit the player multiple times.
When the bullet collides with the player, all of the collision behaviors that allow the bullet will be activated on the same frame, so It would still work.
Like grazer said a timer any shorter won’t do anything.
If you have a timer between 0.1-0.3 it will technically all activate on the same frame. They will technically go off at different times within the same frame, but that gets into frame ordering.
