Version 1.30.1 Released

Version 1.30.1 is now available.

This update is focused entirely on stability, save integrity, and progression safety following the release of The Last Meridian. No major new content has been added in this patch — instead, we performed a deeper audit of several systems that could behave incorrectly under unusual timing, corrupted metadata, repeated inputs, or invalid Chapter XV progression states.

Save & Recovery Improvements

The save system has received another major reliability pass.

Primary save data and its metadata are now committed as a verified pair. If either part of the write fails verification, the game attempts to restore the previous valid save instead of leaving the profile in a partially written state.

Backup handling has also been strengthened. Backup rotation now rebuilds metadata against the actual stored save data, and valid backups with damaged or outdated metadata can be recovered instead of being rejected immediately.

Automatic recovery has also been made safer in situations where the current game instance does not own the active save lease.

In short: 1.30.1 is significantly more defensive about protecting your profile when storage behaves unexpectedly.

World Threat Action Protection

Several World Threat actions could previously be triggered multiple times during very small timing windows.

Recon and battle actions now use additional risk-action guards to prevent duplicate execution from rapid clicks or repeated input.

World Threat combat setup has also received additional defensive limits for generated enemy modifiers, including damage reduction, life steal, and resistance values.

Chat Runtime Fixes

The active chat system now tracks delayed chat callbacks explicitly.

Pending typing indicators, simulated replies, Living World conversations, and other deferred chat events can now be cancelled correctly when chat is disabled, a save is imported, or the profile is reset.

This prevents old scheduled chat events from unexpectedly firing after the state of the game has already changed.

Chapter XV Progression Hardening

The Last Meridian progression logic received a deeper validation pass.

Invalid decision IDs are now discarded instead of being accepted into campaign state. Objective completion records are checked against real locations and valid objective indices, while boss and ending progression is derived from legitimate completed objectives rather than trusting potentially inconsistent stored counters.

Quest progression now also rejects invalid objective indices instead of silently clamping them into valid values.

Additional self-tests were added specifically for:

• Invalid Meridian decisions
• Invalid objective records
• Incorrect derived boss progression
• Invalid decision gates
• Out-of-range quest completion attempts

This makes Chapter XV considerably more resistant to malformed or legacy progression data.

Release Integrity Improvements

The tutorial/release audit has been updated to validate the current chapter rather than relying on an outdated Chapter XIV-specific check.

Release metadata, build identifiers, cache versions, feedback/report filenames, the boot build badge, and the in-game news entry have also been synchronized for v1.30.1.

Validation

Before packaging the release, the updated build passed:

• JavaScript syntax validation across the game files
• The Last Meridian progression self-test
• Local asset/reference validation
• Archive integrity checks

A separate Chromium-based boot test could not be completed in the build environment because the available browser process depends on system DBus services that are not present there. No game-side failure was identified by that test attempt.