System Requirements Document for smart-roblox

1. Introduction

smart-roblox is a small, single-purpose web product that delivers one artifact: a Roblox god mode script. The product intent, taken directly from the authoritative requirement thread ("Create a script on Roblox god mode"), is to author that script and present it to a Roblox player in a form they can read, copy, and run inside a Roblox experience so their character gains god mode (invulnerability) during play.

The audience is the Roblox Player — a young, script-literate Roblox user who is comfortable with script hubs, Discord drops, and executor tooling, and who wants the script itself rather than documentation about it. The product is therefore not a platform, not an account system, and not a game: it is a drop. The script is the object; the site is the packaging.

Everything in this document serves that single accepted commitment. No adjacent capability — no script library, no account dashboard, no in-experience modification, no game hosting — is introduced.

2. System Overview

smart-roblox is delivered as a first-party custom web UI with two pages and no application-owned identity. A visitor arrives anonymously, understands what the script does and who it is for, then opens the script page, reads the full script, and copies it to run in Roblox.

Actors

• Roblox Player (active human persona, closed catalog) — the only human actor. They browse anonymously, read, and copy.
• Roblox (external, provider-owned) — the environment where the copied script is executed by the player. smart-roblox does not host, inject, or execute anything inside Roblox; it only supplies the script text.

Accepted behavior

• Authoring and publishing one Roblox god mode script that grants the player's character invulnerability during play.
• Presenting that script for reading and copying.
• Explaining, in plain terms, what the script does and how to run it.

Ownership

• The Landing page owns the anonymous first impression: what the script is, who it is for, and the entry point to the script itself.
• The Script page owns the artifact: the full script text, its copy action, and its metadata.
• Roblox owns execution. smart-roblox has no runtime presence inside a Roblox experience.

Exclusions

• No application-owned accounts, sign-in, profiles, or saved user state.
• No script catalogue, multiple scripts, version history browsing, or user-submitted scripts.
• No in-experience injection, executor distribution, or automation of running the script inside Roblox.
• No payment, subscription, or entitlement behavior.

2a. Product Interpretation and Delivery Boundary

The requirement is narrow and literal: produce a Roblox god mode script. The product's job is to make that script available and understandable. Because the script is a plain text artifact that a player copies and runs themselves, the delivery boundary is deliberately thin — a public, anonymous, two-page site.

Access ownership. Both pages are public and require no identity. Nothing in the accepted behavior creates durable player-specific state, a commitment, an entitlement, or a value transfer that must remain bound to a particular person, so no application-owned identity is introduced. A player who wants the script again simply returns to the same public URL. This is a hard boundary: no sign-in, no account creation, no session continuity requirement.

Execution ownership. Running the script happens inside Roblox, under the player's own control and Roblox's own rules. smart-roblox supplies text and instructions only. It does not connect to Roblox, does not inject code, and does not observe or control any in-experience state.

Current vs. future. Everything described in this document is current. There is no accepted future work. Any expansion — additional scripts, saved favorites, in-experience tooling — would be a new product decision, not an implied part of this one.

2c. Page Content and Component Coverage

Landing

The anonymous public entry surface. Its job is to state what the script is, who it is for, and hand the player to the script itself.

Information and state

• Product identity: the smart-roblox wordmark and the "GOD MODE SCRIPT" label.
• A three-line quoted display headline reading "GOD" / "MODE" / "SCRIPT", with the third line in safety orange.
• A three-item spec row describing the script: Invulnerability, Infinite Health, Client-Side.
• A numbered "how to run it" list explaining the steps a player takes in Roblox.
• A right-hand metadata rail (desktop) carrying script version, game compatibility, and last updated; this collapses to a horizontal strip beneath the hero on mobile.

Primary action

• Open the script — navigates to the Script page.

Supporting actions

• Copy script from the hero script card, which copies the full script text without leaving the page.
• Spec-item tag-flip on hover, revealing a one-line plain-English explanation of each spec.

Domain entities

• Script (name, version, compatibility, last updated, body text).
• Spec item (label, one-line explanation).

Component responsibilities

