Conversation
|
@copilot |
Co-authored-by: MaksyKun <77341370+MaksyKun@users.noreply.github.com>
Addressed in commit I fixed the crafting-limit lifecycle by propagating instant-collect finalization results (instead of always returning enqueue success), so limit/storage failures are no longer masked and shift-multicrafting stops at the first real limit failure. I also added regressions covering limit-1, exact-limit, finished-but-uncollected, instant-collect limit behavior, and shift-multicraft stop behavior, while keeping the existing cooldown/reload/atomic double-consumption persistence tests in place. |
Splitted some work across several branches and decided to merge them into this one here due to out current capabilities on deployment:
instant_collect: true/falseintoconfig.yml. When craftingTime ist configured to 0 or -1, it is instantly crafted and added to the inventory (or dropped on full inv) to skip queue slots