v4.25.0: audit storagearea material pickup flow
Curse Maven Snippet
What's new
The Siege Overhaul v4.25.0
Deep audit of how a Workers 2 builder actually fetches materials from a storagearea. Fixes one silent failure mode and a search-anchor mismatch.
What changed
Traced the full material pickup path: GetNeededItemsFromStorage state machine, AbstractChestGoal.scanAvailableStorageAreas, and StorageArea.canWorkHere. Two real problems came out of it.
-
Storageareas in Workers 2 gate access by job type. If your storagearea does not have Builders enabled in its GUI, the builder silently reports "No available storage found nearby" even though your storagearea is right there. Fortify Perimeter now checks that bit up front and gives you a specific message telling you to open the storagearea and toggle Builders on.
-
Our storagearea search was anchored on the builder. Workers 2's runtime search is also builder-anchored, but the builder moves as it walks the wall. The Core is the stable centre of your perimeter, so the up-front check now anchors on the Core. That matches where the builder will spend most of its time and stops false negatives when the builder is standing at one edge and the storagearea is at the other.
Also: when a storagearea is in range but does not have Builders enabled, we still surface it as a fallback candidate so we can emit the specific "turn Builders on" message instead of the generic "not found" one.
Compatibility
No save data changes. Existing worlds keep working.
All Relations
- All Relations
- Embedded Library
- Optional Dependency
- Required Dependency
- Tool
- Incompatible
- Include