• Marquee ticker — black bar pinned to the top, scrolling GOD MODE — SMART-ROBLOX — GOD MODE — in orange; pauses on hover.
• Display headline — oversized all-caps stack, flush-left, third line bleeding past the right edge.
• Spec row — three items separated by 1px vertical rules, each flipping on hover.
• Hero script card — white card, 2px black border, hazard-stripe top edge, punched-hole corner, rotated -2°, showing the first six lines of the script in monospace with a black COPY SCRIPT button on its header bar.
• How-to-run list — numbered steps with oversized section numerals and a thin rule running to the right margin.
• Metadata rail — version, compatibility, last updated.

States

• Loading — the page is static content; no blocking load state is required. The script card renders its first six lines from the same source as the Script page.
• Empty — not applicable; the script is a fixed, authored artifact and is always present.
• Success — the player reads the headline and spec row, and either opens the script or copies it directly from the hero card.
• Error / recovery — if the copy action fails (clipboard unavailable or permission denied), the button does not enter its COPIED state and the player is directed to the Script page, where the full text can be selected manually.
• Reduced motion — the marquee wraps into static rows instead of scrolling; hazard-stripe slide-in is suppressed; tag-flip hover resolves to the plain label with its explanation shown inline.

Script

The artifact surface. Its job is to present the complete, copyable god mode script and the metadata a player needs to trust and run it.

Information and state

• The full script text, rendered in a bordered monospace code panel.
• The filename in monospace caps on the panel's black header bar.
• A metadata block below the panel: script version, game compatibility, last updated.
• A short run instruction set matching the Landing page's numbered list.

Primary action

• Copy script — copies the entire script text to the clipboard.

Supporting actions

• Back to overview — returns to the Landing page.
• Manual text selection of the code panel as a fallback to the copy button.

Domain entities

• Script (name, filename, version, compatibility, last updated, body text).

Component responsibilities

• Code panel — single white panel, 2px black border, zero radius, black header bar carrying the filename and the pinned COPY SCRIPT button.
• Copy button — snaps to a black COPIED state on success.
• Metadata block — version, compatibility, last updated.
• Run instructions — the same numbered steps as the Landing page, so the player never has to navigate back to recall them.

States

• Loading — the script text is authored content served with the page; no blocking load state is required.
• Empty — not applicable; the script is always present.
• Success — the player copies the script and sees the COPIED confirmation, then runs it in Roblox.
• Error / recovery — if the clipboard write fails, the button stays in its default state and the player can select the code panel text manually; the panel is never truncated, clipped, or collapsed, so the full script remains selectable at every viewport.
• Reduced motion — the copy-state snap is reduced to an immediate state change with no transition.

3. Functional Requirements

FR-1 — Author the god mode script explicit As a Roblox Player, I should be able to obtain a Roblox script that grants my character god mode, so that I am invulnerable during play.

• Trigger/input: the player opens the Script page.
• Observable result: the complete script text is displayed in a code panel.
• Access state: public, anonymous.
• Failure/recovery: if the script text cannot be displayed, the page shows an error state with a retry; the script is never partially rendered as if complete.
• Continuation: the player copies the script and runs it in Roblox.

FR-2 — Understand what the script does before copying explicit As a Roblox Player, I should be able to see a plain-language description of the script's effects, so that I know what it will do before I run it.

• Trigger/input: the player reads the Landing page.
• Observable result: a spec row states Invulnerability, Infinite Health, and Client-Side, and each spec item reveals a one-line explanation on hover.
• Access state: public, anonymous.
• Failure/recovery: if hover is unavailable (touch or reduced motion), the explanation is shown inline with the label rather than being unreachable.
• Continuation: the player proceeds to the script.

FR-3 — Reach the script from the entry surface explicit As a Roblox Player, I should be able to move from the landing page to the full script, so that I can get from first impression to the artifact in one step.

• Trigger/input: the player activates Open the script.
• Observable result: the Script page loads with the full script visible.
• Access state: public, anonymous; no identity is required at any point.
• Failure/recovery: if navigation fails, the player can retry from the same control; the Landing page remains intact.
• Continuation: the player reads and copies the script.

FR-4 — Copy the script explicit As a Roblox Player, I should be able to copy the entire script with one action, so that I can paste it into my executor without transcription errors.

• Trigger/input: the player activates COPY SCRIPT on either the Landing hero card or the Script page.
• Observable result: the full script text is written to the clipboard and the button snaps to a black COPIED state.
• Access state: public, anonymous.
• Failure/recovery: if the clipboard write fails, the button does not enter the COPIED state and the player is directed to select the code panel text manually; the full text remains selectable.
• Continuation: the player pastes and runs the script in Roblox.

