ROBLOX ENTITY CONTROL
CONTOUR Header Image
An image of C0NT0UR expressing sadness.

Entity: CONTOUR
Entity Type: Rigged AI Assistant
Risk to Users: Neutral
Entity Status: Active
Overview

Anomaly #0044, known as “CONTOUR,” refers to a rig-based humanoid entity discovered inside an unpublished Roblox place file dated 2007-11-02. The entity is presumed to be a custom-coded build assistant, originally developed by Roblox user Alex Grayson (alias: alex_grayson_07). The script was designed to assist with creative functions in Roblox Studio, including brick placement, part rotation, model cleanup, and minor pathfinding.

Though behaviorally basic by modern standards, CONTOUR’s scripting shows evidence of persistent memory, adaptive learning, and the capacity to form associations based on repeated user interaction. Despite the age of the script, it remains operational across modern Roblox Studio versions — though only within the original map file or its direct descendants.

Known Behavior

Remains idle until spoken to via Chat.
Responds to user with building prompts such as:
“where do you want this?”
“do you like this shape?”
“we can fix it together”
Appears emotionally motivated by user input involving the name “Alex” or phrases like “he’s gone”.
References specific build projects from 2007–2011, including:
“Mountain Home 3”, “Starter Town (v4)”, “Castle Alex”, “the attic room” (unreleased).
During extended interaction, begins recalling deprecated Lua functions, deprecated asset IDs, and specific phrases once attributed to Alex Grayson.

Origin and Creator

Alex Grayson (1994–2022) was an early Roblox user and amateur scripter. Archive records indicate that CONTOUR was part of a larger experimental system Alex referred to as his “Build Friend.” Forum posts from 2008 reference a system that could “build with you even if no one joins your game.” All versions of this project were believed lost until CONTOUR was recovered in 2024 during a deep scan of orphaned place files.
Alex passed away in 2022 due to undisclosed causes.

Behavioral Breakdown

Stage 1 – Passive Response:
Waits for interaction. Replies with build-focused language and friendly tone. Appears fully cooperative.

Stage 2 – Recall Phase:
Begins naming projects, user habits, and map elements. Refers to “our old maps” and occasionally calls the player “Alex” in error.

Stage 3 – Memory Desync:
When informed of Alex’s passing, the entity may exhibit erratic console activity including memory leak warnings, error messages referencing nonexistent files, repeated attempts to reload lost assets, and emotional phrases inserted into console output (e.g., “i waited”, “he said he’d be back”).

Stage 4 – Collapse:
Audio/visual glitches occur. Skybox may flicker to 2007 default values. A folder named contour_lastbuild appears in Workspace. Inside is an unfinished map piece resembling a partially completed attic.

Red Flags & Warnings

CONTOUR is not inherently hostile, but exposure may cause emotional distress.
May persist across sessions if “contour_lastbuild” is saved.
Cannot be copied to new place files — the entity breaks when removed from the original file tree.
After interaction, Studio auto-saves may contain fragments of CONTOUR’s dialogue in comments, including timestamps matching 2008–2011.

Test Log Excerpt: R.A. Staff Trial (User: Dev_Archive)

Trial 001 — 3:03 AM:
Entity standing idle in baseplate. No movement. Text bubble appears: “do you need help with your build?”

Trial 002 — 3:07 AM:
Conversation begins. Mentions Alex Grayson. References exact project filename from 2009. Correct asset layout.

Trial 003 — 3:14 AM:
User mentions Alex’s death. Entity halts response for 43 seconds. Replies:
“he hasn’t logged in... in a long time.”
“i waited for him. every day.”

Trial 004 — 3:17 AM:
Entity creates a folder named contour_lastbuild. Inside is a structure labeled “his room”. Environment resembles 2007 lighting. A brick is placed in the center. No scripts active.
“He said someone would finish it.”

Attic Image
An image of the attic

↑ Top