Ship #1 Changes requested

@RedstoneStar on Root-Directive · 7 days ago

Root Directive
An immersive, interactive webOS simulator game featuring a custom terminal AI named Chadwick, built and published on Hack Club.

About the Project
Root Directive started as a fun side project designed to help me learn more about JavaScript and HTML. Building this project made me dive deep into custom UI components, virtual file system (VFS) architectures, and general programming, improving my web development skills along the way.

Quick Walkthrough
Here are the core steps to beat the game:

Desktop & Snapshot: Open the Welcome Window, drag the code image to the desktop, and open it in the Photo Diagnostics Tool to adjust brightness and contrast to reveal the first password (Admin_Lumina).

Memory & Registry: Use the password to unlock mem_pointer.txt, jump to the memory address in the System Memory Viewer to find the registry key, and use the terminal to uncover hidden vault cache files.

Jailbreaking Chadwick: Enter the 4-digit PIN in Vault Backups to get the relink instructions, jailbreak Chadwick, use the code to unlock sector_scan.log and get the complete Vault Code.

Cracking the Core: Retrieve the system launch date from the calendar logs, enter it into the memory viewer for hex fragments, and use the Hex Color Overlay in the image editor to generate your final vault code.

Final Override: Intercept network packets via the CommLink app, decode the Base64 payload, and unlock the final system parameters to win.

3 devlogs
12h
WebOS 1

Try project → See source code →

Open comments for this post

@RedstoneStar on Root-Directive · 7 days ago

37m 12s logged

Devlog #3

A few quick bug fixes before shipping the project.

Fixed issue where the user was able to access a file before they were supposed to. (Made the file password protected)
Fixed issue where the user was able to read a locked file through the terminal even if the file was locked.

Also added new icons for all of the apps.

Hopefully the project will run bug free now!

Open comments for this post

@RedstoneStar on Root-Directive · 7 days ago

5h 42m 29s logged

Devlog #2:

After 20-some hours of work, I realized that none of my work was being logged, sooo, that’s fun.

Since my last devlog, I’ve become more confident with JS and added several new apps and features.

New Terminal, Files, Memory Viewer, and CommLink app.
Greatly improved the logic for Chadwick
Expanded the game to have over 20 steps
3 new red herrings
New “Hex tool” in the image editing app.

I’m not very satisfied with the current steps in the game. I added them while programming new features without a clear plan, and the result is a fairly big mess.

Open comments for this post

@RedstoneStar on Root-Directive · about 2 months ago

5h 25m 45s logged

Dev-log #01: Root-Directive

Hello everyone!

I just started working on the webOS Jam and wanted to share my first dev log for my OS, Root-Directive.

Root Directive is an interactive, browser-based puzzle game designed to look and feel like a custom desktop operating system. The core gameplay requires the user to navigate the OS environment, use system diagnostics, and review config logs to piece together a 6-digit cryptographic code to access the central vault.

After working through the basics (top UI bar, background, etc), I got distracted and wanted to implement a chatbot that could help the user along their path to finding the password. So, Chadwick was born! I used AI to come up with robotic, smart-sounding responses. I then developed an EXTREMELY simple answer system that maps specific keywords (hello, thanks, hint, etc) to a list of responses that it randomly chooses from. Chadwick also keeps track of the past conversation so that if the user responds directly to something Chadwick says, it will know what the user was referring to.

It was definitely far too early to implement this; I don’t have a single clue or challenge in yet. I’ve just had the idea of a simple AI assistant in the back of my head for a long time and wanted to try it out.

Next steps:
With the core systems in place, it is time to start working on the actual puzzle.

-At very least 10 sequential steps to find the code
-5 non-sequential ones
-At least 2 hidden easter eggs
-Red-herrings?