Printable View
Hey, I've searched all around on forums and I haven't found anything close to this. After my player is killed create object is immediately done, I would like to delay this by a few seconds before another player is created. I created a timer and played around with activating it after the player is killed and I can't get it to activate the timer countdown. Logically I know what I want to do, I just don't know how to put in MMF2
Here you go.
Thanks, I'll check it once I get home
I'm confident that Chris' other reply will help, but also consider encouraging abstinence.
;)
It doesn't seem like a killer problem.
Create a counter named Spawn Delay.
On the condition that kills the player, set Spawn Delay to one.
Event: Every second, If Spawn Delay > 0, add 1 to Spawn Delay.
Event: If Spawn Delay = 3, and number of Player = 0, create Player. Set Spawn Delay to 0.
Quote:
Originally Posted by Grim_Jester
Where is "If Spawn Delay >? I don't see where I can put that from that condition
OK it works Grim...However, my question is why am I adding 1 to the Spawn Delay?
Because "Spawn Delay" is a variable that is holding time in it. It's essentially seconds.
You could call it SecondCounter instead of Spawn Delay if you wanted.
Did you look at my example Jbrown?
Aylictal was correct, but let me provide some more detail to what I suggested.
In my example, you initially set Spawn Delay to 1 when the player object is destroyed. Setting it to 1 is used to start the timer with another condition later.
The condition is looking for Spawn Delay to be more than 0. This condition is true/active when the player is destroyed, because we set it to 1. Now that it's true, we tell the counter to start counting (in this case, with seconds). We are having MMF 2 add 1 to Spawn Delay every second.
When the count of Spawn Delay = 3, that means that two seconds have passed since the player object was destroyed.
Why 2? When we set it to one when the player was destroyed, that was done instantly. A second later, we increased it to 2. Another second later, it's at 3, the player object is created, and Spawn Delay is reset to zero in case we have to do it all over again.
If you wanted the player object to be created 5 seconds later, you would check to see when Spawn Delay = 6 instead of 3.
I hope this helps.
Chris Burrows' solution is definitely more elegant, but perhaps harder to understand. You should take a look if you haven't already.
heres an example using the eggtimer object, which is what you originally wanted to do (i think?)
the timer here is checking 3 seconds after the last death of the sheep, and can easily be modified or copied.
Attachment 7289
I have quickly done up an example for you in 5 events. This could be abbreviated to just two events, but for the example I included movements in there to display it working for you.
This is assembled using 2 events using the game's FPS timer instead of the built-in timer as this can (on some platforms) cause issues. With using the framerate to determine the timer it's guaranteed to keep up with your game/app at all times.
Attachment 7292
ChrisBurrows example is perfect for this. There are so many ways of doing this sort of thing and they are all good. I usually use the objects alterable values and just set the object off screen then reposition it after the delay is finish. Four events like Chris's
If you don't mind counting deep into the treacherous depths of negative infinity, it can be done in 3 events.
Sorry to be Negative towards yours Chris, but I shot the target 3 times and it didn't respawn. You need to remove 'Only One Condition When Event Loops' and retry with <= 0. It can skip, as it did with me. No need for only once event loop because you're 'Always' means its subtracting a number all the time so it would only hit 0 or -1 once anyway before resetting :p
Kind of strange, Mr. Borrows example in post 14 works fine on my end every time. Nice Chris! Me likey!!
Mmmm I rushed that one.
Madness. You've gone too far!
Quote:
Originally Posted by ChrisBurrows