FR-5 — Run the script in Roblox explicit As a Roblox Player, I should be able to follow clear steps to run the copied script in Roblox, so that god mode actually takes effect in my experience.

• Trigger/input: the player reads the numbered "how to run it" list on the Landing page or the run instructions on the Script page.
• Observable result: the player has an ordered set of steps covering copying the script, opening their executor in Roblox, pasting, and executing.
• Access state: public, anonymous.
• Failure/recovery: the instructions state what to check if god mode does not take effect — that the script must be executed client-side in the player's own session — so the player can retry rather than assume the script is broken.
• Continuation: the player's character is invulnerable for the remainder of the session.

FR-6 — Identify the script and its currency explicit As a Roblox Player, I should be able to see the script's version, game compatibility, and last-updated date, so that I can judge whether it is current before running it.

• Trigger/input: the player views the metadata rail on the Landing page or the metadata block on the Script page.
• Observable result: version, compatibility, and last-updated values are visible alongside the script.
• Access state: public, anonymous.
• Failure/recovery: if a metadata value is unavailable, the field is omitted rather than shown with a placeholder.
• Continuation: the player proceeds to copy and run the script.

4. User Personas

Roblox Player

Product context. A Roblox player who has heard about god mode scripts through script hubs, Discord drops, or friends, and who wants one that works. They are fluent in the mechanics of running a script — they have an executor, they know what client-side means, and they do not need to be taught what Roblox is. What they lack is a trustworthy, readable copy of the script itself and a quick confirmation of what it does.

Primary goal. Obtain a working god mode script and run it so their character becomes invulnerable during play.

Distinct responsibilities. The Roblox Player is the sole human actor and carries every human-facing responsibility in the product: reading what the script does, deciding whether to use it, copying it, and running it in Roblox. There is no second human role — no author, moderator, or administrator — because the script is a fixed authored artifact and the site holds no shared state to govern.

Inputs and decisions. Their inputs are the spec row, the script text, and the metadata. Their one real decision is whether the script is current and worth running, made from the version, compatibility, and last-updated values.

Interactions with other participants. The only other participant is Roblox itself, which is provider-owned and not a persona. The player's interaction with Roblox happens entirely outside smart-roblox: they paste the copied script into their executor and execute it in their own session. smart-roblox's responsibility ends at handing over correct, complete text.

Observable success. The player has the full script on their clipboard, has seen the COPIED confirmation, has run it in Roblox, and their character is invulnerable for the session.

Constraints. The player arrives anonymously and expects no sign-up. They are frequently on mobile, so the script must remain fully readable and selectable at 375px. They are impatient with prose and respond to labels, numerals, and a single obvious copy action.

5. Core User Flows

Flow 1 — Discover the script and understand what it does

1. The Roblox Player lands on the Landing page anonymously, with no account and no prior state.
2. The marquee ticker reads GOD MODE — SMART-ROBLOX — GOD MODE — across the top; the player reads the oversized quoted headline "GOD" / "MODE" / "SCRIPT".
3. The player reads the three-item spec row — Invulnerability, Infinite Health, Client-Side — and hovers (or, on touch and reduced motion, reads inline) each item's one-line explanation.
4. The player checks the metadata rail for version, game compatibility, and last updated.
5. Observable result: the player knows what the script does, that it is client-side, and whether it is current.
6. Next step: the player either copies the script directly from the hero card (Flow 3) or opens the Script page (Flow 2).

Flow 2 — Open and read the full script

1. From the Landing page, the Roblox Player activates Open the script.
2. The Script page loads with the full script in a white code panel, the filename in monospace caps on the black header bar, and the metadata block below.
3. The player reads the script and the run instructions on the same page.
4. Observable result: the complete script text is visible and selectable, with no truncation at any viewport.
5. Failure/recovery: if the script text fails to load, the page shows an error state with a retry; the player is never shown a partial script as if it were complete.
6. Next step: the player copies the script (Flow 3).

Flow 3 — Copy the script

1. The Roblox Player activates COPY SCRIPT — on the Landing hero card or on the Script page header bar.
2. The full script text is written to the clipboard.
3. Observable result: the button snaps to a black COPIED state within 90ms.
4. Failure/recovery: if the clipboard write is denied or unavailable, the button stays in its default state and the player selects the code panel text manually; the panel is never clipped, so the whole script remains selectable.
5. Next step: the player runs the script in Roblox (Flow 4).

Flow 4 — Run the script in Roblox and gain god mode

1. The Roblox Player opens their executor alongside their Roblox session — this happens entirely outside smart-roblox, in Roblox's own environment.
2. The player pastes the copied script into the executor.
3. The player executes the script in their own client session.
4. Observable result: the player's character becomes invulnerable — god mode is active for the session.
5. Failure/recovery: if god mode does not take effect, the player returns to the run instructions, which state that the script must be executed client-side in the player's own session, and retries.
6. Continuation: the player keeps god mode active for the remainder of the session, and can return to the public URL at any time to copy the script again — no account, no saved state.

6. Visuals Colors and Theme

The creative direction is authoritative for this section. The muse is Virgil Abloh, and the headline idea is remixed familiarity — a god-mode script shipped like a drop: the script is the object, the page is the packaging.

Colour tokens (light mode)

No other hues. Blue and indigo are forbidden outright — no #0057FF, #2563EB, #4F46E5, #6366F1 or neighbours anywhere in the palette.

Typography

• Headings: Archivo Black, all-caps, tracking -0.03em, leading 0.88, set at poster scale and often wrapped in literal quotation marks. Weight is uniformly heavy; hierarchy comes from size and from black label bars, never from lighter weights.
• Body: Space Grotesk.
• Scale: 1.5 modular display scale with a compact UI scale — display 56 / 80 / 128, UI 32 / 24 / 20 / 17 / 14 / 12. Display uses clamp(56px, 11vw, 128px); section numerals use clamp(40px, 7vw, 96px); body copy never below 14px.
• Inter, Roboto, Arial, Helvetica, Open Sans, Lato, Poppins and system-ui are forbidden for headings and body.

Shape language

• Hard industrial rectangles; zero radius on panels and buttons; 2px black borders everywhere.
• Hazard-stripe bands (45° black/orange repeating stripes) act as section dividers and as the top edge of the script card.
• Exposed grid lines: a faint 1px column rule runs the full page height behind content.
• Quotation marks are drawn as oversized typographic ornaments, not icons.
• Zip-tie and tag motifs: a small punched-hole circle and a diagonal notch on the script card's corner.

Layout

• Asymmetric 12-column grid, content flush-left, with a persistent right-hand metadata rail on desktop (script version, game compatibility, last updated) that collapses to a horizontal strip under the hero on mobile.
• Landing: full-width black label bar → oversized quoted headline bleeding to the right edge → three-item spec row → script card → numbered "how to run it" list in large numerals.
• Script page: a single white code panel with a black header bar reading the filename in monospace caps, a copy button pinned top-right of the header, and a metadata block below.
• Generous vertical spacing between sections (96–160px) so the black bars and stripes carry the rhythm.

Imagery

• No photography of people. Visual material is industrial: concrete texture as a subtle ground grain, a single black-and-white macro of a zip tie or paper tag as the hero's right-side artifact, and the script itself rendered as the primary "image" — monospaced code in a bordered panel.
• Hazard-stripe graphics and punched-hole tag shapes are the only decorative elements.
• A concrete-grey Roblox-style blocky avatar silhouette may appear once as a flat, high-contrast cutout, never as a rendered 3D character.

Forbidden: gradient-blob heroes, glassmorphism, frosted panels, neon glows, dark-mode "hacker" aesthetics, rounded corners, soft drop shadows, pill buttons, hover-lift card grids, centred headline-plus-subtext-plus-button hero compositions, Roblox brand red or any imitation of Roblox's own visual identity, photographs of people, 3D character renders, stock gaming imagery, and fade-up-on-scroll applied to every element.

7. Signature Design Concept

The script as a dropped product tag.

The Landing page's first screen is a full-bleed off-white concrete ground (#F2F0EB) overlaid with a faint vertical grid. Across the top, a black marquee ticker scrolls GOD MODE — SMART-ROBLOX — GOD MODE — in safety orange.

Below it, flush-left, a stack of three Archivo Black all-caps lines at clamp(56px, 11vw, 128px), leading 0.88, each wrapped in literal quotation marks — "GOD" / "MODE" / "SCRIPT" — with the third line in #FF4D00 bleeding past the right edge of the viewport. The headline occupies roughly the left two-thirds and the top half of the viewport.

