From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20383 invoked by alias); 14 Aug 2004 03:50:30 -0000 Mailing-List: contact xconq7-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: xconq7-owner@sources.redhat.com Received: (qmail 20376 invoked from network); 14 Aug 2004 03:50:29 -0000 Received: from unknown (HELO rwcrmhc12.comcast.net) (216.148.227.85) by sourceware.org with SMTP; 14 Aug 2004 03:50:29 -0000 Received: from [192.168.181.128] (c-67-172-156-222.client.comcast.net[67.172.156.222]) by comcast.net (rwcrmhc12) with ESMTP id <2004081403502801400r3ible>; Sat, 14 Aug 2004 03:50:29 +0000 Message-ID: <411D8BE5.5040508@phy.cmich.edu> Date: Sat, 14 Aug 2004 09:19:00 -0000 From: Eric McDonald User-Agent: Mozilla Thunderbird 0.7.1 (Windows/20040626) MIME-Version: 1.0 To: Elijah Meeks CC: xconq7@sources.redhat.com Subject: Re: Wrecked-Type Doesn't Apply to Detonating Units References: <20040813234600.55463.qmail@web13122.mail.yahoo.com> In-Reply-To: <20040813234600.55463.qmail@web13122.mail.yahoo.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004/txt/msg00893.txt.bz2 Elijah Meeks wrote: > It seems that the wrecked-type-if-destroyed table > doesn't apply to units destroyed by detonating units. > Is this by intention? I don't recall intentionally setting it up that way. I suppose it could be made to do so, but I am not sure whether that would be a good idea or not. What if a detonating unit can also destroy another unit through conventional means? I guess we could pretend that this is never a real game design possiblility, and let the 'wrecked-type-if-destroyed' table handle detonation deaths as well. If we don't, then probably YANT (yet another new table) is called for: 'wrecked-type-if-blown-up', perhaps? Eric