On 3/25/06, Kyle Lutze <[EMAIL PROTECTED]> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > � wrote: > > Hi everyone, > > > > We have understood that most people want a priority system for buildings > > construction. We might implement this when we (Nuage and I) get some time. > > Please summary how you want the system to work. > > > > Thanks, > > > > Steph > > > > automatically. > order: > 1. inns > 2. swarms > 3. cannons and walls > 4. schools > 5. barracks, tracks, pools > 6. markets > > I think this would be the easiest to keep from micromanagement. > > > Kyle > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.2.2-ecc0.1.6 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFEJeDPVFIipMnXxfYRAk9iAKCNCZF7pbfJiWbDNUYAVLKyY0tHvgCfWqs3 > LBeYgf8uImlDXaa3o3NyiAA= > =C7O0 > -----END PGP SIGNATURE----- > > > _______________________________________________ > glob2-devel mailing list > [email protected] > http://lists.nongnu.org/mailman/listinfo/glob2-devel >
Thats not what he means, as there is already a priority system like that. nct, I have summarrized how I would like the system to work in the other thread, first post, however, Kai believes that proximity should also be considered when balancing priority. My idea, just try to have it consider both proximity and prioirty that is set by the user, don't put any logic behind it (it could be as dumb as proximity/priority to determine overall priority rating). We will then test the system, and see how well it considers priority and proximity. Most likely, on the first attempt, it won't work well, but with further fine tuning, (maybe proximity/(priority*3) or something like that, or entirely new consideration formula), we will get it right. So, like i said, just have it able to consider both proximity and priority, and we will work from there to determine whats really neccessary.
_______________________________________________ glob2-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/glob2-devel
