Good morning. I am having a little problem with creating a personal quest. It's how to construct a countdown timer for one of my quests. I searched the Qedit.info page under the OPCodes, I can't seem to find anything, except for Ba set time limit which us used for battle mode. I've check some of the PSO BB quests that have a countdown time limit, and nothing. So, I am coming to this community to ask if anyone knows how to go about doing it. Ba set time limit is self explanatory, but for some reason regular PSO BB quests isn't. Maybe it is. Thanks for your time.
Count down timer
- Thread starter parrot215
- Start date
- Guildcard
- 42017744
When you want your timer to start, get the starting time in seconds and save it to a register: https://qedit.info/index.php?title=Gettime
Where you go from here varies. What Sega usually did was spawn a
The timer thread has a few main jobs.
First job is to call
The second job is to display the current time using https://qedit.info/index.php?title=Window_time and https://qedit.info/index.php?title=Winset_time , where you give
The third job, depending on quest, is to detect if the quest is over and how to handle it. Sega was wildly inconsistent with this. Sometimes the timer goes away in a few frames, sometimes immediately, sometimes it sticks around until floor change. Typically the timer thread handles the quest failure message (usually a window_msg with freeze_enemies and return to p2).
Some other notes:
Where you go from here varies. What Sega usually did was spawn a
thread_stg for the timer thread in the floor handler of each floor. The thread_stg can loop until the timer has started (the register from above is nonzero for example, or another register). A number of custom quests, including my early ones, typically create a single thread at quest start that waits until the timer should start. I think a single thread is easier but it has some corner case issues if quest failure occurs during a loading screen (which can be fixed by checking for failure in floor handlers).The timer thread has a few main jobs.
First job is to call
gettime every frame to get the current time in another register. The difference between this register and the first one is the number of seconds that have elapsed since quest start. You should know the countdown timer's max time, so you can do some math to figure out how many seconds are left in the quest.The second job is to display the current time using https://qedit.info/index.php?title=Window_time and https://qedit.info/index.php?title=Winset_time , where you give
winset_time the number of seconds you calculated.The third job, depending on quest, is to detect if the quest is over and how to handle it. Sega was wildly inconsistent with this. Sometimes the timer goes away in a few frames, sometimes immediately, sometimes it sticks around until floor change. Typically the timer thread handles the quest failure message (usually a window_msg with freeze_enemies and return to p2).
Some other notes:
- Typically you
sync_registersome random register from zero to nonzero to indicate the timer should begin for all players. - Never
sync_registera value retrieved fromgettime. - Don't
sync_registerthe final clear time or you'll have a jumpy timer when the quest is ending.
Last edited: