

In general though I think the game is too far along in development to change such fundamental values that may break codes that haven't been touched in years. Longer source regen times (and correspondingly larger amounts) might help with roaming harvesters. Bigger links would let you use them as sinks for remote haulers more easily. Other constant changes would have similar effects. I also may add new harvesting techniques based off harvest boost and unboost. You'd be able to harvest out a source into the container without worrying about spillover and move on to a new source. The former being a bit wasteful on CPU, but easier to code and less liable to edge cases screwing things up. The library has a few main components: the main Dashboard, an assortment of Widgets, and some helpful Metrics calculations to organize data for the widgets. Right now there's a few solutions to container mining, and most people either go for "haulers tied to a route and sized for the distance" or "wild haulers which can pull from any source container and are full sized". screeps-viz The screeps-viz repo is up on GitHub and the package is available for install through npm.

I can't decide if larger containers would make things easier or harder.
