yeah, I know about random using decimals, but I figured when I use it on seconds it doesn't matter since even if the system spawn smth 33.728 seconds, it'd be fine by me, but in the equality case, it makes sense of course.
hmm.. so could you explain how the algorithm above would be executed? just curious to know more about the engine.
As I said, I imagined "every random(1, 10) seconds" working the following way:
The system checks the condition, chooses 3.456, executes the action after 3.456 seconds. Then it checks the condition again (as you mentioned it won't remember that it chose 3.456 before, but it should still random nonetheless right?) and chooses 7.219, after 7.219 seconds it executes the action and checks the condition again. etc.
If what you meant was that, when it checks the condition and chooses 5.15 for example, and then before that time passes forgets this choice the next tick, then it wouldn't spawn anything at all, however that's not the case.
Sorry for writing so much, I just wanna get to the bottom of this :D
P.S. I understand your solution, but what if what I want specifically is for object to spawn the least 2 seconds apart and the most 7 seconds apart and it should random in between? Like I want to progressively narrow this gap, imagine something like:
LOW LIM = 2
HIGH LIM = 10
Every 1 second --- substract 0.1 from LOW LIM
--- substract 0.8 from HIGH LIM
Every random(LOW LIM, HIGH LIM) --- spawn object
how do I achieve this if "every random x second" doesn't work that way?