Files
GaCy-GO/docs/UI-RECOVERY-20261024.md
2026-10-28 18:54:43 +07:00

2.9 KiB

Recovery checkpoint — 2026-10-24

Confirmed findings

  • No tracked files were deleted at the initial audit. Missing menus alone do not prove missing assets.
  • Latest captured Player.log reports missing sub-mission 104020220, followed by MainMissionData.AddSubMission / _OnCmdGetMissionDataScRsp sorting failure. Mission initialization failure is a plausible cause of incomplete unlock/menu state; Client recovery is not yet confirmed.
  • Added only this observed exclusion to MissionCompatibility.json for the existing client revision entries, retaining previous exclusions. Copied the resource to for ship/resources/ as well. No executable was rebuilt or replaced.
  • The current persistent file had lost whole sections. Restored only absent sections; comparison against the checkpoint confirms every preexisting field is semantically unchanged.

Restored sections

team_presets (8 saved teams), active_team_preset, tierce_progress, player_outfits, scene_group_properties, profile, and currency_wars (configured account only).

Source: .runtime/before-cw-grants-25691022-130022/persistent, dated 2026-10-22. CW envelope revision 529, route 2801, chapter 1, section 5. This is the best located backup, not proof of the latest state before loss.

Source SHA256: 0a2c9cc2d065f1a5f5f42142e6c28136e0fe92da7d25de4f45fc0fab35d383d0

Recovered persistent SHA256: eee9771994ef931d4710b6c0b6f7dad241c7d0f556fec76b67ebf21aeab34398

Current lineup, position, scene, EX values, food stock and existing flags were preserved. No queued grants were restored. Missing Aha Help level was not guessed: no exact saved value was located in the inspected backups.

Private rollback checkpoint

.local-checkpoints/restore-ui-20261024T124147Z/before-recovery.zip contains the pre-recovery persistent, local configuration, changed files, executable copies and Player.log evidence. It contains private local data; do not publish it. The adjacent manifest records hashes.

Unresolved

  • The writer responsible for dropping persistent sections is not established. Do not attribute it to one command without evidence.
  • Further missing mission configs may surface after the current failure is removed. Do not claim the entire mission catalog is compatible from this single correction.
  • Two AA source paths disappeared during the audit while replacement round-selection files were present. Both original paths are preserved in the checkpoint; do not blindly restore them over concurrent work.
  • No gameplay tests, build, server restart or runtime probe was performed for this recovery. Client/menu behavior remains unverified. Existing executables read the external corrected resource on a fresh launch.

Next check

Open the normal walking screen and phone menu on a fresh launch, then inspect the new Player.log for mission initialization errors. Stabilize restored menus and saves before continuing gacha or event injection. Avoid simultaneous writers from another coding session.