STU Ward

STU Ward

The current source targets Valheim 1.0.7 and BepInExPack 5.4.2350. Jotunn is no longer required by STUWard. Guilds and Clan remain optional integrations; other installed mods may still require Jotunn.

Simple, Tidy, and Unique Ward for Valheim servers.

It adds a clone of vanilla ward but with more server-side features such as diverse protections, permission control, Guilds/Clan integration, ward count limits, and compatibility handling for common utility mods.

Trusted players manage individual ward registration from Ward Settings.

There is blacklist config to block certain items inside ward area.

Ward Settings UI

Ward area cannot be overlapped unless the wards share an owner or an authorized Guild/Clan group.

Good old auto closing door inside ward area.

What It Does

• Adds a placeable Ward with server-controlled protection rules
• Lets trusted players configure alerts, range rotation, door auto-close, protected-action restrictions, and ward range when the server enables it
• Blocks unauthorized interaction, building, terrain edits, pickup, item use, and damage inside enabled foreign wards
• Prevents foreign ward overlap while allowing same-owner and same-Guild/Clan ward groups
• Tracks per-account ward limits
• Shows ward pins and active ranges on the map when allowed

How To Use

• Select Ward with the hammer and place it.
• The server assigns the largest legal radius up to its configured maximum.
• Look at your ward and press Alt+E to open Ward Settings.
• On the first page, manage registered and recent unregistered players.
• Add a character from the server's recent unregistered-player list.
• Open the second page to configure ward alerts, range rotation, door auto-close, protected actions, and ward range when enabled by the server.

Protection

Inside an enabled ward, unauthorized players are blocked from:

• Opening or using containers, doors, carts, ships, signs, item stands, beehives, crafting stations, fermenters, sap collectors, traps, portals, and tamed creatures
• Building, repairing, removing pieces, or modifying terrain
• Damaging protected structures and objects
• Picking up items, including auto-pickup when the item policy blocks it
• Using or equipping blocked item prefabs
• Using creature-catching items on protected tamed animals

Building pieces inside an enabled STU Ward receive extra damage protection. Player and tamed-creature damage to protected building pieces is blocked, and hostile creature damage can also be blocked depending on ward attendance settings.

Permissions

STU Ward uses one trusted-player permission level for existing wards. Trust is granted to:

• The ward owner
• Individually registered players
• Players matching the ward's authorized Guild or primary Clan identity
• Server admins using effective debug control

All trusted players can use the protected area, open and change ward settings, toggle the ward, add or remove players from its individual registration list, and dismantle the ward. Authorized changes apply immediately without confirmation popups.

The owner identity is still retained for ward limits, reporting, and group metadata; it does not grant a higher permission tier on an existing ward.

STUWard supports either Guilds or Clan 1.0.0+ (sighsorry.Clan, public API v4) as its group provider. Clan Leader, Officer, and Member roles are authorized through the primary Clan; Guest connections never grant automatic ward access. Individually registered, owner, and admin-debug trust continue to work independently of group membership. An older or incompatible Clan API fails closed for automatic group authorization.

Registration

Individual registration is managed by trusted players in Ward Settings:

• The server stores structured policy in BepInEx/config/STUWard/STUWard.yml and keeps one recent-player history in BepInEx/config/STUWard/STUWard.RecentPlayers.yml.
• The list includes authenticated characters currently online or seen within the last twenty-eight days, wi