Find or create an event
Events are a calendar of game updates and activities.
How to use it
- Open Events and select a game in the calendar heading.
- Open an event to read its description, check its time and visit the game.
- Select Create event. Choose the game by name and icon, just as in advertising; search accepts a name, ID or Roblox URL. Enter the title, subtitle, description and times, then save to Roblox.
- Past events show the interested count in the same place as current events. It is retained in the archive; hover over the count to see when it was obtained.
Advice and practical context
Event as context
The calendar links an activity's timing to audience changes, but nearby dates do not prove impact. Distinguish scheduled start, actual active period, and observation time. The description should tell players what happens and let an analyst identify the measurement window precisely.
After the event
Compare a complete pre-period, the event itself, and a mature post-period while accounting for weekends, ads, and other releases. Do not compare the event's peak hour with an ordinary day's mean or treat interested users as guaranteed attendees.
Choose the event outcome in advance: live attendance, new Visits, later returns, or expressed interest. Each requires a different window. Record overlapping game activities as well, because concurrent events cannot be separated honestly after the fact.
Technical detailsCalculations, permissions and behavior
Game events and contacts
The game side card and the shared Events section show public active Roblox events with a cover, title and dates in the device timezone. In the shared feed, the people icon and large current count sit in their own left-aligned row beneath the game artwork and title, without a redundant label. MARPLA reads the dedicated public Roblox Interested counter instead of counting the bounded list of 25 profiles; when the exact counter is unavailable, no value is substituted.
Select the event or its image to open Roblox. Creator titles and descriptions remain in their source language. Events without a dedicated cover use the game image labeled Game cover.
If Roblox has not prepared the image, MARPLA shows Cover not available yet and retries later. Contacts come only from explicitly published Discord and Telegram links; restricted data is not bypassed and handles are not guessed.
Creating and editing events
Click the dashed creative area or drop a PNG/JPG into it. The same area replaces the selected image; Undo selection restores the previous choice. The title and subtitle are each limited to 25 characters; counters below the fields show the used length.
Emoji are preserved and count towards the text length. Before saving an event, MARPLA waits for Roblox to approve its image. Upload completion does not mean moderation is complete.
If review takes longer, save again later in the same editor: the existing image is checked without uploading a duplicate. If Roblox rejects the event, the form displays the available reason; correct the indicated data and save again. The large game picker with artwork sits directly in the calendar heading, matching Advertising: choose one game or the combined feed.
Select Create event or the pencil in an existing row; the Events action on a connected game card opens the same workspace already filtered to that game. The form changes the real Roblox event title, subtitle, description, start, end, visibility, entry Place ID and creative. Select Upload creative or drop a PNG/JPG into its field: up to 20 MB, both dimensions below 8000 pixels, with 16:9 recommended.
Editing shows the current cover; Replace creative selects a new image and Undo selection restores the original before saving. Changing only the creative enables saving. The file uploads to Roblox when you select Save to Roblox; moderation may delay the cover.
The experience API key or OAuth connection needs Assets: Read and Write for the image owner. If grants are missing, Configure Roblox connection opens that game’s setup. If Roblox is still processing the file, saving again resumes the same upload without creating another image.
Errors keep the file in the form; if the event was already saved, retrying edits the same event instead of creating another. End must be later than start: an invalid field immediately receives a red outline and a precise explanation, while Save to Roblox stays disabled. The button also stays disabled when required values are invalid or nothing changed.
Roblox failures show the known reason, and a successful response is additionally checked against the saved dates. The MARPLA Game event management role permission plus universe.event:read and universe.event:write on the selected Universe ID are required. If grants are missing, the public calendar stays available and links to the exact key setup.
Interested counts for past events
The new-event form selects a game by name and icon, as in advertising, with search by name, ID or Roblox URL. After an event ends, MARPLA retains its interested count and observation time. Past events without a post-event snapshot request the exact Roblox counter, at most eight per cycle.
A successful observation stays in the archive without further polling. Failures preserve the previous count and never replace it with zero: automatic backfill retries up to three times with a one-day delay, then manual refresh remains available. Past events stay in history even when Roblox no longer returns them in the current listing.
This is the last observed Interested count, not actual attendance. If saving a new event could not be confirmed, check Roblox's list before retrying to avoid a duplicate.