The plugin announced the wrong version of itself. 1.1.0 moved the csproj, the manifest and the toml and missed the
BepInPluginconstant, which is the version the plugin actually reports and half of what Core's gate compares - so the package read 1.1.0 on Thunderstore and introduced itself as 1.0.1 on every connection. Harmless while everyone runs identical builds, and not harmless the moment they do not.
Discussion
Nothing said yet.
Sign in or make an account to join in.