Scrapcode

You don't fly the drone. You write its code.

A derelict is drifting, and the hull is failing. You send a salvage drone in — but you never touch its controls. You write the program it will run, you press DEPLOY, and then you watch through the sensor feed while it does exactly what you told it to.

Which is rarely what you meant.

def run():
    while cargo_count() < 4:
        readings = scan()
        move_to(readings["scrap"][0])
        grab()
    return_home()
    while cargo_count() > 0:
        drop()


<p>That program works. It also loses the drone on the fourth wreck, because it fills the hold before checking whether there's still time to walk home.
</p>
<h3>The black box</h3>
<p>When a run goes wrong, drag the timeline. The mission replays from its recording, and the line of code the drone was executing is highlighted as you scrub. You don't guess what happened. You watch the exact moment your logic turned.
</p>
<p>It's the feature the whole game is built around — the machine that runs your program was written from scratch so it could be rewound.
</p>
<h3>Nine missions that teach, then get out of the way</h3>
<p>Every mission hands you a program that already runs and asks for one change. Nobody ever faces an empty editor.
</p>
<p>You start by pressing a button. You finish by budgeting a return trip against a failing hull — and then the generated wrecks open up, where the only limit is how good your program is.
</p>
<p>The language is a small subset of Python. Whole numbers only, no imports, no classes. If you've never written a line of code, mission one is four lines long and you don't have to type any of them.
</p>
<h3>Three ways to be better</h3>
<p>Every finished run is recorded against your best on three axes: salvage brought home, ticks taken, tokens written. A shorter program and a faster run pull against each other. Deciding which one matters is the game.
</p>
<h2>Features (liste à puces itch)</h2>
<ul><li>A real programming language, written from scratch — nine missions to learn it in
</li><li>A replayable black box: scrub any run and watch which line was executing
</li><li>Procedurally generated derelicts from shareable seeds
</li><li>Errors written for people learning to code, not for compilers
</li><li>Three-axis scoring: salvage, speed, program size
</li><li>No image or audio files. Every shape, colour and sound is generated by the game's own code
</li><li>Your programs are saved as plain text you can open, edit and back up
</li></ul>


<h3><span></span></h3>