Death Order: Simon Says is a Roblox survival experience in the platform's own "1 vs All" sub-genre, from Voxq Enterprises, a verified Roblox group. Every figure on this page comes from Roblox's own public API rather than a tracker's paraphrase, and each one is stamped with the moment we read it. At 13:40 UTC on August 17, 2026 the game held 8,845 players in game and had logged 35,273,309 lifetime visits.
Live Snapshot
Read directly from Roblox's own public endpoints at 13:40 UTC on August 17, 2026, for universe 6324644175 (root place 18666738837). These are raw platform fields, not estimates. Both links open the live JSON, so you can re-run our reading yourself rather than take our word for it — the numbers will have moved on since we read them, which is the point:
games.roblox.com/v1/games— players in game, visits, favourites, created and updated dates, live title.games.roblox.com/v1/games/votes— the up and down vote counts behind the approval figure.
Live title at reading: Death Order: Simon Says · Developer: Voxq Enterprises (Roblox group 7015605, verified badge) · Universe 6324644175, root place 18666738837.
Background
Death Order: Simon Says launched on July 26, 2024, per the created field on Roblox's own API, and the platform's most recently recorded developer update was August 17, 2026 at 05:30 UTC — hours before this reading. The developer's own description opens with "Daily Updates" followed by "Game is new so there will be a lot of bugs please report them in our community server." That framing sits oddly next to a created date now more than two years old and a lifetime-visit count above 35 million — we surface the mismatch rather than resolve it, since nothing in the description says what "new" is actually meant to describe. We do not have a first-party sourced date for when the code system started, so we do not print one here; see the codes page for what the trackers do, and do not, agree on.
How the Game Works
Death Order: Simon Says drops players into a prison with no memory of how they got there, per the developer's own description. Survival means obeying Simon's orders only when they are prefixed "Simon Says" — get a command wrong, in either direction, and you are eliminated. The description frames the loop in three lines: "Follow Simon's Orders," "Survive the Events," and "Be the Last Standing." That is the extent of what the developers state first-party. We have not played the game, and we are not going to describe what the in-game events actually consist of, how eliminations are enforced, or what happens after outlasting everyone else — the description does not say, and we are not filling the gap with assumptions borrowed from other Simon Says or elimination games.
Official Channels
Where to go for first-party information. We link these without nofollow because we have checked them and stand behind them, unlike the third-party trackers we cite on the codes page.
- Death Order: Simon Says on Roblox — the game itself, and the description field most of this page is sourced from.
- Voxq Enterprises — the verified developer group behind the game.
The description also points players to "our community server" for bug reports, but gives no URL, so we are not linking one we have not verified ourselves. The raw API endpoints behind our figures are linked in the Live Snapshot section above rather than here, because they are a verification tool rather than somewhere a player would go.
Death Order Guides
Death Order: Simon Says Codes (August 2026)
Source-listed Cash signals, a single-source caution on one new string, and the trio of moderator-name codes that has moved to expired.
Codes
Death Order: Simon Says has an active set of source-listed Cash codes, redeemed through the Cash icon on the left side of the screen. We treat every code as a dated signal rather than a confirmed working code — full detail, the single-source caution on one new string, and the expiry note on three moderator-name codes are on the codes page.
Go to Death Order Codes →
Source-listed signals, one single-source caution, and a dated source list.
Update Rule
We do not mark a code as active just because another page says it is active, and we do not quote a player count without saying when we read it. This page records what was checked, when it was checked, and where the evidence runs out.