Inquiry Regarding Tournament Reset Schedules and Early Season Termination
-
I would like to clarify how the system handles result calculations and rewards when a tournament's reset cycle is modified.
If we change the reset interval of an ongoing tournament to force-start a new season, does the result calculation and reward distribution automatically reschedule to align with the new season's start time? Or does the system maintain the original schedule established at the beginning of the season (meaning rewards are only processed at the originally scheduled time, even if a new season has already begun)?
If the system follows the original schedule, it would be difficult to handle cases where we need to emergency-restart a season. Is there a supported method to prematurely end a season (including processing rewards) and immediately trigger the start of a new one?
-
Yes, changing the reset cycle automatically reschedules result/reward processing, but only while the
TournamentResultsjob is still inScheduledstate. If the job has already been fired or transitioned out ofScheduled, the update is silently ignored. The new rotation's end time gets stored, but the old job has already run (or is running), so no re-processing occurs for the current rotation. There isn't a force-end rotation API, but as a workaround, you can manually set arotationResetDateto a near-future time. -
I see! So if the schedule hasn't started yet, changing the reset cycle resets everything, including the rewards. Thanks for letting me know!
-
[[undefined-ago, M moondory77, ]]