STU Ward

Simple Tidy and Unique Ward to protect your base efficiently on your server

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

Registration is same with vanilla ward
There is blacklist config to block certain items inside ward area

Ward Settings UI

Ward area cannot be overlapped unless there is guild or one player built all the wards

Good old auto closing door inside ward area

What It Blocks

Inside a foreign enabled Ward, unauthorized players are blocked from:

• Interacting with containers, doors, carts, ships, signs, item stands, beehives, crafting stations, fermenters, sap collectors, traps, portals, and tamed creatures
• Building, repairing, and removing pieces
• Modifying terrain
• Damaging or destroying protected structures and objects
• Picking up items, including auto-pickup
• Using or equipping blocked item prefabs configured by the server
• Using creature-catching items on tamed animals inside the ward
• Using TargetPortal map teleport and portal toggle mode on protected portals
• Pulling crafting materials from protected containers through supported crafting mods
• Damaging protected trees (TreeBase)
• No push players feature

Optional Compatibility

If installed, STUWard adds extra integration or blocking for:

• Guilds (guild-based trust and overlap behavior)

Following mod's feature would be blocked on other's wards

• TargetPortal
• AzuCraftyBoxes
• kg_TameableCollector
• PortablePals

How To Use

1. Select Ward with the hammer and place it.
2. A newly placed ward starts with an actual radius of 8m.
3. Look at your ward and use the default shortcut Alt+E to open Ward Settings.
4. Adjust radius, range display settings, and door auto-close delay.
5. Player registration works like vanilla wards:
   • turn the ward off
   • the player to be registered interacts with it using E

While placing a ward, the placement preview shows the current maximum configurable radius.

Permission Model

A player is treated as trusted inside a ward if they are:

• The ward owner
• In the same guild as the ward owner (The mod Guild is required)
• Listed under Registered players

Notes:

• Guild trust and registered-player access are similar for most interactions, but they are not fully identical
• Ward overlap trust behaves more like a guild/shared-group rule than a simple registered-player rule
• Being in the same guild usually grants the same practical interaction access as being registered, but guild membership is treated more like a shared trust group for ward-to-ward behavior
• A registered player can use a ward they are allowed in, but registration alone does not make separate wards behave like shared guild wards

Misc

• By default, each Steam/platform account can place up to 3 wards. (Set to -1 for unlimited)

• Specific accounts can override ward limit withBepInEx/config/STUWard.WardNumberOverride.yml

• If an account is listed in this file, that value overrides Max Wards Per Steam ID.

• command stuw_wardreport generates BepInEx/config/STUWard.WardCountReport.yml

• Admin in debugmode have acess to any ward

Localization

There should be STUWard.English.yml in BepInEx/plugins/STUWard
Translate it to your language and name the file STUWard.YourLanguageName.yml and put it in plugins folder

Overlap Behavior

Ward overlap is not treated as "one ward allows, so access is fine".

For access checks, overlapping wards are additive:

• if at least one overlapping foreign ward denies access, access is denied
• if all overlapping wards allow access, access is allowed

For placement and radius expansion:

• STUWard prevents overlap with foreign wards
• overlap is only ignored for wards that share the same owner or the same stored guild identity
• Registered players access does not bypass ward overlap rules

In practice:

• same owner wards can overlap
• same guild wards can overlap
• a registered player cannot place their own ward overlapping yours unless owner/guild rules also allow it

Guild Edge Cases

When a ward is placed, its guild identity is stored on the ward itself.

This means:

• the ward does not automatically change guild ownership later
• there is no sync button
• changing guild later does not rewrite old wards

Example:

• Player A places a ward while in guild Red
• Player B places a ward while also in guild Red
• those wards can overlap because they share the same stored guild identity
• later, Player A leaves Red

After that:

• A still has full access to A's own ward because A is the owner
• A no longer matches the stored guild identity on B's ward
• B still matches the stored guild identity on A's ward as long as B remains in Red
• in overlapping space, A can be blocked by B's ward while B can still access both areas

If you want a ward to belong to a different guild later, the intended workflow is to remove it and place a new one under the new guild.