I have a leaderboard in a map I'm making which changes every 10000 seconds, but it seems to never change. I heard hyper triggers make waits longer, but by how much?
You can't have any other waits for that player if it continually cycles, and make sure you add the hyper triggers last so they don't interfere with your other wait triggers.
So, do you mean I dont make the hyper trigger trigger(a lot of wait for 0 milliseconds) until all my other wait triggers are done?
Save your map with no Hyper Triggers in it, then add the hyper triggers and save it again, then they shouldnt interfere with each other... But each time you add a new wait command after the hyper triggers, youll have to repeat the process and re-add the hyper triggers.
All right, I'll try that. Thank you.
Wouldent it be easier to just make the hypers for a player that dosent use waits(a neutral computer or something)?
Yes it would, Besides if you have a 10,000 wait for your leaderboard then it would stop your hyper triggers from functioning.
You will need to have the hyper triggers and your leaderboard owned by seperate players.
To answer your question about how long the hyper triggers will extend your wait. Well it is very dependant on the structure of your hyper trigger. A crappy hyper trigger would make them take a extra 30 seconds but a good one would make it take 6 hours. But even 6 hours is a short time when compaired to how many hyper triggers some people create. The wait in your leaderboard would be delayed until the hyper triggers compleat firing, the problem is hyper triggers are designed so they do not to finish.
All right, I deleted the wait and made it so there's only one leaderboard. The other one(next level) goes in mission objectives so you can check whenever you want. Seems a lot easier to do and gets rid of the delay on other wait triggers. Thanks for the help! ^_^
Bolt why is it that when a trigger is created before the Hyper Trigger its waits still execute, but when it is created after the get messed up?
Because only one wait can exicute at a time. If it is before the hyper trigger the wait will have prioity and jump in the middle of the list of waits on the hyper trigger. As a side effect the hyper trigger will not function when the other wait is running.
When the wait is after the hyper trigger every wait in the hyper trigger has priority over the wait after it. Therefore the wait after the hyper trigger must wait for all the waits in it to compleat before it becomes it's turn to fire.