Update file storage paths in Client/Release_stream/Lazer/File_storage
#13882
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
A user complaint that occurs much more than I would like to see it happen is that someone backs up just the `files` directory inside the lazer user folder, which *is not enough* to recover from, as `client.realm` is also required. There's even a loud `IMPORTANT READ ME` file in the lazer user folder that even says the same thing, and yet it still keeps happening. Today I randomly stumbled upon this wiki article again and noticed it was pointing to the `files` directory, which *may* explain why this is happening so often - people might be googling "how to move lazer" or whatever, finding this article, which results in an incorrect conclusion and an undesirable outcome. And yes, before you ask: the information previously in the article was *technically* correct, but it could also be harmful. And we *could* address this in client via fifteen disparate ways people have proposed, but addressing this in client via those ways is inherently more time-consuming and risky than a wiki article update, because a wiki article update doesn't risk *absolutely every lazer user losing their data* if we mess up whatever migration process is used to hopefully "address" this problem.
|
Someone else has edited same files as you did. Please check their changes in case they conflict with yours: |
|
Conflicts with the above are trivially resolvable either direction. |
Walavouchey
approved these changes
Oct 27, 2025
2 tasks
Nivalyx
added a commit
to Nivalyx/osu-wiki
that referenced
this pull request
Oct 27, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A user complaint that occurs much more than I would like to see it happen is that someone backs up just the
filesdirectory inside the lazer user folder, which is not enough to recover from, asclient.realmis also required.There's even a loud
IMPORTANT READ MEfile in the lazer user folder that even says the same thing inside, and yet it still keeps happening.Today I randomly stumbled upon this wiki article again and noticed it was pointing to the
filesdirectory, which may explain why this is happening so often - people might be googling "how to move lazer" or whatever, finding this article, which results in an incorrect conclusion and an undesirable outcome.And yes, before you ask: the information previously in the article was technically correct, but it could also be harmful. And we could address this in client via fifteen disparate ways people have proposed, but addressing this in client via those ways is inherently more time-consuming and risky than a wiki article update, because a wiki article update doesn't risk absolutely every lazer user losing their data if we mess up whatever migration process is used to hopefully "address" this problem.
Self-check
(translations only) The changes are reviewed on GitHub by a fluent speakerHopefully obvious enough to not be required.