VALHEIM AUTOMODSYNC 2.6.1

Join the server. The mods follow.

AutoModSync is a client/server synchronization utility for Valheim + BepInEx.

Instead of requiring every player to manually locate, compare, update, and install the same server-required files, AutoModSync lets a trusted Valheim server maintain its synchronized BepInEx environment automatically.

Players connect to the Valheim server normally.

AutoModSync can synchronize:

BepInEx/plugins files
Required BepInEx/patchers files
Explicitly allowlisted BepInEx/config files
Client-required files from BepInEx/AutoModSync/ClientPayload/plugins

Server synchronization behavior is configured in:

BepInEx\config\com.gordonfreesay.valheimautomodsync.server.cfg

When an AutoModSync client joins an enabled server, it can establish the server identity, compare installed files against the signed synchronization manifest, transfer only missing or changed files, verify them, safely apply changes, restart Valheim when required, reconnect to the same server, and continue using the previously selected character when possible.

Version 2.6.1 is the security and connection-boundary hardening release for the 2.6 line.

It retains the large-transfer, caching, resume, scheduler, ownership, transactional recovery, and UI improvements introduced in 2.6.0 while strengthening protected-server access, stale-mod compatibility handling, updater architecture, and server signing-key protection.

✨ WHAT'S NEW IN 2.6.1

PROTECTED-SERVER SYNCHRONIZATION BOUNDARY

Password-protected servers now withhold protected AutoModSync synchronization information until the exact live connection has been granted normal Valheim server access.

Before server access is granted, AutoModSync exposes only:

AutoModSync presence
Version / protocol information
The fact that server access is required
An opaque random one-time challenge

Before that access boundary succeeds, it does not expose:

Server signing identity/fingerprint
Manifest metadata or contents
Synchronized paths
File hashes
File sizes
Synchronized configuration
Bundle/cache state
Transfer capabilities
Synchronized file bytes

ONE-TIME CONNECTION-BOUND SERVER-ACCESS VERIFICATION

Current 2.6.1 clients negotiate the password-auth2 capability.

Valheim's normal server-key/server-access prompt remains the user input flow.

The client derives Valheim's salted password verifier locally.

AutoModSync does not transmit that reusable verifier.

Instead, AMS sends a one-time HMAC-SHA256 challenge response.

The challenge is:

Cryptographically random
Bound to the exact live connection
One-use
Time-bounded
Discarded when the connection ends

A later reconnect must satisfy the normal server-access boundary again.

STALE-MOD COMPATIBILITY ISOLATION

Some Valheim mod libraries can send compatibility/version RPCs from ZNet.OnNewConnection, before Valheim's normal ServerHandshake.

That means an outdated client mod can potentially reject a server before AutoModSync gets a chance to update it.

2.6.1 adds negotiated preflight-quarantine1 handling.

During AutoModSync preflight:

AMS protocol traffic remains active
Required server-access controls continue normally
Early non-AMS compatibility/version traffic can be temporarily quarantined
If synchronization changes files, stale queued compatibility traffic disappears with the old connection
If no changes are required, AMS4_Ready releases queued calls in their original order
Genuine disconnects are not trapped
Non-AutoModSync / legacy flows retain bounded fail-open behavior
Recognized inactive preflights cannot retain authorization/quarantine state indefinitely

This is generic rather than being hardcoded specifically for Jotunn, ServerSync, Warfare, Epic Loot, or another individual mod.

ONE INSTALLER / UPDATER — NO APPLY.EXE

AutoModSync 2.6.1 removes the old standalone:

ValheimAutoModSync.Apply.exe

The existing crash-safe post-exit transactional update engine now lives inside:

ValheimAutoModSyncInstaller.exe

The executable therefore has two roles:

Explicit AutoModSync install / repair / uninstall
AutoModSync's required visible post-exit transactional updater

During normal synchronization updates, the updater:

Runs visibly
Waits for Valheim to close normally
Never force-terminates Valheim
Does not force-kill another process
Runs as the current user
Does not request UAC elevation
Applies only already-verified staged AutoModSync changes
Preserves PREPARED / COMMITTED journaling
Preserves verified backups and rollback/recovery
Preserves path/reparse validation
Preserves digest verification
Preserves ownership rules

Explicit install, repair, and uninstall actions can still request normal Windows elevation when required.

SERVER SIGNING-KEY ACL HARDENING

The persistent AutoModSync server private signing key now receives explicit Windows ACL hardening.

AutoModSync:

Disables inherited ACL permissions on the private key
Restricts Full Control to the actual key-owning/runtime Windows identity
Allows LocalSystem
Allows local Administrators
Removes broad principals such as Users / Everyone
Re-hardens existing identities during startup
Refuses to use a private key if the restrictive ACL cannot be established and verified
Removes a newly generated identity if hardening fails

The public signing key/fingerprint remains public.

CLEARER EXECUTABLE-CODE TRUST BOUNDARY

BepInEx plugins and preloader patchers are executable code.

The first-contact trust flow now makes that boundary explicit.

Accepting an AutoModSync server authorizes that trusted server to provide synchronized executable mod files and configuration to the user's PC.

AutoModSync verifies transport policy, server identity, integrity, synchronization scope, and installation state.

It does not certify that arbitrary third-party plugins themselves are safe.

RELEASED 2.6.0 PROTECTED-SERVER MIGRATION

Released AutoModSync 2.6.0 clients have a dedicated migration bridge for password-protected 2.6.1 servers.

The first connection does not receive protected synchronization information before Valheim grants normal server access.

After the correct server key is accepted:

The server creates a short-lived one-use migration grant bound to the same platform identity.
The bootstrap connection intentionally disconnects.
The released 2.6.0 client requires one manual reconnect.
That reconnect must occur within the five-minute migration-grant lifetime.
The grant permits the signed 2.6.1 migration path only.
It does not permit gameplay.
AutoModSync installs the 2.6.1 client plus the installer/updater.
Valheim restarts.
Normal 2.6.1 protected-server behavior applies afterward.

AutoModSync 2.5.x and earlier clients do not have this protected-server migration bridge.

LIVE-QUALIFIED RELEASE

The 2.6.1 live qualification covered:

Wrong/correct server-key behavior
Protected synchronization disclosure boundary
A real released 2.6.0 → 2.6.1 migration
Stale-mod preflight isolation
Visible installer/updater apply
Normal Valheim shutdown
Restart and reconnect
Normal post-migration 2.6.1 protected join
Final package inspection confirming no standalone ValheimAutoModSync.Apply.exe

✨ FEATURES

• Automatic server-to-client synchronization
Downloads missing or updated synchronized BepInEx files required by the server.

• Plugins, patchers, selected configs & client-only payloads
AutoModSync can synchronize normal plugins, required preloader patchers, explicitly allowlisted configuration files, and dedicated client-only payloads.

• Client-only server payloads
A dedicated server can provide client-required files from:

BepInEx\AutoModSync\ClientPayload\plugins\

without loading those files into the dedicated-server process itself.

• Pre-compatibility synchronization
AutoModSync gets the opportunity to reconcile required synchronized files before normal Valheim and Jotunn/ServerSync-style compatibility checks complete.

Those compatibility systems are not disabled or bypassed.

• Delta synchronization
Only missing or changed synchronized files are transferred.

• Content-addressed bundle caching
Identical synchronized change sets can reuse the same immutable prepared bundle rather than independently recompressing the same content for every player.

• Startup bundle prewarming
Servers can prepare the common nearly-bare-client synchronization bundle during startup.

• Single-flight bundle construction
Overlapping requests for the same uncached bundle can share one package construction operation.

• Interrupted-download resume
AutoModSync can retain one bounded partial package after an interrupted transfer.

Before accepting a nonzero resume point, the server independently verifies the exact retained prefix against the current immutable bundle.

• Bounded multi-client scheduling
Server-wide active and waiting limits prevent an unlimited number of fresh synchronization jobs from becoming active simultaneously.

• Round-robin transfer grants
Active synchronization clients receive aggregate bandwidth grants in rotation.

• SteamNetworkingSockets backpressure awareness
AutoModSync can defer additional transfer data while Steam's reliable queue is already under pressure.

• No extra sync port
AutoModSync uses Valheim's existing game connection.

• Signed server manifests
Each AutoModSync server has its own signing identity.

• SHA-256 verification
Transferred files are checked against the authenticated signed manifest before they become live.

• Safer first-contact trust
A short human-comparison security code is displayed when trusting a new server identity.

The complete 256-bit fingerprint remains internal for cryptographic verification and trust pinning.

