Blood Altar loop
Input: LP generation → Store: altar capacity → Process: altar recipes → Output: slates, orbs, and progression components.
Inputs, storage, processing, and outputs. Once you can see those four parts, troubleshooting becomes much faster.
Input: LP generation → Store: altar capacity → Process: altar recipes → Output: slates, orbs, and progression components.
Input: network refilling → Store: player-bound capacity → Process: activations → Output: utility, mobility, and bound-item effects.
Input: Will acquisition → Store: Will containers → Process: Hellfire Forge → Output: Will-based components and progression tools.
Input: valid structure + activation → Store: required player/resource state → Process: ritual effect → Output: automation or large-scale utility.
Speed cannot process resource that is not present.
Keep an operating buffer instead of spending to zero.
Will requirements are separate from normal ingredients.
Debug systematically before rebuilding.