AzuCraftyBoxes Fixes & Config 1.5.0

• Toggle nearby-chest materials separately for building, crafting, and machines.
• Keep personal settings for every player, including non-admins.
• Change settings live; customize hotkeys or disable them with None.
• Includes safeguards for stuck crafts and unpaid free-camera building materials.
• Supports the Valheim 1.0 CraftyBoxes rebuild and optional patched Build Camera.

This is the renamed and expanded continuation of AzuCraftyBoxesBuildingOnly. The Thunderstore package ID, DLL, plug-in GUID, and config filename remain unchanged, preserving player settings.

New in 1.5.0

Supports the fedorovdgap AzuCraftyBoxes 1.8.18 rebuild for Valheim 1.0. It replaces the original Azumatt 1.8.15 dependency in this package's manifest. Install one base AzuCraftyBoxes, never both.

The rebuild already uses the current game APIs. This add-on no longer attempts the obsolete Message/Changed/status-effect rewrites. Its remaining ore hook preserves the rebuild's two-argument RPC payload and transferred items' cheated flags. The fermenter safeguard is retained: the inspected rebuild still sends a string where the supplied game expects a numeric prefab ID.

The unofficial Build Camera 1.0 fix, package 1.2.0 is supported as an optional replacement for the original camera. Its already-fixed calls are checked, not patched twice. It still uses the placement flow covered by this add-on's material-consumption checks.

KRINJUN AzuAutoStoreCompat 1.0.0 is optional. Our runtime checks pass with its preloader bridges and Harmony hooks active. It is not required for CraftyBoxes and does not become a dependency of this add-on.

AutoStoreCompat limitation: its published plug-in skips AutoStore's favoriting and MultiUserChest patches. Do not rely on AutoStore favorites to protect slots/items with that combination. This add-on does not restore those AutoStore features or diagnose unrelated inventory movement.

Startup safeguards remain: the base must have completed its checked startup markers; the original failure is logged before cleanup; cleanup errors stay separate; and Loaded successfully appears only after all required add-on initialization completes. A failed base or camera dependency is not repaired or silently accepted.

The remaining CraftyBoxes adapter was read, generated, installed and removed using the supplied Harmony/MonoMod libraries, both with and without AutoStoreCompat. A live Valheim client/server test is still required. See VALIDATION.md for the exact boundary.

Per-player feature switches

The switches are independent, local to each player, and usable by non-admins. Two players beside the same chest can keep different choices.

AzuCraftyBoxes still controls range, eligible containers, YAML exclusions, permissions, its own enabled state, and its per-player Prevent Pulling Logic option. This add-on never approves a pull that AzuCraftyBoxes rejected.

Live changes and hotkeys

Configuration Manager changes take effect on the next relevant action. Saving the generated config file while the game is running also reloads the local values.

Every shortcut is configurable. Set a shortcut to None to disable that hotkey.

Craft-completion fix

AzuCraftyBoxes can defer one crafting ingredient until the craft completes. If the nearby-resource choice changes or a craft is cancelled at the wrong point, its global pending state can become stale and the crafting timer may finish without completing the item.

Each craft is treated as one transaction:

• Captures that player's crafting toggle when the craft actually starts.
• Keeps the same choice through requirement checks, ingredient withdrawal, and completion.
• Clears stale pending-consumption state before a new craft and after completion, cancellation, or closing the crafting panel.
• Resets AzuCraftyBoxes' temporary recipe-scan guard even if another patch throws an exception.

This targets the stuck-started-craft path without changing recipes or crafting speed.

Build Camera material-consumption fix

The add-on marks the successful placement transaction used by Valheim and the unofficial Build Camera Valheim 1.0 fix. It snapshots required amounts before AzuCraftyBoxes runs and audits the amounts afterward.

• If the normal path consumed everything, the fix does nothing.
• If Build Camera/AzuCraftyBoxes missed part of the withdrawal, only the missing remainder is removed.
• It uses the player's inventory first and then only AzuCraftyBoxes-approved nearby containers.
• It respects container access, exclusions, range, and AzuCraftyBoxes' Leave One rule.
• It cannot intentionally charge more than one recipe.

