Abonner for at downloade
LibConstruct

@Tom_is_unlucky thanks for the reply, we will try that out and see if that fixes it, good catch!

actually @Sheetpan i see your issue. the mods folder should not be in streamingassets, but in the same folder as the server exe

@Sheetpan and @Vince could you send me the full log? easiest place is probably the #modding channel on the stationeers discord

I'm also running into the same issue with LibConstruct on a dedicated server. I have the logs, and it looks like something is going wrong in the About.xml
Here's a snippet from the log. I can share the entire log if you like, too

An error occurred while deserializing a file!: Z:/home/container/rocketstation_DedicatedServer_Data/StreamingAssets\Data\Mods\3505115682\About\About.xml - There is an error in XML document (2, 2). : <ModMetadata xmlns=''> was not expected.
Failed to load Z:/home/container/rocketstation_DedicatedServer_Data/StreamingAssets\Data\Mods\3505115682\About\About.xml
InvalidOperationException: <ModMetadata xmlns=''> was not expected.

Any update to @EnGinEar 's problem? I'm having the same issue.

@EnGinEAR what platform is the server hosted on, and do you have the logs? it sounds like the server isn't loading bepinex at all

Trying to use this for the ModularConsoles mod, im hosting a dedicated server using this mod, BepInEx, and StationeersLaunchPad.
my problem is that my client isnt able to connect to the server because " Server is missing LibConstruct@0.2.5 "

i have installed the serverside LaunchPad and use the client side LandingPad export zip button. LibConstruct is in there and identical to the client mod
maybe im just tired and missing something obvious

Apparently I'm still subscribed to this thread lol, whoops, but I figured I can chime in that it really seems to be just the symlink itself causing problems and not just the other mods getting loaded first leading to weird conflicts. I tested it with all the same mods that BepInEx was loading automatically because of the symlink, and no matter where in the load order they were, the problem never returned. It's weird that it's only this library has the problem, but if it's happening for multiple people it may be simplest to just add a note to the mod page telling people (if they ever used StationeersMods) to just delete the symlink at time of install so the problem doesn't even manifest... and/or get it added to the LaunchPad install page under the correct section, if you can? The "upgrading" part just says to delete the old StationeersMods files but not the symlink, after all...

StationeersLaunchPad will load all the enabled workshop mods for you. The symlink isn't needed at all any more

But if i remove the symlink, the workshop content won't works, don't?