It doesn't like OpenStarbound

[Awfuulfool]

Whenever I linked the "starboundpath" to OpenStarbound's Starbound.exe it takes forever to load (we're talking minutes of loading here), but once it does it immediately crashes with a "Fatal Exception Caught" error. However when I link it to the starbound.exe in my steamapps folder it works perfectly fine and loads up immediately but only runs the version of Starbound that's on steam. Am I doing something wrong in setting up it's config to OpenStarbound's .exe, or is it supposed to link to steam's .exe, and if so how do i get it to use OpenStarbound?

[zetaPRIME]

its base assets path is dependent on the starbound path (it creates a new boot config out from scratch); if you want it to work properly with osb you need to use osb mode, of which the auto install is currently slightly broken because they changed the archive names <_< for now you can use the manual option for it in the settings dialog though!

[Awfuulfool]

Thank you for replying to me, I had been running it in Osb mode and kept the "starboundpath" to Openstarbound's .exe but i still kept getting the dreaded error, that was until I found out that for whatever reason Multibound 2 wanted me to put Openstarbound's assets folder into the root directory of the drive it was on, after I had done that it worked like a charm, is this intended/normal?

[zetaPRIME]

uhhhhhh. that shouldn't be how it works??? something's going weird with windows support there, it sounds like

[Awfuulfool]

So i've looked through the _init.config to try and get a better idea as to why this is the case, from what I can assume whenever I link it to the steam starbound.exe the program looks for the assets folder in starbound's main folder, however when I link it to OSB's starbound.exe it looks for the assets folder in the root directory, is it possible to tell multibound 2 where to look for the assets folder specifically?

[zetaPRIME]

you need to leave the Starbound path on steam. to direct MB to your OSB installation, you turn on OSB mode, set it to dev/manual installation, and set things *there*. completely different path value.

…

On Tue, May 13, 2025, 2:18 PM Awfuulfool ***@***.***> wrote: *Awfuulfool* left a comment (zetaPRIME/MultiBound2#24) <#24 (comment)> So i've looked through the _init.config to try and get a better idea as to why this is the case, from what I can assume whenever I link it to the steam starbound.exe the program looks for the assets folder in starbound's main folder, however when I link it to OSB's starbound.exe it looks for the assets folder in the root directory, is it possible to tell multibound 2 where to look for the assets folder specifically? — Reply to this email directly, view it on GitHub <#24 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABS5V6WPE7NHUB2BN7WXLHD26IZOJAVCNFSM6AAAAAB46ZIPL6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQNZXGUZDOMBUGM> . You are receiving this because you commented.Message ID: ***@***.***>

[Awfuulfool]

I have followed your instructions and found out that Multibound needed me to install a different version of OpenStarbound that was stated on the release.json than the one I had already installed, and that I was supposed to put said installation into the opensb folder inside Multibound instead of trying to link an outside version of OpenStarbound to Multibound, apologies for taking your time with this rather foolish user error.