Skip to content

Extend remote fallback for corrupted files #374

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Kruithne opened this issue May 30, 2023 · 0 comments
Open

Extend remote fallback for corrupted files #374

Kruithne opened this issue May 30, 2023 · 0 comments
Labels
enhancement Improvement of an existing feature

Comments

@Kruithne
Copy link
Owner

It is possible for local installations to be partial, meaning that certain files may be missing as they have not yet been streamed into the local data files, most likely due to not being required by the game yet. In the event of a missing file, wow.export will fallback to streaming this file from the remote server and then caching it locally.

It is possible for local installations to have corrupted files that cannot be parsed or do not match the checksum provided for said file. To cover this scenario, we should extend the remote fallback functionality used for missing files to also cover corrupted files.

An important note is that we should not patch the users local installation in the event of any missing or corrupted files. All fallback files must be stored within our own cache.

@Kruithne Kruithne added the enhancement Improvement of an existing feature label May 30, 2023
@github-project-automation github-project-automation bot moved this to 📋 Backlog in wow.export roadmap May 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Improvement of an existing feature
Projects
Status: 📋 Backlog
Development

No branches or pull requests

1 participant