> 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.
count distance in squares they travel. 5x5=5 in glob2 ;) (diagonally they can travel sqrt(2)* further) > 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... only knowing the distance to wheat is painfully little information to implement 3 point path finding but is all we got atm. leo _______________________________________________ glob2-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/glob2-devel
