Rewben ValheimRAFT 5.1.102

Maintained at https://github.com/Rewben/ValheimMods on rewben/main, based on ValheimRAFT-v5.1.1. This fork integrates portal synchronization corrections and RaftRebalance behavior. It retains upstream plugin GUIDs, assembly names, prefab names, and saved-world keys. All clients and the server need the same fork version.

5.1.102 corrects the deployment health check that prematurely stopped the first 5.1.101 maintenance attempt: the container's informational log-filter declaration was mistaken for a plugin failure. Full server/profile rollback was verified. The portal and rebalance implementation is unchanged; gameplay acceptance remains pending. Deployment evidence is now returned over the same SSH connection.

Build and package (Windows PowerShell 7)

Install .NET SDK 8.0.425 or a newer 8.0 patch. Supply your own legally installed Valheim managed assemblies and BepInEx core. No Unity editor, private libs submodule, game launch, or plugin installation is needed.

git clone --filter=blob:none --branch rewben/main https://github.com/Rewben/ValheimMods.git
Set-Location ValheimMods
git remote add upstream https://github.com/zolantris/ValheimMods.git
.\tools\Build-Fork.ps1 -ManagedPath 'E:\SteamLibrary\steamapps\common\Valheim\valheim_Data\Managed' -ProfileBepInEx 'C:\path\to\profile\BepInEx'
.\tools\Package-Fork.ps1 -ManagedPath 'E:\SteamLibrary\steamapps\common\Valheim\valheim_Data\Managed' -ProfileBepInEx 'C:\path\to\profile\BepInEx' -Python 'C:\path\to\python.exe'

Public reference dependencies and hashes are pinned in tools/reference-lock.json: Jotunn 2.30.2, PlanBuild 0.20.0, PlantEasily 2.3.0, Gizmo 1.16.0. Cached references live in ignored .references/. A matching installed reference can be reused; otherwise the build downloads the pinned public package. Game/reference DLLs are never added to Git or the ZIP. Package-Fork.ps1 requires committed source, runs the headless regression suite, builds, and writes the ZIP, SHA256, and metadata under dist/. Startup logs and metadata identify the source commit and upstream base. The ZIP DLL allowlist contains only RAFT's six runtime assemblies.

Python 3 is needed for the deployment fixture checks during packaging. CI runs headless production-code contract tests with inspected game API doubles, Harmony instruction checks, and deployment/rollback fixture tests. These checks do not simulate Unity physics or establish multiplayer/gameplay acceptance. Release binaries are built locally with game references. Legacy upstream build workflows are archived under .github/upstream-workflows/; they are not active fork release workflows.

Installation and configuration migration

Quit Valheim and Gale. Back up the whole Gale profile, including Gale's profile metadata. Remove upstream ValheimRAFT and RaftRebalance from that profile, then import the local ZIP in Gale. Keep Jotunn and other unrelated mods. Disable upstream RAFT updates for this profile; install future fork releases explicitly. Retain the legacy vhrf.RaftRebalance.cfg for the first startup. Never install both implementations. Startup rejects a companion DLL even if its file was renamed.

The first fork startup backs up zolantris.ValheimRAFT.cfg to .before-rewben and migrates before other RAFT settings bind. Existing integrated settings win; otherwise legacy companion overrides win, followed by existing RAFT settings, then fork defaults. [Rebalance Migration] Schema = 1 prevents stale legacy files from overriding later edits. Unrelated configuration stays in the same file. Migration completion is logged. The new settings use Jotunn's synchronized, admin-only configuration tags. Migrated recipe controls live in [Rebalance Recipes], separate from the original [RecipeConfig] fallback values.

[Rebalance] contains MaxHullClearance (1.5 m), BlockCannonHarvesting, EnforceRaftLocks, LegacyRefunds, HaulStaminaPerMeter (10 by default, retaining an existing RAFT value), and optional PortalDiagnostics. Recipes retain their prefab names under [Rebalance Recipes]. Locks disable flight, ballast, terrain ramming, land vehicles, and public administrative commands. Ordinary creative editing remains available, with non-admin lift clamped to 0–5 m; an existing lift of 0 stays 0. Hull rebuilds and per-ship edits reapply the clearance cap. Rams hit creatures; cannons retain damage to creatures, spawners, and player buildings while blocking harvesting. Hauling initializes at startup/synchronization and stops at exhaustion.