• Fail-open discovery for normal servers
If a selected server does not identify itself as AutoModSync during the bounded discovery flow, normal Valheim behavior can continue.

• Fail-closed protection after AMS recognition
Once a server is positively recognized as AutoModSync, protected security or synchronization failures block that protected join rather than silently ignoring the failure.

• Transactional apply & recovery
AutoModSync uses durable PREPARED / COMMITTED transaction states with verified backups and recovery behavior.

• Ownership-safe stale cleanup
AutoModSync records ownership only for files it actually installs or replaces.

Pre-existing matching files are not automatically claimed.

Locally modified and unrelated files are preserved.

• Stronger path safety
Includes fixed synchronization roots, canonical path validation, traversal rejection, Windows device/reserved-name defenses, trailing-dot/space protections, and reparse-point rejection.

• Bounded ZIP extraction
Compressed size, expanded size, synchronized file count, individual file size, transfer geometry, and ZIP expansion are bounded.

• Branded synchronization UI
The AutoModSync panel can display:

Comparison counts
Queue position
Current throughput
Average throughput
ETA
Resume-retained bytes
Verification state
Apply state
Restart state
Reconnect state
Completion
Bounded failure state

• Passive server-browser AMS presence
Supported Steam-backed servers can advertise passive AutoModSync version/protocol information.

AMS-aware clients can show a small local AMS badge beside positively identified server-browser entries without changing the advertised server name.

• Automatic restart
If synchronized files change, AutoModSync stages and safely applies them before restarting Valheim.

• Automatic reconnect
After synchronization and restart, AutoModSync can return the player to the originating server.

• Selected-character continuation
When possible, AutoModSync continues using the character selected before synchronization restarted the game.

• Server/client classification
Server-only and optional client-required patterns let administrators avoid advertising dedicated-server-only files to players.

• AMS4 / protocol 4 retained
AutoModSync 2.6.1 remains:

AMS4 / protocol version 4

New 2.6.1 behavior is negotiated through protocol capabilities.

INSTALLATION

Close Valheim and any running Valheim Dedicated Server before installing.

1. INSTALL BEPINEX

Install BepInExPack Valheim 5.4.2350, or another compatible current Valheim BepInEx 5 installation.

BepInEx is a separate requirement for the CurseForge package.

The included ValheimAutoModSyncInstaller.exe does not mean this CurseForge package contains BepInEx.

The standalone GitHub/website package includes the pinned BepInEx archive. The lightweight CurseForge package does not.

2. INSTALL AUTOMODSYNC

Install or extract the AutoModSync CurseForge archive into your Valheim game directory or Valheim Dedicated Server directory while preserving its directory structure.

The AutoModSync files should land beneath:

BepInEx\plugins\GordonFreesay-ValheimAutoModSync\

The 2.6.1 package contains:

ValheimAutoModSync.Client.dll
ValheimAutoModSync.Server.dll
ValheimAutoModSyncInstaller.exe

There is no ValheimAutoModSync.Apply.exe.

3. LAUNCH NORMALLY

Start Valheim or the Valheim Dedicated Server normally through the BepInEx-enabled installation.

On valheim_server.exe, the client role disables itself automatically.

On a normal Valheim client, the server role remains passive unless that client is hosting.

CURSEFORGE PACKAGE

This is the lightweight CurseForge distribution of AutoModSync.

It contains:

ValheimAutoModSync.Client.dll
ValheimAutoModSync.Server.dll
ValheimAutoModSyncInstaller.exe
AutoModSync package documentation/notices

It intentionally does not contain:

Bundled BepInEx
ValheimAutoModSync.Apply.exe
Arbitrary third-party gameplay mods
The standalone GitHub/website package
A nested standalone archive

WHY IS THE INSTALLER INCLUDED IF BEPINEX IS STILL REQUIRED?

Because in 2.6.1:

ValheimAutoModSyncInstaller.exe

is also AutoModSync's required transactional updater.

The CurseForge package does not contain the standalone release's bundled:

Bundled\BepInExPack_Valheim-5.4.2350.zip

so the lightweight CurseForge package cannot bootstrap BepInEx from that archive.

BepInEx remains a separate dependency.

During normal synchronization, the same executable is launched in updater mode only after required changes have already been downloaded, verified, and staged.

The standalone package with bundled BepInEx is available here:

Developer website:
Valheim AutoModSync Website