Build Camera is optional (a BepInEx soft dependency only). Use the unofficial package 1.2.0, which retains the original camera DLL version 1.2.10 and GUID. Its package also installs Build Hotbar 0.7.1; that hotbar is independent of our switches. Do not keep the original camera installed alongside it.

Inventory items appearing again

This plug-in does not call Inventory.AddItem and does not move items into a player inventory. No safe AzuCraftyBoxes fix was added for that separate symptom.

The cause is not confirmed. An inventory expansion or automatic storage mod is one possibility. If it happens again:

1. Record which item returned and what action caused it.
2. Save the client BepInEx log and current mod list.
3. Check every equipment, quick, food, ammo, and extra slot supplied by the inventory mod.
4. Do not launch the character without its inventory mod until all special slots are emptied into normal chests.

Those details are needed before patching because guessing at an inventory transfer could duplicate or destroy items.

Multiplayer installation

Install the same version on:

• The dedicated server or host
• Every connecting client

After successful initialization, ServerSync requires the plug-in and a compatible version but synchronizes no gameplay toggle or hotkey. If this add-on stops before version registration, it does not provide version enforcement. Each client controls only its local player's three features. The dedicated server has no local player, so its local toggle values are inert.

Compatibility

Do not install this together with ValheimCompatibilityFixes; both contain the same AzuCraftyBoxes gate. It can be installed with the separate BreedingUpgradesChickenEggFix.

Only the inspected layouts are supported. The original AzuCraftyBoxes 1.8.15 and original camera's obsolete calls are rejected. This release does not patch any dependency's ServerSync code. The camera package retains its own older ServerSync; inspect its startup/network logs separately, especially when used without a preloader bridge. An initialized plug-in instance alone is not proof that all of a third-party mod's network behavior works.

Update from an earlier release

1. Close Valheim and stop the server.
2. Replace the older add-on with AzuCraftyBoxesBuildingOnly-1.5.0.zip on the server and every client.
3. Disable/remove Azumatt-AzuCraftyBoxes-1.8.15 and install fedorovdgap-AzuCraftyBoxes-1.8.18 everywhere. Check that the profile contains only one base AzuCraftyBoxes.dll.
4. If using Build Camera, replace its original package with the unofficial 1.2.0 package. Keep only one camera DLL. If the camera is also on the server, use the same replacement there.
5. Install AutoStoreCompat only if you use AzuAutoStore and want that separate compatibility bridge. Keep both its patchers/ and plugins/ components; it requires a restart.
6. Existing add-on settings and hotkeys are preserved. Restart, check both mods' startup logs, then follow the copied-profile checklist below.

For a manual installation, place our AzuCraftyBoxesBuildingOnly.dll in BepInEx/plugins/AzuCraftyBoxesBuildingOnly/. Dependencies are installed separately; this ZIP contains only our DLL.

Config

Generated at:

BepInEx/config/local.valheim.azucraftyboxesbuildingonly.cfg

See CONFIG_REFERENCE.md for the full behavior and migration reference.

Required copied-profile test

First install the supported base rebuild and confirm its startup succeeds. Then verify the add-on logs Loaded successfully. If it reports a dependency or adapter failure, the gameplay checks below are blocked. Use STARTUP_DIAGNOSTICS.md to capture the first error.

1. Craft an item using only nearby-chest materials and confirm the timer finishes and creates exactly one item.
2. Cancel a one-ingredient craft, then craft another item and confirm both inventory and chest amounts are correct.
3. Toggle crafting through Configuration Manager during separate crafts and confirm no craft becomes stuck.
4. Place the same piece normally and through Build Camera free-cam; each must consume exactly one recipe.
5. Repeat with two non-admin players beside the same chest using opposite settings.
6. Check client and server BepInEx logs for Harmony or AzuCraftyBoxes Fixes & Config errors.
7. Fill a smelter with ore, and a fermenter with one base from a nearby chest. Confirm exactly the accepted amount leaves the chest and the machine starts processing.
8. Test a normal crafting station and an upgrader station; only the relevant resources should be charged.
9. With AutoStoreCompat installed, repeat these checks and one deliberate AutoStore transfer using unimportant items. Do not use disabled favoriting as protection.
10. Compare carried/chest ingredients and their existing cheated flags. A clean craft fully funded by carried materials must not inherit a flag from an unused nearby chest.

