Floating priorities
Posted: Sun Mar 08, 2009 6:54 am
I'd like if the priority for something depended on how much work needed to be done, how close the worker is, and then only some influence for time, user override, etc.
The idea is that if an inn is at 49/50 wheat it shouldn't grab a worker from across the map. Instead a local worker should be found, and only a single worker at that. 45/50 might earn 5 workers, but only if they were already close, and more likely it'd have to wait until 30/50 or something to earn a bunch.
If you place a new building it would peel off a few workers as they finish their current jobs, which would immediately lower the priority of that building (not waiting for them to pick up a resource), preventing any more from peeling off. This might go back and forth a bit, but hopefully can be tweaked to converge on a stable point.
This would replace the need for explicit worker controls in most buildings. User priority multiplier, rather than worker count, might be sufficient for the swarm.
The idea is that if an inn is at 49/50 wheat it shouldn't grab a worker from across the map. Instead a local worker should be found, and only a single worker at that. 45/50 might earn 5 workers, but only if they were already close, and more likely it'd have to wait until 30/50 or something to earn a bunch.
If you place a new building it would peel off a few workers as they finish their current jobs, which would immediately lower the priority of that building (not waiting for them to pick up a resource), preventing any more from peeling off. This might go back and forth a bit, but hopefully can be tweaked to converge on a stable point.
This would replace the need for explicit worker controls in most buildings. User priority multiplier, rather than worker count, might be sufficient for the swarm.