The root README is the one players get: package.ps1 and nexus-readme.py
read it. JotunnModStub/README.md and Package/README.md had drifted for
versions, and edits kept landing in them by mistake. Both are gone. The
csproj links the root README, the publish scripts copy it into Package/
at release, and that generated copy is ignored.
VALHEIM_INSTALL and BEPINEX_PATH were read from machine-level environment
variables that a fresh clone does not have. With them empty every derived path
started at the drive root, so the first Copy of a build failed on a new machine.
They now default to the standard Steam install and the environment variables
still override.
The DLL has exactly one destination, BepInEx\plugins, and it goes there on Debug
builds too - that is the loop you actually iterate in. If the folder is missing
the build warns instead of failing. The Thunderstore and Nexus zips stay in
dist\ and stay Release-only.
Copying assemblies into the Unity stub project is now opt-in
(-p:CopyAssembliesToUnity=true). It rewrote a folder of game assemblies on every
build for the sake of asset authoring that most builds are not doing.
dist\ is ignored. Only a stale icon.png was ever tracked in there - the packaging
step reads the real one from JotunnModStub\Package - so it is untracked, not
deleted.
A Windows .lnk stores an absolute path to the machine that created it, so the
file resolves for nobody else who clones the repo. It arrived alongside the
dist icon and has no business being versioned.
The local shortcut is left on disk; only the tracking is dropped. *.lnk joins
.gitignore so the next one does not follow it back in.