and doesn't try to track the individual consumptions and productions as calculating and storing those requires extra time which slows down auto-evo unnecessarily

This is mostly just copy-pasting but I'd like to see in any PR solving this some good architectural combining of the two method variants as much as possible to reduce real code duplication (but the more important consideration is raw performance, so some dirtyness here would be fine as this is a pretty well contained part that's critical for speed).