Prestige and carryover

Prestige resets your workshop in exchange for currencies and permanent unlocks. Read what you keep and what you lose before confirming it.

Shared requirements

Complete Theory and reach rank 100 on all eight equipment types. After your first prestige, at least 60 online seconds must pass between confirmed prestiges. The first prestige has no interval requirement. Rank 100 is a requirement, not an upgrade cap.

The three prestige options

OptionExtra requirementRewardCurrencies clearedPermanent unlocks
RecompileNoneRuntimeShard +3NoneSecond region, helper classes, Persist, fourth golem slot
RebuildAt least 3 RuntimeShardWorldCore +1All RuntimeShardThird region, async/await, fifth golem slot
AscendAt least 1 WorldCoreAscensionSigil +1All RuntimeShard and WorldCoreKeeps unlocked regions

Recompile keeps WorldCore and AscensionSigil. Rebuild keeps AscensionSigil. Once a region is unlocked, later prestige does not lower it.

What stays and what resets

KeptReset
Spell text and settingsOrdinary stock and research points
Earned achievements and titlesCurrent-run research
Online time and permanent unlocksEquipment upgrades and additional golems
Persist fields directly on Program and their reachable stateOrdinary Program fields and execution continuations

Initial equipment returns to rank 1 and ownership returns to one golem. Keeping your spell does not mean keeping every variable's value.

Request prestige

For a manual prestige, stop your script, choose an option in Prestige, read the preview and confirm. Manual prestige disqualifies the run from pure-script conditions.

After unlocking Theory, scripts can access Workshop.Prestige[PrestigeKind.Recompile]. Use Preview() to inspect rewards and resets, CanRequest to check eligibility, and Request() to submit the request. There is no automatic prestige settings switch. Your spell decides when to request another prestige.

A successful Request result means acceptance. Confirm that prestige has committed through OnPrestige or a change to Workshop.Epoch.

Prestige waits for accepted jobs. If they have not drained within 30 online seconds, only the prestige request is cancelled. Jobs are not automatically cancelled. Resume explicitly when ready. Closing the menu does not cancel a request.

Events after prestige

SituationEvent order
First executionOnStart, then OnTick
Resume the saved autonomous spell after rejoiningOnRestored, then OnTick
Prestige commits while runningOnPrestige, then OnTick. No OnStart
Prestige commits while stoppedNo automatic start. Notification waits for resume

A pending prestige notification runs before OnStart or OnRestored on resume. Rewards are applied when prestige commits, not inside your event handler.