Inquiry Regarding Tournament Reset Schedules and Early Season Termination

moondory77

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?

JasonL

Yes, changing the reset cycle automatically reschedules result/reward processing, but only while the TournamentResults job is still in Scheduled state. If the job has already been fired or transitioned out of Scheduled, 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 a rotationResetDate to a near-future time.

moondory77

I see! So if the schedule hasn't started yet, changing the reset cycle resets everything, including the rewards. Thanks for letting me know!

moondory77

hi @Paul-Winterhalder.

Following up on our previous discussion, I have an additional question regarding leaderboard scheduling.

When we modify the Leaderboard Config to change the reset time, could you provide a way to apply those changes to already instanced/active division instances?

Currently, our service operates on a weekly tournament rotation. There are scenarios where we need to adjust the reset time of an ongoing tournament to a specific time based on certain triggers.

We’ve noticed that when we update the reset time via Design > Leaderboard Config:

For future divisions (those not yet created), the new "Calculate Result" time is correctly applied when they are eventually instanced.

For active divisions (those already instanced), the updated schedule is not reflected, and they continue to follow the old reset time.

For our service logic, it is critical that all divisions remain synchronized, ensuring they all start and end at the exact same time.

Is there a feature, an API, or a workaround to forcibly update the reset/rotation schedule for leaderboard instances that are already in progress?

Paul Winterhalder

@moondory77 - why would you need/want to update a tournament in progress?

We consider the tournament to be a contract between the player and the game dev. You enter this tournament. You have <X> hours to compete. And you can win <Y> in prizes.

Changing the rules half-way through the tournament seems unfair? You are changing the duration? The prizes? These are both things that the player did not agree to.

Anyway - that was the assumption of the system - and it's why once a tournament is started any changes you make to the tournament get queued up for the NEXT tournament cycle, not the current one.

That said - divisions are even more complicated - as even if we wanted to there would be potentially thousands of records to update to make the change.

I need to better understand your use case to consider this request.

Paul.