Uninstall

Remove this package from the server and every client, then restart. AzuCraftyBoxes returns to its normal behavior. The add-on stores no world objects or item data.

Complete source is included under src/ and released under the MIT License.

Changelog

1.6.0

• Support official Azumatt AzuCraftyBoxes 1.8.19 through one verified profile shared by both startup gates and patch selection. Preserve loaded-instance, active-watcher, completed-status-effect and installed-callback checks.
• Use official 1.8.19's corrected fermenter transfer implementation. Retain the old replacement only for the explicitly supported legacy fedorovdgap 1.8.18 rebuild.
• Keep ore cheated-item metadata handling and existing per-player controls, material safeguards, crafting state cleanup and optional-camera behavior.
• Update the manifest to require the official base. Preserve plugin/DLL/config identities and local settings.
• Add focused profile, executable patch-plan and startup-order checks; remove the old AutoStoreCompat bridge from recommended setup instructions.
• Live acceptance status is maintained in docs/VALIDATION.md; managed checks alone are not a gameplay claim.

1.5.1

• Keep required CraftyBoxes startup running when the read-only optional Build Camera API/startup check fails; report the camera problem as a separate warning.
• Keep optional camera targets out of the required adapter installation list.
• Preserve strict base-mod checks, original-error-first installation logs, separate cleanup errors and success logging only after required initialization.
• Preserve independent player settings, hotkeys, saved config, crafting/transfer fixes and normal Player material-consumption checks.
• Remove the unavailable unofficial camera listing as a current installation recommendation; retain checks for existing compatible patched copies. No camera DLL or new hard dependency is included.
• Clarify that this add-on neither repairs nor disables a failing camera. A camera warning leaves its free-camera behavior unvalidated.
• Record successful 1.5.0 startup in a supplied Valheim 1.0.12 dedicated-server log; 1.5.1 gameplay still requires in-game testing.

1.5.0

• Support the fedorovdgap AzuCraftyBoxes 1.8.18 Valheim 1.0 rebuild; update the required Thunderstore dependency.
• Recognize the unofficial Build Camera 1.0 fix 1.2.0 while retaining normal/free-camera consumption safeguards.
• Check the replacement's native APIs instead of reinstalling obsolete compatibility rewrites.
• Preserve the fork's two-field ore RPC payload and cheated metadata; retain the single-transfer fermenter fix with numeric prefab IDs.
• Make add-on patch resolution independent of global name-only reflection overrides; verify coexistence with AzuAutoStoreCompat's preloader and runtime hooks.
• Retain strict dependency-health checks, original-error-first logs, separate cleanup errors, independent player settings, hotkeys, config migration, and crafting safeguards.
• Update installation guidance for replacement packages and AutoStoreCompat's disabled favoriting/MultiUserChest patches.
• Validate actual ore-adapter installation/removal with the supplied Harmony/MonoMod; live Valheim gameplay still requires testing.

1.4.1

• Check AzuCraftyBoxes startup completion before registering version checks or installing integration patches.
• Log the original initialization exception before any cleanup, including the failing stage and method.
• Replace blanket rollback with per-target cleanup; continue after cleanup errors and report unverified/partial rollback honestly.
• Preflight all adapter targets using the installed MonoMod reader before applying any patches; reject unreadable legacy methods instead of trying a late IL rewrite.
• Require actual Harmony installation to succeed for every target before declaring the add-on ready.
• Keep surviving callbacks and the Update loop inactive after startup failure.
• Preserve per-player switches, saved settings, configurable/disabled hotkeys, crafting cleanup, transfer metadata, and optional Build Camera material checks.
• Add runtime startup/cleanup regression tests and correct the prior compatibility claims: the supplied base 1.8.15 ServerSync error is not fixed, and gameplay tests remain blocked.

1.4.0

Historical release: its offline IL checks did not establish runtime installation. The startup/rollback and compatibility claims below are superseded by 1.4.1.

