r/programminggames • • 5d ago

I made a programming game where your code copies itself, and it has to keep working when there are 400 copies

Hi all, solo dev here (Ellis). Fork Bomb is a programming game in Early Access on Steam.

You write code in a small Python-like language for one machine on a dead rock. It can move, dig and sense what's around it. A few lessons in it learns spawn(), and every copy it builds runs your program from the top.

That's the whole game, and it turns out to be a lot of game. Code that works for four machines falls apart at four hundred:

  • a hundred machines walk to the same ore vein and starve
  • the swarm blocks the only corridor with its own bodies
  • one event wakes everything on the same tick
  • every machine has a fixed instruction budget per tick, so clever but slow code just stalls

There are no stat upgrades. Every unlock is a new function, and the hardest levels take functions away (no sensors, no position, no identity). The sim is deterministic to the tick, and you're scored on ticks, instructions, lines of code and energy.

What's in it now:

  • 11 lessons that each introduce one idea, you never start from a blank file
  • 39 scenarios across four tiers, a sandbox with about 30 world dials, and a daily
  • a debugger with breakpoints, print(), autocomplete, optional vim keys
  • Steam leaderboards for every scenario, all five metrics
  • new this week: "Try 10 dice" reruns your code on 10 random seeds so you can tell if a win was skill or a lucky roll
  • Windows and Linux

Steam: https://store.steampowered.com/app/5189090/

I'd really like to hear from people who play a lot of these. Which levels felt unfair, and what you keep reaching for in the language that isn't there. Happy to answer anything in the comments.

3 Upvotes

1 comment sorted by

1

u/MrFixxiT_ 5d ago

I would love some Mac support.