Data page · Roblox event
Steal An Egg monster update
Data pageLast checked
Roblox's own virtual-events API — not a third-party report — confirms a real event, "MONSTERS ARE COMING...", hosted by Steal An Egg's own developer group, running to . The event's own description says "Giant creatures" are emerging and that "The Monster Update arrives this weekend" — future tense. We check the one thing that would prove that update had already shipped regardless of wording: whether a new badge has appeared in the Roblox Badges API. As of our last check, none has — consistent with the event's own "arrives this weekend" wording, not a gap in our data.
Live status: has the monster update shipped anything checkable yet?
Reads the virtual-events, Games, and Badges APIs directly, cached at the edge for 5 minutes. This is a snapshot at the moment we fetched it, not a continuous poll — the timestamp below is exactly how stale it is. The event status row below reads Roblox's own field live rather than assuming it is still running.
<1m ago
this snapshot is a point-in-time read, not a live poll — press "Check again" for a fresh one
Re-reads all three endpoints now instead of waiting for the cache.
| Signal | Value | Source |
|---|---|---|
| Event status (Roblox `eventStatus`) | Active (read live from Roblox's own eventStatus field) | |
| Event window (UTC) | → | |
| Games API `updated` field | ||
| Concurrent players | 1,615,530 | |
| Favorites | 1,291,082 | |
| Main game description mentions "monster"/"creature" (event object's does) | No | |
| New badges since the event started | 0 | |
| Event host matches game's own creator id | Yes — host 825735094 = creator 825735094 |
Confirmed vs. not yet published
Everything the event object itself establishes, next to what players are searching for that nobody — including us — has confirmed yet.
Confirmed, official source
- Event exists, titled "MONSTERS ARE COMING...", subtitle "Something has awakened." — the host group matches the game's own creator id (checked live above), so this is the developer's own event object
- Window: 2026-08-29T15:00:56.774+00:00 → 2026-08-30T15:00:56.774+00:00, ~24 hours
- Official description, verbatim: "Strange sightings have been reported across the world. Giant creatures are beginning to emerge... and this is only the beginning." followed by "Prepare yourself. The Monster Update arrives this weekend" — future tense, not a claim that it has already shipped
- Information Gain: the event object's own description names "Giant creatures"; the main game listing's description does not mention monsters or creatures at all as of our last check — two official Roblox surfaces for the same game, disagreeing on whether to mention the event at all
- Games API `updated` moved to 2026-08-29 — confirms the developer pushed some change on or near the event's start date; the field does not say what changed
Not yet published, as far as we found
- Monster names or how many exist
- What a monster does, or how a player interacts with one
- Any new pet, egg, biome, mutation, or size tied to this event
- Any reward, drop, or currency change
- Whether the content is permanent or time-limited
- Any redemption code tied to the event
- Player interest count — the event object does not expose a "going" figure, and we do not cite the two secondary write-ups' conflicting unverifiable numbers for it
This list is a documented absence, not a guess: no source we reviewed — including the event object itself — names any of these. We will move an item out of this column the same day we can cite it against a live endpoint or a primary source.
New badges since the event started
A new badge is the strongest evidence available that new content shipped: it is server-defined by Roblox and cannot be faked by a thumbnail or description edit. Every badge below carries its own created timestamp from the Badges API.
No new badge yet. All 6 badges in the universe still carry a `created` date before the event's own start time, read directly from the Badges API — consistent with the event object's own "arrives this weekend" wording. If a badge tied to the monster update appears, it will show in the table below and in the live count above the same day we check.
| Badge | Created | Awarded | Past 24h |
|---|---|---|---|
| Angelic Treadmill! | 200,928 | 56,524 | |
| Divine Trail! | 768,287 | 201,213 | |
| Hatched Divine! | 407,939 | 48,891 | |
| Hatched Secret! | 14,654,040 | 2,711,724 | |
| Hatched Eternal! | 9,049,333 | 1,630,731 | |
| WELCOME! | 68,961,454 | 7,720,299 |
Why we read three endpoints instead of one announcement
The virtual-events API gives the event's own record — title, window, official wording — first-party and unauthenticated, so there is no need to rely on a secondary write-up for that half of the page. But an event object can describe an update without that update having shipped, which is exactly what its own "arrives this weekend" phrasing says. What nobody outside Roblox can fake is a badge's created field: it is set server-side the moment a developer defines a new achievement, and the Badges API returns it for every badge in the game, same as our rarity page reads for the full roster. So this page tracks the one signal that would prove the announcement turned into shipped content, the same way our update log tracks the Games API's updated field for the site generally.
This is still a narrow instrument. It can say "the event exists, runs this window, and no badge has changed" — it cannot say what a monster does, how many exist, or whether the content will be permanent, because none of the three endpoints exposes that. We also do not cite a player-interest figure: the event object has no such field, and the two secondary write-ups we found disagree with each other on it without either linking a verifiable source.
Steal An Egg monster update FAQ
What is the Steal An Egg monster update?
The Roblox virtual-events API — a first-party, developer-published record, not a third-party report — lists an event for Steal An Egg titled "MONSTERS ARE COMING...", subtitle "Something has awakened.", hosted by group 825735094, the same group that owns the game (checked live against the Games API's `creator.id` on every page load). Its description reads, verbatim and in two paragraphs: "Strange sightings have been reported across the world. Giant creatures are beginning to emerge... and this is only the beginning." followed by "Prepare yourself. The Monster Update arrives this weekend" — no closing punctuation in the original, and that second sentence is future tense: the event announces an update, it does not itself claim to be the update.
When does the Steal An Egg monster update start and end?
Per the virtual-events API, `eventTime.startUtc` is 2026-08-29T15:00:56Z and `endUtc` is 2026-08-30T15:00:56Z — an almost exactly 24-hour window. That resolves an earlier disagreement between two third-party write-ups over the exact start minute; the official record settles it at 15:00:56 UTC (11:00 AM ET).
What new monsters, pets, or rewards has the update added?
Nothing we can confirm as of our last check. The event object itself names no specific monster, mechanic, or reward — only "Giant creatures", unnamed. We check the Roblox Badges API directly, since a new badge is the strongest evidence available that new content shipped, and as of our latest read every badge still carries its original 2026-07-25 creation date. Combined with the event description's own "arrives this weekend" wording, this reads as an announced-but-not-yet-shipped update, not an absence of information.
Has the monster update added a new badge?
Not as of our latest check. The live panel above reads the Badges API's own `created` timestamp for every badge in the game. A badge created on or after 2026-08-29 would show here the same day it appears; none has yet.
Does the monster update add codes or a redeem system?
Nothing we found claims it does. Steal An Egg has no confirmed redeem-code system as of our last check (see /codes), and the event object itself makes no mention of one.
Is the monster update still running right now?
Check the live panel above — it reads Roblox's own `eventStatus` field on every page load rather than stating a fixed answer, because the announced window (2026-08-29T15:00:56Z to 2026-08-30T15:00:56Z) is short enough that this answer changes within the same day the page was published.
Related pages
Update log
Every dated reading of the Games API `updated` field for the game generally, not just this event.
Rarity data
Every pre-event badge and how many players hold each, from the same Badges API this page watches for a new one.
Codes
Whether Steal An Egg has a redemption system at all — relevant if the monster update turns out to add one.
Wiki homepage
Live player count, favourites, and the rest of what the Games API exposes for Steal An Egg right now.
Sources for this page
Every figure above comes from one of these. Anything not derived from them is not on this page.
| Source | What it gave us | Seen |
|---|---|---|
| Roblox virtual-events API: event id 4700307205033952014, title, description, eventTime, eventStatus | The event window, official description, status row, and the "Giant creatures" quote | 2026-08-30 |
| Roblox Games API: `updated`, `playing`, `favoritedCount`, `description` | The live status table and the "description mentions monsters" check | 2026-08-30 |
| Roblox Badges API, complete list, each row's `created` field | The new-badges table and the confirmed-new-badge count | 2026-08-30 |