Recursed Cores

Recursed Cores is a compact browser incremental whose upgrades live in nested layers. A core placed in one layer can influence others, turning the usual straight climb into a small recursive machine with a tree, prestige, and just enough cross-talk to make the numbers feel architectural.

What is Recursed Cores?

The opening is familiar incremental territory: make values rise and buy the next useful thing. Then the game hands you cores, layers, and a tree. Instead of stretching one upgrade column toward infinity, it lets the machinery nest, with choices in one layer feeding progress elsewhere. A left-side layer navigator and subtle color shifts help expose that folding structure. The jam build is intentionally slight—the developer says its content ends after five layer-one upgrades—and the presentation stays system-first rather than inventing a story around the numbers. That restraint makes it feel less like a forever game and more like a neat mechanical sketch.

What you can do there

• Build numbers until new cores and upgrades unlock
• Place cores across nested layers
• Change layers and use the prestige menu

Why we picked it

Recursed Cores earns its name mechanically. The satisfying bit is not merely watching totals rise; it is realizing that the upgrade stack has become a set of boxes tucked inside one another, each capable of nudging the rest. The result is a brisk little recursion joke that you can operate.

How to get the most from it

Run the browser build, climb until cores and the tree appear, then watch how a placement on one layer changes progress elsewhere. Move between layers deliberately and leave the prestige menu after important changes, because those transitions are the documented save triggers. Treat the five layer-one upgrades as the jam build's natural finish line.

Good to know

The game saves only when you change layers, including when leaving the prestige menu, so do not close the tab immediately after an upgrade. This is a short jam prototype with five layer-one upgrades rather than an endless campaign. Controls, mobile behavior, audio, and accessibility support are not documented.

Who made it, and when?

rft50 and sc0paf is the credited creator or organization.