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

Binary path and save file support realitive path #669

Closed
GoogleBeEvil opened this issue Mar 3, 2019 · 2 comments · Fixed by #911
Closed

Binary path and save file support realitive path #669

GoogleBeEvil opened this issue Mar 3, 2019 · 2 comments · Fixed by #911
Labels
Feature Request User submitted feature request.

Comments

@GoogleBeEvil
Copy link

I put game in mobile HDD ,I should modify the path each time plug in diffrent pc for the label of disk is diffrent.and the save file same. If MO2 suppport realitive path, this will help

@GoogleBeEvil GoogleBeEvil added the Feature Request User submitted feature request. label Mar 3, 2019
@Al12rs
Copy link
Member

Al12rs commented Mar 3, 2019

Could you upload your mo_interface.log ?
It contains your current paths and setup so I can understand what the situation is.

You can access the logs from the "Open folder" drop-down menu over the modlist. There is an entry saying open logs folder.
Close Mo2 and drag and drop the log on github

@GoogleBeEvil
Copy link
Author

GoogleBeEvil commented Mar 4, 2019

ok let me make it clear,my skyrim folder :
all files include mo2 ,esp-esm translate tools in SSEA folder ,and game binary file in SSEB folder,if i rename SSEA to SSEC, i should modify the game path in mo2 .

can make mo2 binary path support realitive path such as
binary: ..\The Elder Scrolls V SSEB\skse64_loader.exe
start in: ..\The Elder Scrolls V SSEB
thus i can change parent folder name(SSEC ,SSED,SSEF.....) with out modify the path
mo_interface.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature Request User submitted feature request.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants