This is the mail archive of the
xconq7@sources.redhat.com
mailing list for the Xconq project.
Re: Screwy UI Resupply Code
- From: Eric McDonald <mcdonald at phy dot cmich dot edu>
- To: Skeezics Boondoggle <skeezics at q7 dot com>
- Cc: xconq7 at sources dot redhat dot com
- Date: Mon, 2 Feb 2004 15:25:13 -0500 (EST)
- Subject: Re: Screwy UI Resupply Code
Hi Skeezics, others,
On Mon, 2 Feb 2004, Skeezics Boondoggle wrote:
> Actually, automatic resupply can get in the way at times. Sometimes, for
> instance, I'll send a bomber out on a long-range mission, while a fighter
> is returning to land and refuel. If the fighter ends up in the same hex
> as the bomber, it'll resupply itself - and I have to turn the bomber
> around and refuel, or try to steal the fuel back from the fighter to
> continue. It's kinda silly. :-)
Agreed. If the materials donor was immobile though, I can't see
that it would be much of a problem.
> However, sometimes if a fighter goes too far out and there's a bomber
> nearby that can refuel it, that's a great way to keep from losing units if
> they're unexpectedly out of range. But since fighters can even refuel
> from destroyers, why build carriers? That could be considered a bug...
Well, if the UI resupply code actually looked at the acp-to-load
and acp-to-unload tables then this could be easily addressed
(without having to create separate fuel types for air units and
sea units).
Eric