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

switching from local game based bepinex to nuget dependencies #326

Closed
sirskunkalot opened this issue Nov 1, 2021 · 1 comment
Closed

Comments

@sirskunkalot
Copy link
Member

its all there - https://nuget.bepinex.dev
publicized game assemblies would be, too, but creating own versions on the fly is more flexible.

@MSchmoecker
Copy link
Member

Closing this. Using local assemblies is usually more reliable, even for BepInEx. A dev environment for starting Valheim with mods is needed anyway.

The Environment.props can be used to overwrite paths. Default values are used for VALHEIM_INSTALL/BEPINEX_PATH and only need to be set if the setup isn't ordinary:

<?xml version="1.0" encoding="utf-8"?>
<Project ToolsVersion="Current" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
  <PropertyGroup>
    <VALHEIM_INSTALL>X:\PathToYourSteamLibary\steamapps\common\Valheim</VALHEIM_INSTALL>
    <BEPINEX_PATH>$(VALHEIM_INSTALL)\BepInEx</BEPINEX_PATH>
  </PropertyGroup>
</Project>

VALHEIM_INSTALL and BEPINEX_PATH can be set independently, so even mod managers are easily supported:

<DEPLOY_FOLDER>$(AppData)\r2modmanPlus-local\Valheim\profiles\Develop</DEPLOY_FOLDER>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants