Refresh events and live players
The refresh button requests up-to-date information for the selected game.
How to use it
- Open the calendar or an event card.
- Select Refresh and wait for the icon to stop spinning.
- Check the event time, interested players and current player count.
Advice and practical context
Result freshness
A manual refresh requests a newer state, but fields can come from different sources and need not change together. The last successful observation time matters more than the spinning icon because it identifies the freshness of the particular value.
When nothing changes
Unchanged CCU after refresh can be real or reflect a delayed source. Check the timestamp and error message. A common mistake is repeatedly refreshing while ignoring the displayed next-attempt time or source limit.
Interested-user count, schedule, and CCU can refresh at different times. Compare each field with its own observation timestamp. After an event ends, fresh CCU describes the game now rather than historical event attendance.
Technical detailsCalculations, permissions and behavior
Event and player-count updates
Events, cover URLs and exact Interested counts are kept in MARPLA's durable server archive, so they appear immediately after a page reload or a new server process starts. Opening the section reads only this archive and never waits for Roblox. Roblox is normally checked every six hours; missing covers retry after 30 minutes and event-list failures after at least one hour.
The all-games view places opened games in a durable queue and refreshes at most two immediately; the background collector continues two per cycle. For one selected game, the square sync button bypasses the six-hour age, but another click within one minute does not create another request; a shared server lease prevents a parallel duplicate. An expired archive stays visible while the request runs in the background.
A successfully created or edited event is written to the archive immediately and does not trigger an immediate repeat list read from Roblox; scheduled reconciliation follows later. The guide icon beside the heading opens these instructions. Playing now contains the latest received player count.
After 15 minutes, the dot turns yellow without an extra status line; hover for the observation time. Online counts are requested first, starting with the oldest observations, and saved in batches of 50 games, before ratings and other optional data. Refresh explains when collection is already running, only part of the data was received, or Roblox is temporarily unavailable; saved values are never presented as new observations.
Per-source event freshness
Opening a card normally reads only the stored archive and never waits for Roblox. The background queue checks the event list and dates every 6 hours and official social links every 24 hours. For a newly discovered event, background collection stores metadata first and moves its cover and Interested count to a separate turn 5 minutes later; a forced manual sync fetches them immediately.
A ready or blocked cover is not downloaded again until Roblox changes its Asset ID; Pending retries in 30 minutes. Exact Interested refreshes every 15 minutes for a live event or one starting within a day, hourly for the next 7 days, and every 6 hours for later events. One turn reads no more than eight counters and fairly continues the remainder in 5 minutes.
Partially returned covers and counters are saved before the next turn. A failure in one source or the collector's local deadline keeps prior values and does not create a false Roblox error for the other sources.