All ten supplied recipe overrides are retained. The turret override remains available for its prefab; upstream 5.1.1 keeps turret registration behind DEBUG, so this fork does not expose that unfinished feature. Eight repriced build pieces record their refundable costs in vhrf_paid_v1. Existing markers are honored; unmarked legacy pieces use the companion's original fallback costs when enabled. Recipe changes cannot raise a marked piece's refund.

Portal behavior and admin tools

Position and rotation updates preserve portal ZDO IDs. Portals belong only in their dedicated portal-sector registry, once each. Tracking is unique by valid ID and pruned; resets clear stale registry references before ZDO pooling. The scene guard only reuses an existing instance of the same ship-portal record. Different overlapping portals keep their separate IDs. Server work uses seconds, honors the configured interval, and skips unloaded vehicles without ending its worker. When TargetPortal manages a portal, vanilla pairing is bypassed. The pairing hook checks the current game's GetPortalList call and fails visibly if that contract changes.

Admin F5 console commands:

vehicle portals audit [ship-id]
vehicle portals repair <audit-id>
vehicle portals repair <audit-id> --remove <ZDO-id>,<ZDO-id> --confirm

Audits list record IDs, instance IDs/positions, ship IDs, and registry anomalies. The console returns a bounded preview; complete server reports are saved under BepInEx/config/PortalAudits/. Audits belong to the requesting server admin and expire after five minutes or a world change. Repair without --remove corrects registrations and removes extra live instances sharing one record. It does not delete distinct saved records. Saved deletion requires explicit IDs from that fresh audit plus --confirm. All selections are validated before mutation. Repair creates no resource refunds. Keep the canonical instance and its record.

Main-server maintenance and full rollback

Prepare and verify a complete staged BepInEx inventory before touching the active installation. Use tools/Push-Fork.ps1 with -BepInExPath pointing at that stage and -ForkMetadataPath pointing at the ZIP metadata. It uses one SSH password prompt, never captures a password, preserves existing server configuration, and mirrors both persistent and runtime plugin/patcher trees. The helper runs on the Linux host, not Windows Docker Desktop. Pass -ResultPath 'C:\path\to\deployment-result.json' to save startup logs, migration settings, backup checksum, and persistent/runtime DLL hashes locally over that same connection, on either startup success or failure. SSH password entry remains attached to its normal console and is not captured.

Log everyone out before maintenance. Stop gracefully with the existing 120-second timeout. The tool backs up the entire stopped /config, including world chunk directories, verifies gzip readability and checksum, and retains prior runtime trees with checksum inventories. It then swaps prepared trees. Automatic vanilla updates remain enabled. Startup checks fork version/commit, migration completion, companion absence, plugin-loading errors, game-version changes, and connection. Readiness is only the start of the gameplay validation below.

If validation fails, quit clients and use full rollback (Windows PowerShell):

.\tools\Push-Fork.ps1 -Server '<SSH-host>' -Container '<container>' -ServerRoot '/srv/games/valheim/<server>' -RollbackDeployment '<deployment-id>' -FullRollback

This stops the server and restores the saved world/chunks, configuration, persistent mods, and runtime mods together. Test-session activity is discarded. Restore the matching local profile backup and Gale metadata with Gale closed. The ordinary -RollbackDeployment option restores only mods/configuration and is insufficient for this maintenance test. Backups are retained without automatic deletion. If restoration itself fails, the helper leaves the server stopped.

Required gameplay acceptance

Use one admin and one non-admin client on the main server. Record baseline and final audits. Check ship rotation/movement across sector boundaries, ten area unload/reload cycles, reconnects, portal travel both ways, bed respawning, and three save/reload cycles. Run 30 minutes with PortalDiagnostics = true and check stable record/live-instance counts for the same loaded ships, bounded tracking, and no new invalid 0:0 pairings. Check creative/admin permissions, clearance, hauling/exhaustion, creature-only rams, cannon targets, all available recipes, and old/new marked refunds. Verify ships, inventories, and unrelated settings. Do not infer duplicate saved portals from overlap or delete them automatically.

See VALIDATION.md for recorded evidence and outstanding checks. A release candidate is not gameplay-certified until those observations are recorded.

Future upstream updates

