NetCode Patcher v4.4.2

Changed

• unity-v{versionMajor}.{versionMinor} package-internal directory renamed to unity-v{version}

Fixed

• Due to directory naming overlap, assemblies for two Unity versions which differ only by patch number would overwrite each other, causing problems targeting Unity 2022.3.62 / 2022.3.9

NetCode Patcher v4.4.1

Added

• Netcode versions 1.12.*, 1.13.*, 1.14.0, 1.14.
• Unity version 2022.3.62
• For Lethal Company v73, make sure to supply the CLI options: -uv 2022.3.62 -nv 1.12.0 -tv 1.0.0

Fixed

• for MSBuild SDK: MSBuild properties are now passed into NetcodePatch task, see README

NetCode Patcher v4.3.0

Fixed

• MSBuild SDK weirdness (#40)

Changed

• SDK patcher early-returns with an indicative message when no patch targets are provided

NetcodePatcher-4.2.0

Fixed

• TypeLoadException at runtime due to missing types - had to spoof the Unity.Netcode.Runtime assembly - so patcher folder structure has been changed

NetcodePatcher-4.1.1

Fixed

• An assembly reference to the patcher assembly (e.g. NetcodePatcher.uv2022...) was being added to assemblies during patching, intermittently causing TypeLoadException at runtime

NetcodePatcher-4.1.0

Added

• Unity Transport version option
• Unity editor version option
• Unity netcode native collection support option

Removed

• Programmatic API NuGet package (for now)

Fixed

• (in theory) patched Lethal Company mods causing crashes at runtime. The patcher was incorrectly assuming Unity Transport v2+, Lethal Company uses v1

NetcodePatcher-4.0.2

Changed

• Refactored the release artifact upload job of the publish workflow

NetcodePatcher-4.0.1

Changed

• quoted "..." the github release asset paths + removed leading ./ from the publish workflow

NetcodePatcher-4.0.0

Added

• Option --netcode-version (alias -nv) to specify a Unity Netcode version within the range [1.5.2, 1.8.1] to use when patching. The default is 1.5.2 (Lethal Company's Netcode version) when unspecified, to avoid breaking changes.

NetcodePatcher-3.3.4

• Fixed: the CLI would always exit with a 0 status code, even when an uncaught exception was thrown. The CLI will now exit with code -1 if an uncaught exception is thrown.