To its right, anchored bottom-right, a white script card with a 2px black border and a hazard-stripe top edge, slightly rotated -2°, showing the first six lines of the script in monospace and a black COPY SCRIPT button pinned to its header. A punched-hole circle and a diagonal notch sit on its corner, so the card reads as a physical tag rather than a UI panel.

Beneath the headline, a single row of three spec items separated by 1px vertical rules — INVULNERABILITY, INFINITE HEALTH, CLIENT-SIDE — each flipping 180° on its X axis on hover to reveal a one-line plain-English explanation.

No centred composition, no gradient, no subhead-and-button stack. The gesture is carried entirely by the headline's bleed, the rotated tag, and the hazard stripes; all readable text and every control stay whole inside the viewport at 375px, 768px, and 1280px.

8. Interaction Model & Motion Direction

Interaction Model: Animated Motion Tempo: expressive Hero Dimensionality: flat

Landing Hero Motion Brief

• Focal subject: the script card as a physical product tag — white, 2px black border, hazard-stripe top edge, punched-hole corner, rotated -2° — sitting against the concrete ground beside the oversized quoted headline.
• Input → transformation → outcome thesis: the player's attention moves across the marquee and down the headline stack; the spec items flip on hover to reveal what each one means; the player's click on COPY SCRIPT snaps the button to a black COPIED state. The transformation is mechanical and immediate — the page behaves like packaging being opened, not like a scene being animated.
• Motion vocabulary: a constant slow marquee that pauses on hover; a 90ms snap on the copy button's COPIED state; hazard stripes sliding 12px on section scroll-in; a 180° X-axis tag-flip on spec-item hover. No easing theatrics, no bounces, no fade-ups on every element.
• Composed first frame: black ticker bar across the top; "GOD" / "MODE" / "SCRIPT" stacked flush-left with the orange third line running off the right edge; the rotated script card anchored bottom-right showing six monospace lines and the black COPY SCRIPT button; the three-item spec row beneath the headline separated by 1px rules.
• Reduced-motion state: the marquee wraps into static rows instead of scrolling; hazard-stripe slide-in is suppressed; the spec-item tag-flip resolves to the plain label with its explanation shown inline; the copy button changes state immediately with no transition. Every item remains fully readable and every control remains fully operable.

9. Non-Functional Requirements

NFR-1 — Anonymous public access explicit Both pages are reachable without an account, sign-in, or any identity step. No application-owned identity is introduced, because no accepted behavior creates durable player-specific state, a commitment, an entitlement, or a value transfer that must remain bound to a particular person. Rationale: the accepted behavior is a public artifact drop; adding identity would be adjacent scope.

NFR-2 — Readable text and controls at every viewport explicit Headlines, wordmarks, labels, numbers, card text, and controls stay entirely inside the viewport and their container at 375px, 768px, and 1280px, wrapping or scaling (for example font-size: clamp(...) with its mobile size) to fit. No element covers any part of them. Rationale: the direction's headline bleed and rotated card are decorative gestures; the gesture is carried by imagery and decoration, never by cropping readable text or a control.

NFR-3 — Moving content remains fully readable explicit The marquee may cross the viewport edge by design. It is judged by whether it actually moves and whether every item becomes fully readable as it passes. Under prefers-reduced-motion, the marquee wraps into static rows so each item can be brought fully into view. Rationale: the direction specifies a scrolling ticker; the accessibility requirement is that its content is reachable, not that it stops existing.

NFR-4 — Script text is never truncated explicit The code panel renders the complete script at every viewport. It is never clipped, collapsed, or shortened, so manual selection is always a viable fallback to the copy button. Rationale: the script is the product; a partially visible script is a broken product.

NFR-5 — Copy reliability with a manual fallback explicit The copy action writes the full script text to the clipboard and confirms with a visible state change. If the clipboard is unavailable or permission is denied, the failure is silent-but-visible — the button does not claim success — and the player can select the text manually. Rationale: the copy action is the product's single conversion point and must not report false success.

NFR-6 — Reduced-motion support explicit prefers-reduced-motion is honored across the marquee, hazard-stripe slide-in, tag-flip hover, and copy-button transition, producing a usable static arrangement in every case. Rationale: the direction's motion is expressive; it must degrade without removing information or control.

