~ Uploaded test version (May 9th , 2026) - 2 days left of jam
~ Uploaded Jam version (May 10th, 2026) 1 day before submissions end , fixed pathing with end conditions.

~ DEADCLOCK ~

STORY:

You are an entry-level developer at a large corporate game studio… or at least, that’s what your contract says.

Your workstation is locked behind strict internal systems. Every action is monitored. Every delay is logged. Every inefficiency has a cost attached to it.

Performance deductions are real.

Rent is due next week.

And somehow… the stability of your build determines whether that happens or not.

The project is called DEADCLOCK.

A "controlled internal development environment built for deployment testing, workflow simulation, and system validation."

At least on paper.

But the system doesn’t behave like software anymore.
Policies update without version control.
And the environment feels less like a workspace… and more like something actively enforcing itself on you.

You don’t just develop the game.

You operate inside it.

And all you need is $300. Good grief...

STORY NOTE:

This is a jam build with limited scope. Only a small number of interactive text and narrative elements are present due to time constraints. Additional systems and story layers are planned post-jam.

CONTROLS:

Primary Interaction (Core Gameplay):

• Mouse: Navigate UI / interact with objects / select systems
• Keyboard (Typing): Input commands into terminals and systems
• E / Q: Context interaction (confirm / cancel depending on system prompt)

Movement (Context-Specific Sections Only):

• WASD or Arrow Keys: Used only in designated movement rooms (not global gameplay)*SPOILER: This is triggered during the 3D aspect of the game + snake levels*

FEATURES:

• Terminal-driven gameplay and command-based progression
• Corporate-style performance system tied to progression pressure

• Economy loop tied to “efficiency” and output
• Glitch events and unstable UI behavior

• Hidden progression paths tied to experimental systems
• Narrative fragmentation through environmental interaction

CREDITS:

Developer: CrypticTM

⚠️ NOTE:

This is a jam prototype build.

Some systems are intentionally incomplete, unstable, or experimental due to strict time constraints and scope limitations.

Certain interactions may result in unexpected behavior, transitions, or system instability as part of the intended experimental structure.

SPOILER: Command cheatsheet: ls , fix desync main drive, check mainframe (takes you to ending 1), check integrity, go past score of 10 in snake minigame for trigger event for ending two.