NearbyCrafting

[1.0.2] - 2026-06-20
Fixed
- Recipes consuming **double** resources in multiplayer. When an ingredient was covered by the
**toolbelt/hotbar**, it was also removed a second time from a nearby container, so a craft cost
twice its listed price (and canceling refunded only the standard amount). The brittle
`RemoveItems` IL transpiler was replaced with a prefix that debits backpack → toolbelt → nearby
storage for the *remaining* amount at each step, so each ingredient is removed exactly once and
it no longer relies on IL matching.
- A **tracked recipe** showed its ingredients as `0/N` when the resources were in a nearby
container (e.g. `0/2` even though you could craft it). The tracker HUD now adds the
nearby-storage count and recomputes completeness on each refresh, so it matches the crafting
window.
- Party **allies** could not craft/repair/upgrade using resources in a friend's **locked**
containers. Access now mirrors the game's own check (owner, password holders, **or** an ally of
the owner).
- Crops not growing: the nearby-storage scan (`ReloadStorages`) took a per-chunk **read lock** that was
not released in a `finally`; an exception mid-scan could leak the lock and block writes to that
chunk. The scan is now wrapped in try/catch/finally so the lock is always released, and a bad
chunk is logged and skipped instead of aborting the scan.

[1.0.3] - 2026-06-28
Fixed
Item duplication from vehicles in multiplayer. Crafting, repairing, upgrading, reloading, or refueling with materials stored in a vehicle removed them only on your client, never on the server. Because a vehicle's inventory is server-authoritative, the materials reappeared on the next resync, so you got the crafted result for free. The mod now pushes the vehicle inventory change to the server (the same sync the game's own vehicle storage uses), so the items are removed for real. Nearby containers were never affected (they already synced correctly).

[1.0.4] - 2026-07-02
Fixed
- Config settings were ignored in multiplayer. Every option (allowLockedContainers, allowAllContainers, range, enableFromVehicles, the enableFor* toggles, modEnabled) is evaluated on the crafting player's own client, so on a dedicated server the client read its own local config.xml and ignored the server's. Setting, for example, allowLockedContainers=false on the server did nothing. The server now pushes its config to every client as they join, so the server's config.xml is authoritative and all options take effect in multiplayer.
Note
- In multiplayer, set your options in the server's config.xml; client copies are overwritten by the server's on join.