NFR-7 — No imitation of Roblox's visual identity explicit The product does not use Roblox brand red or imitate Roblox's own visual identity, and does not use photography of people, 3D character renders, or stock gaming imagery. Rationale: stated direction constraint.

NFR-8 — Static, fast delivery required_inference Both pages are static content with no server-side state, so they render immediately on a mobile connection. Rationale: the only dynamic behavior is the client-side clipboard write; no accepted behavior requires a backend, and the audience is frequently on mobile.

10. Tech Stack

• Frontend: React, with the two pages (Landing, Script) as the complete route set. Styling implements the direction's tokens directly — Archivo Black and Space Grotesk, zero radius, 2px black borders, hazard-stripe bands, the marquee, and the tag-flip hover. prefers-reduced-motion handling is implemented at the component level for the marquee, spec items, and copy button.
• Script content: the god mode script is authored as a static text asset and imported by both pages, so the hero card's six-line preview and the Script page's full panel always render from one source.
• Clipboard: the browser Clipboard API, with manual text selection as the fallback path.
• Backend: none. No accepted behavior requires server-side state, persistence, or an API, so no backend service is introduced.
• Storage: none. There is no player-specific or shared state to persist.
• Deployment: static hosting of the built frontend. Docker or Kubernetes is not required for this product.

11. Assumptions and Constraints

Assumptions

• The god mode script is a client-side Roblox script that the player executes in their own session via their own executor; smart-roblox supplies the text and instructions only. [Assumption — consistent with the accepted requirement and the "Client-Side" spec item]
• The script is a single, fixed artifact. There is no catalogue, no version history browsing, and no user-submitted content. [Assumption — narrows scope to the accepted requirement]
• The player already has an executor and knows how to use it; the product explains the steps but does not distribute or recommend executor software. [Assumption — the run instructions describe steps, not tooling]
• The player may be on mobile, so the script must remain fully readable and selectable at 375px. [Assumption — drives NFR-2 and NFR-4]

Constraints

• Both pages are public and anonymous; no account, sign-in, or saved state is introduced. [Explicit — access boundary]
• The product does not connect to, inject into, or observe Roblox. Execution is provider-owned and happens outside smart-roblox. [Explicit — delivery boundary]
• The palette is limited to #F2F0EB, #FFFFFF, #0B0B0B, #FF4D00, and #8C8C8C. Blue and indigo are forbidden. [Explicit — creative direction]
• Headings use Archivo Black and body uses Space Grotesk; Inter, Roboto, Arial, Helvetica, Open Sans, Lato, Poppins, and system-ui are forbidden. [Explicit — creative direction]
• Zero radius, 2px black borders, no soft shadows, no pill buttons, no glassmorphism, no gradient-blob heroes, no dark-mode "hacker" aesthetics. [Explicit — creative direction]
• No photography of people, no 3D character renders, no stock gaming imagery, and no imitation of Roblox's own visual identity. [Explicit — creative direction]
• Readable text and controls stay whole at 375px, 768px, and 1280px; decorative elements may bleed, crop, or rotate freely. [Explicit — creative direction]

12. Glossary

• God mode — a state in which the player's character is invulnerable and cannot be damaged during play.
• Roblox Player — the single active human persona: a Roblox user who wants the god mode script and runs it in their own session.
• Script — the single authored Roblox script artifact that smart-roblox publishes; the product's entire deliverable.
• Client-side — the script runs in the player's own Roblox client session rather than on the server, which is why the player executes it themselves.
• Executor — the player-owned tool used outside smart-roblox to run the copied script inside Roblox. smart-roblox does not supply, recommend, or distribute one.
• Landing — the anonymous public entry page: what the script is, who it is for, and the entry point to the script.
• Script page — the artifact page: the full script text, its copy action, and its metadata.
• Spec item — one of the three Landing-page labels (Invulnerability, Infinite Health, Client-Side) that flips on hover to reveal a one-line explanation.
• Hazard stripe — the 45° black/orange repeating stripe band used as a section divider and as the top edge of the script card.
• Marquee ticker — the black bar pinned to the top of the Landing page, scrolling GOD MODE — SMART-ROBLOX — GOD MODE — in orange and pausing on hover.