Releases: EvaisaDev/UnityNetcodePatcher
Releases · EvaisaDev/UnityNetcodePatcher
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 causingTypeLoadException
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 is1.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.
NetcodePatcher-3.3.3
- Changed:
NetcodePatched
attribute is applied to assemblies' main module, rather than the assemblies directly- This should stop BepInEx from crashing on startup
- Fixed: Some dependency assemblies were not being included in the
MSBuild
package
NetcodePatcher-3.3.2
- Fixed : Issue where incorrect
AttributeTargets
were being set on theNetcodePatchedAttribute
NetcodePatcher-3.3.1
- Fixed [to verify]: Errors resolving assemblies when writing assembly definition to file