GitHub Releases:
AutoModSync Releases on GitHub

SERVER CONFIGURATION

AutoModSync's synchronization rules are configured in:

BepInEx\config\com.gordonfreesay.valheimautomodsync.server.cfg

ExcludePatterns

Located under:

[General]
ExcludePatterns =

A semicolon-separated wildcard list for files that must not be synchronized from configured roots.

ServerOnlyPatterns

Located under:

[Compatibility]
ServerOnlyPatterns =

Use this for plugin or patcher files that belong on the server but must never be synchronized to clients.

ClientRequiredPatterns

Located under:

[Compatibility]
ClientRequiredPatterns =

This is an optional plugin/patcher allowlist.

When empty, plugin and patcher files that are not excluded or classified server-only remain client-required.

When populated, only matching plugin/patcher files are advertised as client-required.

If a mod has dependency DLLs or assets beside its primary DLL, include the appropriate folder wildcard.

Example:

ClientRequiredPatterns = SomeMod/*;AnotherRequiredMod/*

SyncPatchers

[Compatibility]
SyncPatchers = true

Controls recursive synchronization of required files beneath:

BepInEx\patchers

SyncConfigPatterns

[Compatibility]
SyncConfigPatterns =

BepInEx configuration files are not synchronized by default.

Only add configuration files that genuinely need to be identical on clients.

Patterns are relative to:

BepInEx\config

Example:

SyncConfigPatterns = com.example.required.cfg;RequiredMod/*.json

The following remain protected from synchronization even if a broad pattern would otherwise match:

ValheimAutoModSync.private.xml
ValheimAutoModSync.public.xml
BepInEx.cfg

ClientPayload

Client-required files that the dedicated server itself should not load can be placed beneath:

BepInEx\AutoModSync\ClientPayload\plugins\

LARGE-PAYLOAD CONTROLS

AutoModSync includes configurable limits and scheduling controls for:

Bundle size
Expanded size
Synchronized file count
Individual file size
Active transfers
Waiting transfers
Aggregate bandwidth
Bundle cache retention
Bundle-cache disk budget
Optional fresh-client prewarming

HOW IT WORKS

01 — DISCOVERY / SERVER ACCESS

AutoModSync determines whether the selected server supports AMS.

If it does not, normal Valheim behavior can continue.

On a password-protected server, protected synchronization information remains withheld until normal Valheim server access is granted.

02 — TRUST

Every AutoModSync server has its own signing identity.

On first contact with a new identity, AutoModSync displays a short human-comparison security code.

The complete fingerprint remains internal for cryptographic verification and trust pinning.

Only trust AutoModSync servers operated by people you recognize and trust.

03 — COMPARE

AutoModSync verifies the signed synchronization manifest and compares the client's synchronized local file state.

Files that already match do not need to be transferred again.

04 — QUEUE / PREPARE

If transfer work is required, the request enters the server's bounded synchronization scheduler.

The server prepares or reuses the immutable bundle matching the required change set.

05 — DOWNLOAD / RESUME

Only missing or changed synchronized files are transferred.

An eligible retained partial package can resume only after the server independently verifies the exact retained prefix.

06 — VERIFY

Transferred data, extracted files, paths, hashes, and resource limits are verified before live installation.

07 — STAGE

Required changes are staged and recorded in durable pending transaction state.

08 — APPLY

AutoModSync launches:

ValheimAutoModSyncInstaller.exe

in visible updater mode.

The updater waits for Valheim to exit normally and performs the verified PREPARED → COMMITTED transaction.

09 — RESTART

Valheim starts again so BepInEx can load the synchronized environment.

10 — RECONNECT

AutoModSync can return to the same server.

When possible, it also continues using the character selected before synchronization.

A password-protected reconnect must satisfy normal server access again.

INTERRUPTED DOWNLOAD RESUME

AutoModSync can retain one bounded partial synchronized package if a connection is interrupted during transfer.

The retained transfer is associated with the exact synchronization artifact and trusted server identity.

Before accepting a nonzero resume position, the server independently verifies the retained prefix against its current immutable artifact.

If the relevant identity or artifact changed, the partial package is rejected and synchronization begins safely from the start.

TRANSACTIONAL APPLY & RECOVERY

Before synchronized live files change, AutoModSync enters a durable:

PREPARED

transaction state.

Existing destinations that need replacement are backed up and verified.

After every required destination has been written and verified, the transaction reaches:

COMMITTED

If AutoModSync or the system is interrupted before COMMITTED, recovery can restore the previous complete state.

If interruption occurs after COMMITTED, AutoModSync preserves the complete new state and finishes cleanup.

AutoModSync does not intentionally accept a mixed half-old / half-new synchronized state.

In 2.6.1 this transaction engine is hosted by:

ValheimAutoModSyncInstaller.exe

There is no standalone Apply helper.

OWNERSHIP-SAFE FILE CLEANUP

AutoModSync claims a synchronized file only when AutoModSync actually installs or replaces it.

A pre-existing local file that already matches the server is not automatically claimed.

A stale owned file is removed only when:

It belongs to the same trusted server identity
AutoModSync previously recorded ownership of it
Its current bytes still exactly match what AutoModSync previously installed

If the player modifies the file locally, AutoModSync preserves it instead of deleting it.

Unrelated files remain untouched.

🔌 NO EXTRA SYNC PORT

AutoModSync uses Valheim's existing game connection.

You do not need to:

Open another synchronization port
Add another AutoModSync firewall rule
Add another router port-forward
Run a separate synchronization web server

CLIENT

On a normal Valheim game process, the AutoModSync client handles synchronization with AutoModSync-enabled servers.

DEDICATED SERVER

On valheim_server.exe, the client role disables itself automatically.

The server component can:

Create and maintain its signing identity
Publish the signed synchronization manifest
Synchronize plugins
Synchronize patchers
Synchronize selected configs
Provide client-only payloads
Cache and prewarm immutable bundles
Share one build across identical requests
Schedule active and waiting transfers
Apply aggregate bandwidth limits
Respect Steam reliable-queue backpressure
Verify retained prefixes before interrupted-download resume
Advertise optional passive AMS server-browser presence

HOST & PLAY

The same package supports a normal Valheim installation that hosts a world.

The server role remains passive on an ordinary client unless that Valheim instance is hosting.

🔐 SECURITY MODEL

IMPORTANT

BepInEx plugins and preloader patchers can execute code.

AutoModSync intentionally allows a trusted Valheim server to provide synchronized files that can execute inside the user's Valheim environment.

Only approve first-contact AutoModSync trust for server operators you recognize and trust.

AutoModSync verifies:

Server signing identity
Signed synchronization manifest
SHA-256 hashes
Bundle integrity
Extracted file integrity
Allowed synchronization destinations
Configured resource limits
Ownership state
Transaction state

SHA-256 verification does not determine whether a third-party plugin or patcher is safe or trustworthy.

AutoModSync is not an antivirus scanner.

SERVER SIGNING IDENTITY

Each AutoModSync server receives its own signing identity.

The private signing key:

BepInEx\config\ValheimAutoModSync.private.xml

must never be distributed to clients.

2.6.1 explicitly ACL-hardens that private key on Windows before it can be used for manifest signing.

THIRD-PARTY MOD REDISTRIBUTION

AutoModSync is a synchronization/transport tool. It does not grant redistribution rights for third-party mods.

Before configuring AutoModSync to provide a third-party mod or related file to connecting clients, the server operator is responsible for confirming that the applicable license or author permissions allow redistribution.

The operator is also responsible for satisfying applicable requirements such as:

Attribution
Copyright notices
License notices
Source availability
Other requirements imposed by the rights holder

A private, password-protected, friends-only, or noncommercial server does not by itself create redistribution permission.

This is especially important for public servers where synchronized files may be distributed to an unrestricted number of players.

Mods whose redistribution permissions prohibit distribution or are unclear should not be synchronized unless the operator obtains appropriate permission.

AutoModSync itself does not bundle arbitrary third-party gameplay mods and does not acquire them from CurseForge, Nexus Mods, Thunderstore, GitHub, or arbitrary external URLs on behalf of a server operator.

Full operator policy:
Third-Party Mod Redistribution Policy

FAIL-OPEN VS FAIL-CLOSED

NON-AUTOMODSYNC SERVER

If a server does not identify itself as AutoModSync during the bounded discovery flow, normal Valheim behavior can continue.

RECOGNIZED AUTOMODSYNC SERVER

Once a connection is positively recognized as AutoModSync, protected synchronization failures do not silently fall back to an unprotected join.

Examples include:

Invalid protocol acknowledgement
Invalid or incomplete manifest
Invalid manifest signature
Declined trust
Server-reported AMS error
Invalid bundle metadata
Corrupt or out-of-order transfer data
Invalid final bundle verification
Unsafe synchronization paths
Resource-limit violations
Apply/restart preparation failure
Failure of the required protected-server access boundary

RESOURCE & PATH SAFETY

AutoModSync safeguards include:

Maximum compressed bundle size
Maximum expanded bundle size
Maximum synchronized file count
Maximum individual file size
Maximum transfer/chunk count
Streaming ZIP expansion limits
Fixed synchronization roots
Rooted/traversal-path rejection
Windows reserved device-name protection
Trailing-period and trailing-space alias protection
Reparse-point / junction redirection protection
Protected AutoModSync identity/config files
SHA-256 verification before live installation

PUBLIC SERVER / LARGE MOD SET SUPPORT

AutoModSync 2.6 introduced a transfer architecture intended to make larger synchronized environments more practical.

IMMUTABLE CONTENT-ADDRESSED BUNDLE CACHE

Identical synchronization requests can reuse the same verified prepared artifact.

FRESH-CLIENT PREWARMING

The common nearly-bare-client package can be prepared during dedicated-server startup.

SINGLE-FLIGHT CONSTRUCTION

Overlapping identical requests share one bundle construction operation.

BOUNDED SCHEDULER

Transfers are admitted through configured active and waiting limits.

AGGREGATE BANDWIDTH CONTROL

Active clients share one server-wide synchronization transfer budget.

STEAM RELIABLE-QUEUE BACKPRESSURE

AutoModSync can delay additional synchronization data when Steam's reliable queue is already under pressure.

EXACT-ARTIFACT RESUME

Disconnected clients do not necessarily need to restart a large synchronized transfer from zero.

SERVER-BROWSER AMS BADGE

Supported servers can advertise passive AutoModSync presence through Steam server rules:

automodsync=<version>
automodsync_protocol=<protocol>

An AutoModSync-aware client can display a local AMS badge beside positively identified server entries.

The advertised Valheim server name itself is not modified.

Server advertisement and client badge display can be disabled independently.

ANTIVIRUS / SECURITY SCANNER NOTES

AutoModSync's source code is public and unobfuscated.

The CurseForge 2.6.1 package contains ValheimAutoModSyncInstaller.exe because the same executable is also AutoModSync's required visible transactional updater.

There is no standalone ValheimAutoModSync.Apply.exe.

The CurseForge package does not bundle BepInEx.

The standalone GitHub/website distribution does include the pinned BepInEx archive.

AutoModSync's Windows executable files currently do not have a publicly trusted Authenticode publisher certificate.

Users should evaluate security warnings rather than blindly ignoring them.

OFFICIAL BUILD VERIFICATION

Official AutoModSync 2.6.1 packages built through the project's GitHub Actions workflows receive:

SHA-256 package digests
GitHub/Sigstore artifact attestations

The CurseForge publishing workflow attests the exact CurseForge ZIP produced before upload.

GitHub CLI verification:

gh attestation verify .\ValheimAutoModSync-2.6.1-CurseForge.zip -R GordonFreesay/ValheimAutoModSync

Successful verification means GitHub found a cryptographically valid attestation for the exact artifact digest under the official AutoModSync repository.

GitHub/Sigstore provenance is separate from Windows Authenticode.

AutoModSync currently does not have a publicly trusted Authenticode publisher certificate, so Windows may still display unknown-publisher or SmartScreen warnings.

Read the release verification documentation

WHAT AUTOMODSYNC DOES NOT DO

AutoModSync does not:

Open a separate synchronization port
Run a generic web downloader
Crawl mod websites
Fetch arbitrary gameplay mods from URLs
Download third-party mods from CurseForge, Nexus Mods, Thunderstore, or GitHub on behalf of the operator
Force-kill Valheim during an update
Ship a standalone ValheimAutoModSync.Apply.exe
Automatically synchronize every server configuration file
Blindly delete unrelated client plugins
Blindly delete locally modified synchronized files
Claim pre-existing matching files merely because they match
Disable normal Jotunn/ServerSync compatibility decisions
Claim third-party plugins are malware-free
Grant third-party mod redistribution rights
Treat GitHub/Sigstore provenance as Authenticode publisher signing