• Categories
  • Recent
  • Tags
  • Popular
  • Solved
  • Unsolved
  • Users
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Darkly)
  • No Skin
Collapse
brainCloud Forums

Inquiry Regarding Tournament Reset Schedules and Early Season Termination

Scheduled Pinned Locked Moved Solved General
3 Posts 2 Posters 8 Views
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • M Offline
    M Offline
    moondory77
    wrote last edited by
    #1

    Hi @Paul-Winterhalder @JasonL

    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?

    1 Reply Last reply
    0
  • J Online
    J Online
    JasonL bitHeads
    wrote last edited by
    #2

    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.

    1 Reply Last reply
    0
  • M Offline
    M Offline
    moondory77
    wrote last edited by
    #3

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

    1 Reply Last reply
    0
  • [[undefined-ago, M moondory77, ]]

  • Login

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Solved
  • Unsolved
  • Users