Death Order Simon Says Game Profile and FAQ

Death Order: Simon Says is a Roblox survival experience published by the verified group Voxq Enterprises. Roblox classifies it as Survival and 1 vs All. Its developer-written premise asks players to follow valid Simon Says orders, survive Events, and become the last player standing.

This profile records stable identifiers separately from changing platform statistics. That distinction makes it easier to confirm you have the right experience without turning a temporary player count or store state into a permanent fact.

Official identity and identifiers

The place ID identifies the root place players open. The universe ID identifies the wider Roblox experience used by APIs for game metadata, badges, thumbnails, and passes. Both IDs refer to the same official experience in this verification.

What the official description confirms

The developer-published description establishes the basic loop:

• follow an order only when Simon says Simon Says first;
• survive Events;
• avoid a wrong response, which the description says results in death;
• aim to become the last player standing.

Those statements define the premise without publishing every implementation detail. The official description does not provide a full command dictionary, a complete Event roster, a reaction-window table, or a permanent safe-area guarantee.

New players should continue with the beginner survival guide, which turns the confirmed premise into a cautious first-session routine.

Stable facts versus live snapshots

The title, place-to-universe mapping, and recorded creation timestamp are relatively stable identifiers. Other values can change whenever Roblox or the developer updates the experience.

Treat these as snapshots:

• server capacity;
• genre and subgenre labels;
• game-pass price and sale state;
• badge enablement;
• visits, favorites, votes, and concurrent player counts;
• creator-group membership totals.

This page records the server capacity and classifications because they came from the official Games API on the verification date. It deliberately does not freeze changing engagement totals into the article body. A live number is useful only when paired with a timestamp.

The sources and verification method explains how this wiki labels time-sensitive facts and when multiple sources are required.

Creator and platform context

Roblox’s Games API attaches the experience to Voxq Enterprises, and the official group endpoint confirms the group record. “Verified” here refers to the Roblox group identity connected to the experience. It does not make this independent wiki an official Voxq Enterprises publication.

The Survival and 1 vs All classifications describe the category Roblox returned on July 30, 2026. They do not supply hidden formulas, team rules, or player-role probabilities. Any guide that adds those details needs separate evidence.

Where to find checked game data

Different questions have different source paths:

• For command decisions, use rules and commands.
• For the enabled badge count and developer-written story clues, use the badges and lore catalog.
• For Robux pass records and community-reported cosmetic categories, use cosmetics and game passes.
• For reported code status and check dates, use the code page rather than an undated list.

This separation prevents a community code tracker, a player video, or promotional artwork from being treated as authority for the official game identity.

Verification record

The profile was checked on July 30, 2026 against the official Roblox experience page, the place-to-universe resolver, the Games API, and the Voxq Enterprises group endpoint. The root place resolved to universe 6324644175, and the returned creator identity matched Voxq Enterprises.

When a value is time-sensitive, this wiki presents the check date and avoids promising that it remains unchanged. When a detail is absent from first-party sources, the article labels it unknown instead of inferring it from the game’s theme or a pass name.