Well, not halfway across the map... sorry that was an over-exxageration. I meant it seemed to go to a resource location that's just not the closest one. Anyway I'll do a bit more observation on this, as Bradley said, it could be a bug.
So does the algorithm for the resource pickup make the worker pick up the resource that has the lowest distance value from it when it was first allocated the task? If that's the case maybe a possible optimisation is to make it consider the resources that are close to the target building as well? And a further optimisation is to make it find the nearest resource located along the path to the target, but that might be quite a heavy process... On Mon, Jul 21, 2008 at 11:27 AM, Bradley Arsenault <[EMAIL PROTECTED]> wrote: > The algorithm should not be sending workers half way across the map for a > resource that could be acquired closer ever unless there is a bug. This is > because it always chooses the nearest square of that resource in terms of > path distance. The > > -- > Extra cheese comes at a cost. Bradley Arsenault. > > _______________________________________________ > glob2-devel mailing list > [email protected] > http://lists.nongnu.org/mailman/listinfo/glob2-devel > >
_______________________________________________ glob2-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/glob2-devel
