Version 1.30.3 Released

Version 1.30.3 is now ready.

This is a focused hotfix for the save-system regression discovered after the release of 1.30.2 – Save Continuity.

A real iPhone play session exposed a browser-storage edge case that our desktop/browser regression suite had not previously reproduced. The game repeatedly displayed:

“Could not verify or save progress in this browser.”

The affected profile was successfully exported before the page was reloaded, giving us both a protected player save and, importantly, our first real-world save fixture for investigating the problem. The player save itself is not included in the release package. 

What Happened?

The underlying save data was not corrupt.

Version 1.30.2 already contained a fallback mechanism for situations where persistent browser storage becomes unavailable. If localStorage could not be written, the game attempted to continue using temporary in-memory session storage.

The problem was that the subsequent read-back verification still tried persistent storage first.

Some browser environments can enter an unusual state where:

two versions did not match, so the save transaction was considered invalid and the game repeatedly displayed the verification error. 

A New Layered Storage Fallback

Version 1.30.3 introduces a more coherent browser-storage adapter.

After the first persistent write failure during a page session, the game now switches completely into session-storage mode for that session.

From that point onward:

• New in-memory save data takes precedence over stale persistent values.
• Save data and save metadata remain on the same storage layer.
• Deleted session values use an overlay tombstone so old persistent data cannot reappear.
• The next page load performs a fresh storage-capability check.
• If persistent storage genuinely remains unavailable, the game continues running but explicitly warns the player to export their save. 

The important distinction is that the game no longer mixes:

new temporary writes + old persistent reads.

That was the failure mode responsible for the repeated error messages.

Save Compatibility Remains Intact

Save Schema remains 39.

There is no new migration between 1.30.2 and 1.30.3. Existing 1.30.2 profiles can move directly into this release. 

The existing compatibility architecture remains unchanged, including:

• Schema 38 → 39 migration
• Progress preservation
• Unknown legacy-field preservation
• Additive attachment of new content
• Save/load roundtrip validation
• Legacy export support
• Backup metadata reconstruction
• Atomic rollback protection
• Future-schema rejection
• Chapter XV progression validation 

Real Player Save Validation

The exported iPhone profile was imported directly into the 1.30.3 browser test environment.

Before import, the real save contained:

• Schema 39
• Original source schema 38
• Save revision 543
• 4,850 Gold
• 229 Crystals
• 3 Raid Keys
• 5 Arena Tokens
• 7 inventory entries 

After importing and committing the profile under 1.30.3:

• Schema remained 39
• Original source schema remained 38
• Gold remained 4,850
• Crystals remained 229
• Raid Keys remained 3
• Arena Tokens remained 5
• All 7 inventory entries remained intact
• Save revision correctly advanced from 543 → 544
• Runtime errors: 0

This is particularly valuable because the compatibility suite is now no longer based entirely on synthetic historical saves: we have successfully validated a real exported player profile against the new storage layer.

New Regression Coverage

The Save Compatibility Regression Suite has expanded again.