A reliability fix. One vanilla field that ValheimOne could no longer read would stop the entire plugin from loading — this release contains that failure to the single optional feature that depends on it.
What was wrong
ValheimOne reads two private fields on Valheim's Minimap for the optional shared-exploration feature. Both were resolved eagerly, the moment the class was first touched, and the class is constructed during plugin startup before any per-feature error handling is in place.
So if a Valheim update changed the shape of either field, the resulting exception escaped plugin startup entirely and nothing loaded — live map, web console, server query, Discord notifications and the activity log all went down together, with only a type-initializer error in the log to explain it.
Minimap only exists on a game client. It is never present on a dedicated server. An optional client-side feature was able to take down an entire server mod.
What changed
Both fields are now resolved lazily, and a failure to resolve them is handled rather than fatal. If either field cannot be read on the running game build, shared exploration disables itself and writes a single warning naming the reason. Every other feature loads and runs normally.
Do I need this?
If your server runs fine today, this changes nothing you can see — on a game build where the fields resolve normally, behaviour is identical to 0.13.1, shared exploration included.
Its value is what happens on the next Valheim update: a field-shape change that would previously have taken the whole plugin offline now costs you one optional feature.
Recommended for all servers.
Upgrade notes
Drop-in. No configuration changes, no new or renamed config keys, and no world or save-data changes. Clients do not need updating — this is a patch release, so the client compatibility handshake is unchanged and any client that worked with 0.13.1 still works.