Developer's Quickstart

These are the basic steps to integrate Jötunn into a new or existing project.

Install Jötunn via NuGet

If you just want to use the library and none of its automations, all you'll need to do is install the latest release of Jötunn from nuget.org into your project and start using it.

Adding a Nuget in Visual Studio is pretty simple. Let's take a look:'

  • Right click on your project, and select Manage Nuget Packages
    Vs Manage Nuget
  • Click on Browse tab in the main pane, then type Jotunn to search for our nuget. Ensure that Include Pre-Release is unchecked.
    Vs Nuget Add Jotunn and then select Install in the right hand pane.
  • Jötunn should now be installed as a dependency for your project, and the Jotunn namespace should be resolved.

Publicized Valheim assemblies

It is recommended that you use publicized versions of the game's assemblies to make the modding more convenient as you don't have to use code reflection to access private methods or otherwise inaccessible members.

You can generate these dependencies manually and add them to your project, or let Jötunn's PreBuild task handle that for you.

Manual dependency generation

Publicized assemblies are manually generated with AssemblyPublicizer. Please follow the instructions found on GitHub using the Valheim assembly DLLs found under Valheim/valheim_Data/Managed.

Activate PreBuild automations

Project references

Jötunn automatically references all dependencies that may be needed for the development process. To overwrite paths, create a new file called Environment.props at the project root and place the following contents inside, modify as needed.

<?xml version="1.0" encoding="utf-8"?>
<Project ToolsVersion="Current" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
  <PropertyGroup>
    <!-- Valheim install folder. This is usually found automatically, uncomment to overwrite.
         Needs to be your path to the base Valheim folder. -->
    <!-- <VALHEIM_INSTALL>X:\PathToYourSteamLibary\steamapps\common\Valheim</VALHEIM_INSTALL>-->

    <!-- BepInEx install folder. This is usually found automatically, uncomment to overwrite.
         Note the default value $(VALHEIM_INSTALL)\BepInEx requires the VALHEIM_INSTALL property to be set. -->
    <!-- <BEPINEX_PATH>$(VALHEIM_INSTALL)\BepInEx</BEPINEX_PATH>-->

    <!-- This is the folder where your build gets copied to when using the post-build automations.
         Note the default value $(VALHEIM_INSTALL)\BepInEx\plugins requires the VALHEIM_INSTALL property to be set. -->
    <!-- <MOD_DEPLOYPATH>$(VALHEIM_INSTALL)\BepInEx\plugins</MOD_DEPLOYPATH>-->
  </PropertyGroup>
</Project>

WARNING: If you already have references to BepInEx and Valheim, this task will most certainly duplicate them.

Publicize Valheim assemblies

Jötunn can automatically create the publicized game assemblies for you. To use this feature you must have the Environment.props file from the last step. Additionally you need to create a new file called DoPrebuild.props in your solution directory.

<?xml version="1.0" encoding="utf-8"?>
<Project ToolsVersion="Current" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
  <PropertyGroup>
    <ExecutePrebuild>true</ExecutePrebuild>
  </PropertyGroup>
</Project>

WARNING: This prebuild task will automate the generation of publicising of game assemblies. By enabling this, you understand that you will be generating new publicised assemblies upon PreBuild IF the binaries have been updated since the last time the PreBuild has run.

First build dependency acquisition

Even if you have errors in your project, you should still build the solution to ensure that the PreBuild task has run and completed successfully.

After the PreBuild has run, and dependencies have been generated, they are automatically referenced via Jötunn. They are generated inside of your game directory, and will ensure that your mods are always built against the latest version of the game.

Done! You should now have all of your required dependencies resolved, such as BepInEx, Harmony, Monomod, Publicised assemblies, Unity corelibs, and Jotunn!

BepInDependency

Don't forget to add dependency tags for bepin and compatibility! This will certify your mod throws an error if ever installed without Jötunn. Click for more information about NetworkCompatibilty.

[BepInDependency(Jotunn.Main.ModGuid)]
[NetworkCompatibilty(CompatibilityLevel.EveryoneMustHaveMod, VersionStrictness.Minor)]