Grouped STUWard.yml, STUWard.RecentPlayers.yml, and the generated STUWard.WardCountReport.yml under BepInEx/config/STUWard, and removed the Ward Settings folder button now that the files use a conventional config path.
There is no automatic migration or legacy-path fallback. Before first startup with this update, stop the game or server, create BepInEx/config/STUWard, and move the existing BepInEx/config/STUWard.yml and BepInEx/config/STUWard.RecentPlayers.yml files into it. Files left in the config root are ignored; without a manual move, STUWard creates the default policy and starts with an empty recent-player history. The generated ward-count report does not need to be moved. Existing ward ownership and registered-player permissions remain stored in ward ZDOs and are unaffected.
1.3.8
Moved STUWard.yml, STUWard.RecentPlayers.yml, and the generated STUWard.WardCountReport.yml to the shared <Valheim save data>/STUWard directory so local-host data survives mod-manager profile removal and related YAML files stay together. Worlds and mod-manager profiles using the same Valheim save-data root share the policy and recent-player history.
Added a Ward Settings header button that opens the data directory for a local host (single-player or listen server). It is hidden from remote clients and headless dedicated servers.
There is no automatic migration or legacy-path fallback. Before first startup with this update, stop the game or server, create <Valheim save data>/STUWard, and move the existing STUWard.yml and STUWard.RecentPlayers.yml files into it. Files left in BepInEx/config are ignored; without a manual move, STUWard creates the default policy and starts with an empty recent-player history. The generated ward-count report does not need to be moved. Existing ward ownership and registered-player permissions remain stored in ward ZDOs and are unaffected.
Deferred managed YAML loading until the authoritative server session is ready, preventing early platform-storage initialization failures while preserving Valheim -savedir overrides.
1.3.7
Updated optional Clan integration to the current sighsorry.Clan plugin GUID while retaining the public API v4 ward contract. The former sighsorry.valheim.Clan plugin GUID is no longer recognized.
Existing wards and individual registrations require no migration or replacement because their stored owner, registered-player, and immutable Clan identity data is unchanged. Servers and clients using Clan must install its current build together with this STUWard version.
1.3.6
Added optional Clan 1.0.0 public API v4 integration. Primary Clan Leaders, Officers, and Members receive group-based ward access, overlap, placement, minimap visibility, and player-list metadata; Guests never grant automatic ward access.
Generalized group identities so Guilds and Clan remain distinct while preserving existing Guilds ward metadata. If both providers are installed, automatic group authorization fails closed until only one remains.
Added the synchronized Ward Range Configuration server setting, defaulting to Off. When disabled, the per-ward radius slider is hidden and the second settings page reclaims the space while preserving stored radii; enabling it restores trusted-player radius adjustment.
Shortened valid SteamID64 values in registered and recent-player rows to their final ten digits. Full IDs remain unchanged internally and searchable, while non-Steam account IDs remain fully displayed.
1.3.5
Restored a server-authoritative per-ward range slider on the second settings page. New wards still start at the largest legal radius; later expansion is clamped against the server maximum and current foreign wards without resizing neighboring wards.
Consolidated recent-player history into one server-profile-wide BepInEx/config/STUWard.RecentPlayers.yml file. Existing ward registrations remain stored on their wards and are unchanged.
Former per-world recent-player files are not migrated automatically or modified. To retain one history, stop the server before its first startup with STUWard 1.3.5 and copy the complete contents of the desired STUWard.RecentPlayers.<worldUID>.yml into STUWard.RecentPlayers.yml. Do not combine multiple files; entries older than twenty-eight days are pruned normally.
1.3.4
Fixed door auto-close for slow-opening modded doors such as OdinsKingdom's GB_Large_Portcullis. After the shared five-second delay, STUWard now waits up to sixty seconds for the door to become interactable before issuing one close request.
1.3.3
Fixed dedicated-server admin+debug ward access when another client owns the ward or container ZDO. Server-validated admin+debug state is now projected to every peer, including late-join snapshots and revocation when debug mode, admin access, or the session ends.
Made same-guild ward access recover quickly when Guilds or remote-player identity arrives after a client enters an already loaded zone, without turning a transient no-guild result into a thirty-second denial.
Removed legacy ward and Guilds recovery paths. STUWard now recognizes only the current piece_stuward prefab and current Guilds Steam_<id>/name schema, and no longer backfills missing permitted snapshots or repairs malformed stored radii.
Removed obsolete ServerSync template, old BepInEx binding redirect, and unstripped-corelib build fallbacks. Servers and all clients must update to STUWard 1.3.3 together.
1.3.2
Extended the per-world unregistered-player history from fourteen to twenty-eight days. The change is not retroactive: records already pruned under the fourteen-day policy return only after those characters reconnect.
Fixed dedicated-server player tracking by reconciling delayed character identities periodically and immediately before building the unregistered-player list.
Renamed the individual-registration list heading to Registered players.
1.3.1
Simplified ward-ring visibility: placement previews and enabled wards show their ring, while disabled wards remain hidden unless highlighted as the closest placement blocker.
Removed the unused per-ward marker-visibility state and the settings-response overlap-feedback flag from the exact-version settings protocol while retaining authoritative radius clamping and the normal placement-conflict warning/highlight path.
Preserved registered-player identity snapshots when offline lookups are unavailable and removed quadratic recent-player filtering.
Rejected oversized or invalid server YAML safely, bounded report and minimap payloads, and preserved the last valid client minimap snapshot when the server exceeds the supported ward count.
Simplified runtime RPC ownership, player-list UI construction, and local deployment while making release packaging stage the manifest without modifying the tracked source file.
This wire format is not backward compatible; servers and all clients must update to STUWard 1.3.1 together.
1.3.0
Expanded the second-page behavior labels and arranged ward alert sound, ward alert visual effect, ward-range rotation, and door auto-close in a two-column grid. Range rotation defaults to on at 50% of the native marker speed.
Added a server-authoritative, per-world list of characters seen within the last fourteen days so trusted players can add them directly to a ward. Records previously pruned by the shorter retention policy cannot be recovered retroactively.
Restored the two-page Ward Settings layout: player management on the first page, behavior toggles and restrictions on the second, with independent scrolling lists.
Removed confirmation popups from ward dismantling, trusted-player removal, and ward activation changes; authorized actions now apply immediately.
Removed disabled-ward outsider self-registration and its stale vanilla opt-in/opt-out hover prompts. Trusted players now manage individual ward registration from Ward Settings.
Recent-player history starts with this release and is not imported from logs or older STUWard data.
Added a local full-brightness ward-ring cue that pulses for 0.5 seconds when crossing and remains active while standing within 0.75m of the boundary.
Added a client-only boundary brightness scope setting for trusted wards, untrusted wards, all wards, or off; placement conflicts independently highlight the closest blocking ward ring for 1.5 seconds.
Added guild, public platform account IDs, and online/last-seen status to player rows, plus independent local search fields for the registered and unregistered lists.
Made generated STUWard.yml ward-limit examples directly uncommentable under the active ward_limit_overrides mapping.
1.2.9
Unified existing-ward permissions for owners, individually trusted players, same-guild members, and admin+debug users.
Added confirmation prompts before removing an individually trusted player, dismantling a ward, or deactivating a ward.
Made new wards automatically use the largest legal radius up to the server maximum, yielding to older foreign wards.
Fixed ward marker speed and brightness at their minimum settings and removed all three marker sliders.
Simplified door auto-close to a per-ward on/off switch with one shared fixed delay of 5 seconds.
Fixed the one-page restrictions grid failing to build because its ScrollView still had Jotunn's default vertical layout component.
Removed the legacy ward-settings payload and door-delay migration path; servers and clients must update together.
Combined warning toggles, individually trusted players, and the two-column restrictions grid on one page with independent scrolling blocks.
1.2.8
Fixed revoked admin+debug access remaining cached and stopped treating cross-platform accounts with the same numeric suffix as the same administrator.
Fixed Guilds membership and ward projection refreshes, including stale join/leave data and prefixed or bare Steam account IDs, while keeping other platform identities distinct.
Fixed host-only and temporarily deferred ward minimap refreshes so local pins update without remote peers and queued server refreshes retry after index preparation.
Reworked automatic pickup protection to run the vanilla AutoPickup method while temporarily excluding denied drops, with exception-safe item-state restoration.
Made temporary interaction, portal, and pickup restriction scopes exception-safe so failed calls cannot affect later ward access checks.
Fixed valid empty permitted-player snapshots being treated as invalid and bounded snapshot backfill work for stale or malformed entries.
Hardened managed-ward placement and minimap snapshot RPCs with malformed-packet checks, request throttling, and bounded pending queues.
Changed newly generated STUWard.yml files to use empty ward_limit_overrides; sample Steam account entries are now comments instead of active mappings.
1.2.7
Fixed ward activation and deactivation VFX/SFX on dedicated servers by assigning the single networked effect spawn to the requesting client after server authorization.
1.2.6
Added a server-side prefab fallback for ward toggle effects when no live ward instance was loaded.
1.2.5
Fixed networked ward activation and deactivation effects multiplying by the number of nearby players.
Simplified blocked-action warnings to flash only the nearest denying ward and coalesced each ward's warning effects into a 0.5-second client cooldown.
1.2.4
Simplified authoritative ward-limit counting to scan only STUWard prefabs.
Removed redundant global ZDO placement tracking and diagnostic logging configuration.
Reduced diagnostic-only state and synchronization plumbing while preserving ward access behavior.
1.2.3
Fixed ward owner and admin+debug controls on dedicated servers when another peer owns the ward ZDO.
Restored authoritative per-account ward limit enforcement across world and zone loading.
Routed managed ward settings, enabled state, and permitted-player changes through the server.
1.2.2
Fixed automatic pickup and ward removal checks to follow each ward's effective restriction and owner-control rules.
Hardened server-authoritative guild, RPC, map-state, and permitted-player synchronization.
Made core Harmony patch startup transactional and simplified duplicated config, map-state, registry, and snapshot code.
1.2.1
Added per-ward restriction toggles with server-side forced/not-forced controls.
Separated hammer-placed consumable and feast consumption from normal item pickup.