Fetch upstream, create rewben/update-<release> from rewben/main, and merge a selected upstream release tag. Review overlapping portal/compatibility fixes and keep the fork identity/version policy. Recheck game API/Harmony contracts, run headless tests, build locally, and repeat maintenance/gameplay checks. Increment the fork revision and version, commit, tag rewben-v<version>, and publish the ZIP/checksums/source metadata. Merge the reviewed update branch to rewben/main. Never use Gale's upstream RAFT update button to update this fork.

Attribution

ValheimRAFT/ValheimMods by zolantris and contributors, with earlier ValheimRAFT contributors retained in upstream documentation. Upstream GPL-3.0 licensing is retained in LICENSE; ServerSync's license is included separately. Rewben fork changes use the same project license. RaftRebalance 1.2.0 (vhrf, supplied by the user) contributed the balance policy, recipes, migration keys, and paid-cost compatibility requirements. This is a typed implementation within RAFT; the companion binary and its Harmony patches against RAFT are not redistributed.

The optional Prepare-Fork.ps1 / Install-ForkClient.ps1 tools prepare a verified profile snapshot and staged inventory, then install the staged plugin tree with Gale closed. The installer updates only that profile's mod list, replacing upstream RAFT and RaftRebalance with a local fork entry. It does not export Gale auth data. Restore-ForkProfile.ps1 restores the profile ZIP and its exact metadata row with Gale closed; schema/identity changes are rejected. Other profiles are preserved.

Changelog

Package and runtime 5.1.106

• Rebuild TargetPortal's cached portal set after explicit cleanup, including dead pooled ZDOs whose network IDs and hash codes changed. Clear temporary map pins after rebuilding so the deleted records cannot recreate them before the next TargetPortal refresh.
• Match the game record's mutable-ID equality/hash behavior in regression doubles and verify stale pooled records are removed while the surviving portal remains.
• Includes the confirmed position cleanup introduced in 5.1.105. Server and all clients must use 5.1.106. No saved-record cleanup runs during installation.

Package and runtime 5.1.105

• Audit position-based saved-portal duplicates using ship, prefab, coordinate frame and unrounded local 3D position with a 1 mm tolerance. Keep one portal per group; missing or invalid local positions are excluded from cleanup.
• Print duplicate counts and the exact short-ID --dedupe --confirm command. Audit stays read-only; complete keep/remove selections remain in the report.
• Delete only after explicit admin confirmation, in batches of at most 32 with network deletion acknowledgements. Stop on changed records, keepers, sessions or worlds. Append repair selections/results to the audit file without refunds.
• Rebuild portal registries in one pass and detach deletion batches efficiently. Replace the large repair-ID broadcast with a compact registry refresh signal.
• Clear TargetPortal's temporary map pins and prune stale cached records after repair. Unrelated saved map pins are unaffected.
• Add production-code tests for large cleanup, position boundaries, invalid coordinates, different ships/types, confirmation, cancellation and map refresh.
• Server and clients must all update to runtime 5.1.105.

Package and runtime 5.1.104

• Limit the server audit preview to ten portal records and show the total count and audit ID prominently at both the start and end of the response.
• Replace the client's unbounded full-record dump with a small loaded-instance counter. Preserve complete server reports in PortalAudits/<id>.txt.
• Use six-character, case-insensitive audit IDs with collision checks against active audits and saved report filenames. Keep admin/session ownership and five-minute expiry checks.
• Periodic portal diagnostics no longer format a full per-record report only to discard it and print the first line.
• Add regression coverage using the production audit commands with 16,248 saved records. Existing saved portals and deletion rules remain unchanged.
• Server and clients must all update to runtime 5.1.104.

Package 5.1.103 / runtime 5.1.102

• Put runtime DLLs and their Assets hierarchy under an explicit plugins/ folder so Gale/r2modman preserve sail textures and translations.
• Rebuild with virtual source paths and without debug symbols.
• Remove the bundled ServerSync binary's original machine-specific CodeView path; executable code, assembly identity and public attribution are retained.
• Ship public installation documentation instead of developer build/deployment notes.
• Validate allowed files, privacy patterns, checksums and asset placement before accepting the final ZIP. No changes to gameplay, saved identifiers or runtime network version are included in this packaging release.

Runtime 5.1.102

• Fix the deployment check's false alarm on the container's informational log-filter declaration and return startup evidence over the deployment connection.

Runtime 5.1.101

• Initial fork integrating portal synchronization corrections, TargetPortal pairing compatibility, admin portal tools and native RaftRebalance policy/migration/refunds.