• Rebuild against the supplied Valheim 1.0.12 managed assemblies and current BepInEx core.
• Adapt AzuCraftyBoxes 1.8.15 and optional Build Camera 1.2.10 API calls in memory; preserve their installed files.
• Update ore RPC payloads and fermenter prefab-hash payloads for the actual 1.0 API; retain each transferred ingredient's cheated state.
• Stop fermenter chest filling after one accepted item, avoiding the old loop consuming additional bases.
• Match normal/upgrader resource selection in requirement checks, recipe amounts, consumption and building audits.
• Preserve cheated-material metadata for eligible chest resources used in crafting, building, cooking and ore processing.
• Keep building and machine choices independent while a craft timer is active.
• Use per-call building audit state, explicitly ignore unassigned hotkeys, validate required game methods, and roll back partial patch installation on failure.
• Preserve package identity, configuration names, existing settings and independent non-admin player control.

1.3.1

• Correct the AzuCraftyBoxes 1.8.15 crafting-state type lookup from AzuCraftyBoxes.ConsumptionManager to AzuCraftyBoxes.Util.Functions.ConsumptionManager.
• Restore the intended stale deferred-consumption cleanup for one-ingredient crafts.
• Make the pending-consumption property a required runtime member so future incompatibilities disable the add-on safely instead of silently skipping the advertised crafting fix.
• Remove the resulting HarmonyX AccessTools.TypeByName warning during startup.

1.3.0

• Rename the visible plug-in and README title to AzuCraftyBoxes Fixes & Config while retaining the existing Thunderstore package ID, plug-in GUID, DLL name, and config filename for a clean update.
• Treat each started craft as one transaction and preserve its crafting-toggle choice until completion.
• Clear stale AzuCraftyBoxes deferred one-ingredient consumption state before and after crafting, cancellation, or closing the crafting panel.
• Guarantee cleanup of AzuCraftyBoxes' temporary recipe-scan guard after errors.
• Mark the exact successful placement transaction used by normal building and Build Camera Custom Hammers Edition.
• Audit building-resource consumption after AzuCraftyBoxes runs and remove only a missing remainder from the player or eligible nearby containers.
• Respect AzuCraftyBoxes container access, range, exclusions, pull rules, and Leave One behavior in the placement fallback.
• Document that this plug-in never inserts items into player inventories; unexplained returning items need an inventory-mod/log diagnosis rather than a speculative transfer patch.

1.2.0

• Replace the one shared server-controlled mode with independent per-player building, crafting, and machine switches.
• Make every gameplay switch available to non-admin players and intentionally exclude it from ServerSync.
• Add configurable local F8, F9, and F10 hotkeys; any shortcut can be rebound or set to None.
• Apply Configuration Manager changes immediately and reload local config-file edits while the game is running.
• Keep required-mod/version enforcement on the server without synchronizing player preferences.
• Fix chest-funded Build Camera placement by keeping the building context active through Player.UpdatePlacement, where Valheim actually consumes resources.
• Cover TryPlacePiece, every current PlacePiece overload, and the full machine interaction/hover paths used by AzuCraftyBoxes 1.8.15.
• Migrate legacy Full, BuildingOnly, and Disabled values to the equivalent three local switches and remove obsolete lock/mode entries.
• Add a two-client same-zone test matrix and updated source/build documentation.

1.1.0

• Require the package on the dedicated server and every client through version checking.
• Synchronize Lock Configuration, Mod Enabled, and Mode from the server.
• Keep the F8 key assignment local while making authorized mode changes global.
• Block non-admin clients from overriding a locked server mode.
• Live-reload and broadcast dedicated-server config-file changes.
• Fail closed if AzuCraftyBoxes' bundled ServerSync cannot be initialized.
• Correct the multiplayer installation and configuration documentation.

1.0.0

• Add Full, BuildingOnly, and Disabled modes for AzuCraftyBoxes.
• Default to nearby-container use for structure placement only.
• Add an F8 runtime switch between Full and BuildingOnly.
• Preserve AzuCraftyBoxes container maintenance and its own enable/permission decisions.
• Add compatibility notes and a copied-profile test checklist.
• Include complete Thunderstore listing, configuration and source-build references plus high-resolution icon masters.