Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Install script does not work for non C:/ documents location

See original GitHub issue

I’ve noticed the install script does not work for users where the documents folder has been moved from C:/

The following script will fix it :

@echo off

FOR /F "tokens=2* skip=2" %%a in ('reg query "HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders" /v "personal"') do set DocumentsFolder=%%b

echo "Installing multiplayer mod in folder: %DocumentsFolder%\Documents\Klei\OxygenNotIncluded\mods\Local\MultiplayerMod\"
xcopy /s .\MultiplayerMod %DocumentsFolder%\Documents\Klei\OxygenNotIncluded\mods\Local\MultiplayerMod\

Issue Analytics

State:
Created 4 months ago
Comments:8 (4 by maintainers)

Top GitHub Comments

1reaction

zuev93commented, Jul 15, 2023

I’ve added your bat script to the repo. So closing this issue for now.

1reaction

zuev93commented, Jun 2, 2023

Thanks for the provided script!

Also do not hesitate to create fork and add your script to the repo (if you’d like to )

Top Results From Across the Web

powershell - Installed script is not found as executable

The script is published to a NuGet repository. It is then installed to the expected location, C:\Users\lit\Documents\WindowsPowerShell\Scripts\ ...

Install-Script (PowerShellGet) - PowerShell

The CurrentUser scope lets modules be installed only to $HOME\Documents\WindowsPowerShell\Scripts , so that the module is available only to the current user.

Script to change the location of Documents folder ...

I'd like to fix this by running a script that will remove both directories and only specify C:\Users\%username%\Documents as the only and ...

Let's move PSModulePath out of the documents folder

The documents folder has always been where modules user-scoped are kept, and that's always been ok, but I recently discovered some problems ......

The script is installed in directory, which is not PATH

Go to File Explorer. Navigate to C: → Users → (your user name) → AppData → Local → Programs → Python → Python38-32...