Request: BepInEx Support

[zem-sessions]

From my limited understanding, it looks like BepInEx could work if launcher.sh wasn't re-generated, or if there was a parameter that allowed attaching the needed exports. Completely understandable if it's outside the project scope or what not.

[chegele]

I’m unfamiliar with BepInEx. Is it just an alternative executable for launching the server? Get Outlook for iOS<https://aka.ms/o0ukef>

…

________________________________ From: Zemeck ***@***.***> Sent: Wednesday, August 23, 2023 6:32:41 PM To: chegele/ValheimManager ***@***.***> Cc: Subscribed ***@***.***> Subject: [chegele/ValheimManager] Request: BepInEx Support (Issue #20) From my limited understanding, it looks like BepInEx could work if launcher.sh wasn't re-generated, or if there was a parameter that allowed attaching the needed exports. Completely understandable if it's outside the project scope or what not. — Reply to this email directly, view it on GitHub<#20>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AHUOSI7ZEICLZMZHUSQAVVLXW2AITANCNFSM6AAAAAA34EGXXU>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[zem-sessions]

https://valheim.thunderstore.io/package/denikson/BepInExPack_Valheim/

So BepInEx has a launch script that looks fairly similar to start_server.sh but it has some extra exports:
`#!/bin/sh

BepInEx-specific settings

NOTE: Do not edit unless you know what you are doing!

export DOORSTOP_ENABLE=TRUE
export DOORSTOP_INVOKE_DLL_PATH=./BepInEx/core/BepInEx.Preloader.dll
export DOORSTOP_CORLIB_OVERRIDE_PATH=./unstripped_corlib

export LD_LIBRARY_PATH="./doorstop_libs:$LD_LIBRARY_PATH"
export LD_PRELOAD="libdoorstop_x64.so:$LD_PRELOAD"

export LD_LIBRARY_PATH="./linux64:$LD_LIBRARY_PATH"
export SteamAppId=892970

echo "Starting server PRESS CTRL-C to exit"

Tip: Make a local copy of this script to avoid it being overwritten by steam.

NOTE: Minimum password length is 5 characters & Password cant be in the server name.

NOTE: You need to make sure the ports 2456-2458 is being forwarded to your server through your local router & firewall.

exec ./valheim_server.x86_64 -name "My server" -port 2456 -world "Dedicated" -password "secret"`

My limited understanding is that those exports are all that's needed to get it to work after it has been installed. I couldn't do any testing as launcher.sh gets overwritten on launch, so I don't actually know if anything else is needed. For LGSM, it didn't require anything extra, but linux isn't my wheelhouse.

[chegele]

Thank you for completing this research for me. The launch file is generated by the manager at runtime. A configuration option can be added to allow launch with BepInEx. I just need to find some time to implement the feature. It could be several weeks.

In case another developer would like to submit a pull request.

Ref: https://github.com/chegele/ValheimManager/blob/53c1a28ef3696bad7a6980b9920ec8701df72a5d/src/launcher.js#L65C1-L81C6

    /**
     * LINUX Generates a shell script for launching the valheim dedicated server. 
     * @returns {boolean} True if the file was created with the expected permissions. 
     */
    async generateLinuxLauncher() {
        this.manager.logger.general('Generating the launch file...');
        const server = this.manager.installer.valheimServerPath;
        const config = this.manager.config.launcher;
        let fileContent = `\n# Launch file generated by Valheim Manager. Not intended for manual interaction.`;
        fileContent += `\nexport TERM=xterm`;
        fileContent += `\nexport templdpath=$LD_LIBRARY_PATH`
        fileContent += `\nexport LD_LIBRARY_PATH=./linux64:$LD_LIBRARY_PATH`
        fileContent += `\nexport SteamAppId=892970`
        fileContent += `\n${server} -name "${config.name}" -port ${config.port} -world "${config.world}"`;
        if (config.password != '') fileContent += ` -password "${config.password}"`;
        fileContent += `\nexport LD_LIBRARY_PATH=$templdpath`
        await fs.writeFile(this.launchFile, fileContent);
        await fs.chmod(this.launchFile, '755');
        const stat = await fs.stat(this.launchFile);
        return stat.mode == '33261';
    }