Loop Dungeon Incremental Demo Save Transfer: Version Rules

At a glance

The newer policy has separate branches for different versions of demo progress. It also includes a choice about starting fresh rather than forcing every detected save into the full game. The table follows those published branches directly, keeping the one-time transition distinct from later play in the demo.

The version boundary is Demo 0.9.0

The newer developer announcement divides demo progress into two groups. Demo 0.9.0 and later is the compatible group for full progress transfer, while earlier versions follow a compensation route instead. That version-specific distinction is the direct answer to whether a demo save carries forward, rather than a blanket yes or no covering every earlier test of the game.

An official title-screen screenshot visibly marks version v0.9.0. The image corroborates that version label in the game's own promotional material, but it does not show a migration being performed. The actual transfer policy comes from the developer's announcement, which is the source for the choices described here rather than a conclusion inferred from the existence of the menu screenshot.

Compatible saves are checked at first launch

For Demo 0.9.0 and later, the announcement says the full game checks for a compatible demo save when it is launched for the first time. When such a save is found, the player is offered a choice between transferring the progress and starting a new game. The described behavior therefore includes both detection and an explicit decision rather than an unconditional replacement of a new save.

The statement that full progress can transfer belongs to that compatible-save branch. It should not be stretched into a separate claim about every platform, file location or application variant using the game's name. The material collected for this guide establishes the developer's announced full-game process, without supplying additional instructions for manual copying, browser storage conversion or other migration methods.

Starting fresh is a documented alternative

The newer announcement explicitly offers a new-game choice when compatible demo progress is detected. A player is therefore not described as being forced to continue the old run merely because a save exists. That matters because continuing prior progress and beginning again are both supported options within the policy, rather than one being an unofficial workaround.

The choice is part of the initial transition described by the developer. It is separate from the repeated expeditions and purchases that take place while playing, and from the prestige reset shown in the videos. Keeping those events distinct makes the announcement clearer: the player is deciding how to begin the full game, not simply confirming another ordinary action inside an existing demo session.

Older demo saves receive a compensation choice

Versions before Demo 0.9.0 do not receive direct full transfer under the announced rule. Instead, the developer describes a one-time migration system offering resource compensation based on the older demo progress. The player can claim that compensation and begin a new game, or decline it and begin completely fresh.

This is a specific alternative to carrying over the earlier save unchanged. The announcement does not provide a general numerical compensation formula in the collected material, so a promised amount should not be added to the explanation. What is established is the type of choice and its relationship to an older save, without guessing how much a particular player's earlier progress will produce.

Transfer happens once rather than remaining synchronized

The developer explicitly describes compatible-save migration as a one-time transfer. After progress has moved into the full game, continuing to play the demo does not alter the full-game save. This answers a different question from initial compatibility: a successful transfer is the transition described by the announcement, not the beginning of an ongoing relationship between the two saves.

That distinction prevents the word transfer from being misread as continuous synchronization. It also keeps the guide from assigning behavior to Steam Cloud or another storage system simply because such a feature appears elsewhere in the game's information. The announcement establishes the one-time migration and the later separation of demo play, while other storage or backup mechanics are outside the described process.

Why the older playtest warning sounds different

The May first-playtest announcement warned that saves would not carry into the final game. That statement concerned an earlier test and predates the later version-specific migration policy. Reading it without its date would therefore flatten different development stages into one rule and obscure the explicit distinction the developer subsequently introduced for newer demo versions.

The newer announcement is more specific about what happens to both compatible and older progress. It does not need to be reconciled by pretending the May test and every later demo are identical builds. The accurate chronology is an early no-transfer warning followed by a later policy that separates full transfer from compensation according to the stated Demo 0.9.0 boundary.

Prestige footage does not demonstrate save migration

Both English videos include in-demo progression, and their prestige sequences reset ordinary development before rebuilding. Neither recording launches the complete game and performs the migration described in the newer announcement. Their reset footage therefore cannot independently prove or disprove the version-transfer policy, even though both topics involve some form of progress and a decision about starting again.

This guide presents the transfer behavior as the developer's announced rule. The official version screenshot corroborates the displayed boundary label, while the dated announcements explain the policy change and the available choices. That gives a clear account of compatible transfer, older-save compensation and one-time behavior without presenting an unperformed full-release test or inventing additional migration procedures.

The browser demo does not establish an extra transfer route

Playsect hosts a browser-playable demo on itch.io alongside the Steam game information. That page establishes a legitimate way to try the project in its development context. It does not independently specify that a browser save can be converted into a compatible Steam save or that every demo application uses an interchangeable storage format.

The version-transfer announcement should therefore retain its own wording and scope. It establishes the first-launch compatible-save choice and the distinction between full migration and compensation. Adding browser extraction instructions or a manual file-copy method would introduce procedures that the collected material does not verify, rather than clarifying the announced option already available to the player.

The advertised release context explains the policy's purpose

The full-game announcement describes additional heroes, skills, bosses and levels beyond the demo. It places migration within the transition from earlier development content to a broader release, which explains why older progress and compatible newer saves are addressed separately. This is a concrete version distinction, not a general assertion that all changes to the game erase every save.

The policy also preserves the option to begin again when the compatible save is detected. That makes a fresh start a documented part of the transition rather than an unofficial consequence invented by a guide. Read together, the developer's choices cover continuing compatible progress, accepting compensation for older progress and starting fresh, without implying ongoing synchronization between demo and full-game play.