hedge-dev / hedge-dev/UnleashedRecomp

Save Backup System

Open
#1,060 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
5.1k
Forks
421
PR merge metrics
No merged PRs in 30d

Description

Save files should follow the correct logic to write and overwrite a file while preserving at least one back up.

  1. The save file should be written to a temporary file (.new).
  2. The backup save file should be renamed to a name that indicates it'll be erased (.old).
  3. The current save file should be renamed to the backup save file name (.bak).
  4. The new save file should be renamed to the current name.
  5. The save file marked for deletion should be erased (.old).

Any failure on this process should roll back all changes by executing the logic in reverse.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points. Start by locating the save-file write and overwrite logic, then trace how failures are handled. Done means writes use the .new, .old, and .bak sequence, preserve one backup, and reverse all completed changes when any step fails.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
operating-systems
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.