Skip to content
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

Allow alternative caching directories (instead of using the system drive) #81

Open
RealSourceOfficial opened this issue Apr 13, 2024 · 2 comments
Assignees

Comments

@RealSourceOfficial
Copy link

Issue

One of my friends has a very corrupted system drive, and it has a very limited capacity for BeamMP to use (I am unsure why he doesn't just delete other things, but he doesn't seem to answer my question)

Solution

So I propose we allow users to set the cache directory (instead of in %appdata%/BeamMP-Launcher or something along those lines, he's not really sure)

Alternatives

  • Wolfie stops being a lazy potato and delete more files
  • Servers reduce the amount of mods loaded onto them to save space on Wolfie's drive.

Screenshots

(this man)

image

@Starystars67
Copy link
Member

@lionkor one for the Launcher :)

@lionkor lionkor transferred this issue from BeamMP/BeamMP Apr 13, 2024
@snepsnepsnep
Copy link
Collaborator

A temporary workaround would be to move the BeamMP Launcher to a different directory (and make sure the shortcut is pointed to it).
Or changing the "Start in:" directory on the shortcut itself should also work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants