October 19, 2026
Roblox Creator Showdown São Paulo: announce your start time
Roblox scheduled São Paulo’s Creator Showdown for 15 October 2026. Learn how to announce a clear start time and prepare your waiting scene in OBS.
On 14 October 2026, Roblox announced the São Paulo Creator Showdown (opens in a new tab), its third edition and first international one, scheduled for 15 October 2026 at 17:00 Brasília time. The announcement outlined eight Brazilian creators in four teams of two, five games, and Portuguese and English broadcasts. That advertised start time offers a useful starting point for thinking about how to present the wait before your own show.
Our proposal is to turn an announcement into a waiting scene that makes sense: what is about to happen, when it starts, and what viewers will see until then. This is an editorial recommendation for your channel, not a description of the tournament’s production or a claim that Roblox used a countdown.
What Roblox announced for São Paulo
Roblox announced a Portuguese feed on its Brazilian YouTube and TikTok channels, and an English feed on its official YouTube, Twitch and TikTok channels. The release assigned different hosts to each version but published one start time for the broadcast. Those announced broadcast plans are the reference for this article.
MultiAnime’s coverage from 17 October 2026 (opens in a new tab) also reported the announced format and schedule. We use it as coverage of the announcement, not as an account of what happened during the stream. The practical lesson below is how to turn a scheduled start into a visible wait on your own broadcast.
Why it matters to streamers
A published start time creates an expectation. Someone may open your channel before the show and find a wait with no context. Preparing that moment lets you explain what is about to begin without relying on viewers having read an earlier post or arriving exactly when the presenter appears.
The useful detail in the São Paulo announcement is the combination of a shared start time and two language versions. We do not need to know how the show was produced or reproduce its scale to identify a specific task: make the advance messages point to the same instant, even when each community reads it in its own time zone.
In a production with several feeds, agree on what that instant represents: the start of the pre-show or the start of the main programme. Two channels can open at different points beforehand and still announce the same beginning correctly. Avoid presenting two different deadlines as though they were the same start time.
The distinction helps a single channel too. If you begin broadcasting a waiting scene at 17:50 and advertise the show for 18:00, the countdown should point to the start of the programme. It is not saying when the feed opened; it shows the time remaining until the moment you communicated to viewers.
Announce a start time you can keep
The first decision is to choose one instant, not to design the counter. Write down the date, time and time zone, and keep that reference in the channel description, announcements and scene. You can display local equivalents, but they must refer to the same beginning. UTC is useful as a shared reference when your audience spans several countries.
In Roblox’s announcement, 17:00 Brasília time on 15 October 2026 is equivalent to 20:00 UTC. These are two ways of expressing the same instant, not two different scheduled starts. For your show, check the conversion before publishing and check it again if you change the date; do not reuse another stream’s conversion without verifying it.
Ask someone outside the project to check the time. A reference expressed only in your local zone can be confusing, especially around a seasonal clock change. Naming the reference city and using a twenty-four-hour clock can make the date easier to check without crowding the scene.
The second decision concerns the scene. During the wait, it should be clear what is going to happen, when the main programme starts, and that viewers are still watching the pre-show. A short message, the show’s name and the time are enough. If you add a countdown, tie it to the advertised deadline and check that the text and numbers are not communicating different starts.
Legibility is tested in the worst case, not the best one. Look at the scene on a phone, at a reduced size and with low brightness, and decide whether the message can still be read. A large counter with a thin typeface may look elegant on the editing monitor and disappear on the screen of a viewer who has just opened the channel.
The third decision is the transition. Prepare the content scene and rehearse the switch from the waiting scene using the controls you will use during the broadcast. If there is a delay, have a message ready and explain the revised plan. Silently changing the countdown’s deadline does not tell viewers why the programme has not started.
Also decide what you will do when the countdown reaches zero. Assign who removes it and who brings in the show, even if the same person does both jobs. If you are starting late, change the waiting message; if you start early, remove the countdown. Do not leave a fixed zero or a running timer contradicting what is already happening on screen.
Prepare the wait and test it before you go live
Before going live, run through the whole sequence: open the waiting scene, review the published time, return from another scene, and check the transition into the content. Look at the actual OBS output and check that an old message has not remained on screen. That rehearsal turns a calendar entry into clear information for someone who has just arrived.
To put that deadline on screen, choose a countdown template in OverlayOn, set the end date and time, and copy the URL to add it as a browser source in OBS. Customize the message to explain what begins when the wait ends, then review the result inside the scene you will actually use.
This lets you display the time remaining until your scheduled start alongside the show’s name, rather than leaving the time only in the channel description. Configure your countdown in OverlayOn and rehearse removing it as you move from the wait into the content.