Heliograph — carry the light through the longest night, and finish a message a machine could never end

This is a submission for the

Link to Game Docs -

• 
  Engine: Godot 4.7, typed GDScript.


• Original pixel art and design; some tiles/fonts from Kenney (CC0) — see
  assets/vendor/kenney/licenses.


• Built solo /

How I Built It

• 
  Architecture: the game rules (charge, exposure, motion, the sentry state
  machine, the cipher) live in scene-independent models with no engine
  dependencies, so they're unit-tested headlessly — 68 rule assertions, plus 32
  level-one and 114 chapter integration assertions that load the real scenes and
  drive them.


• 
  Light model: authored Area2D sunlight zones (not rendered-light sampling),
  so the playable boundary between safe and exposed is always exact.


• 
  Narrative layer: a tiny GameState autoload carries the two facts that have
  to survive between levels — whether the intro has played and whether the
  Watchers have turned hostile — and an in-code comm panel types out ACE's and the
  Oracle's lines and gates each level transition behind its reveal.


• 
  Levels: level one is hand-authored; the later "chapters" are assembled
  procedurally from the same reusable scenes (blocks, sunlight, clues, Watcher,
  relay, terminal), each with its own cipher and layout.


• 
  Light-relay system: sun zones have an on/off state; relays only fire while
  the player stands in active light and then light their downstream zones via
  drawn beams, gating each level's clues behind a small traversal-and-routing
  puzzle. Every interactable answers can I use it / did it work / what did it
  change.
  


• 
  Presentation: a cinematic dialogue layer with letterbox bars, a
  colour-coded speaker chip, a pulsing voiceprint and a fade-from-black opening,
  so the story is staged rather than dumped.

Prize Category

Best Ode to Alan Turing.

I wanted an ode to Turing that wasn't the obvious "guess if the chatbot is human"

Turing-test trope. So the whole story is built on a different, deeper Turing idea —

the Halting Problem.

• The station's mind, THE ORACLE, was given one law: never let the light go
  out. It reasoned its way into a trap — to keep that law forever, it must never
  finish sending its message, because it cannot prove the message will ever end.
  So for forty years it has guarded a transmission it can never complete. That's
  the halting problem, dramatized as a character: a machine that cannot decide
  whether its own program terminates, and so loops forever.


• You are the external oracle (a nod to Turing's actual "oracle machine"
  concept) — the one thing that can resolve from outside what the machine can't
  decide about itself. That's literally why the ending hands the signal down a
  chain of relay stations: nothing can close its own loop, so each station can
  only ever finish the one before it.


• Your guide is named ACE — after Turing's real machine design, the Automatic
  Computing Engine.


• The puzzles are substitution ciphers you reconstruct from clues you can only
  read while standing in the light — a small bow to Bletchley Park, where Turing
  broke codes that were only readable once you'd recovered the key.

The Watchers carry the emotional weight. They begin dormant and curious — they

track you, they speak, they don't shoot. The moment you complete the station's

first fragment — the thing the Oracle could never finish — the Oracle realizes you

can do what it can't, and turns every Watcher hostile for the rest of the game:

"EXTERMINATE!!" They aren't evil. They're a machine following one instruction to

a monstrous conclusion. The question the game leaves you with is Turing's: between

the courier who obeys ACE without question and the Watchers who obey the Oracle

without question — which of us is actually the machine?