From: Eric McDonald <mcdonald@phy.cmich.edu>
To: Elijah Meeks <elijahmeeks@yahoo.com>
Cc: xconq7@sources.redhat.com
Subject: Re: Wrecking Issues
Date: Sat, 10 Jul 2004 21:40:00 -0000 [thread overview]
Message-ID: <40EFF87F.3050203@phy.cmich.edu> (raw)
In-Reply-To: <20040709165424.17238.qmail@web13121.mail.yahoo.com>
Elijah Meeks wrote:
> Is there any chance someone could patch the wrecking
> code so that a half-built unit doesn't wreck into a
> fully functional version of its wreck-type? Maybe a
> wreck-type-if-insufficient-cp or something?
I just checked in what I think is probably a suitable fix. If the unit
being wrecked is incomplete, then the damage code simply disposes of it.
If there are cases where this is unsuitable, then the alternative would
be to make the change-type code (used by wrecking) to scale the wrecked
type's CP to the unwrecked type's CP, in a manner similar to what is
already done with ACP and HP. But, I'll leave the fix like it is for now.
Eric
next prev parent reply other threads:[~2004-07-10 14:09 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1088896371.19592.ezmlm@sources.redhat.com>
2004-07-03 23:21 ` Just say no to bungee paratroopers Henry J. Cobb
2004-07-03 23:55 ` Eric McDonald
2004-07-04 0:55 ` Hans Ronne
2004-07-04 1:39 ` Eric McDonald
2004-07-04 3:17 ` Hans Ronne
2004-07-04 1:14 ` Jim Kingdon
2004-07-04 3:37 ` Henry J. Cobb
2004-07-04 6:13 ` Henry J. Cobb
2004-07-04 15:13 ` Hans Ronne
2004-07-04 18:01 ` Jim Kingdon
2004-07-04 21:38 ` Hans Ronne
2004-07-04 21:57 ` mskala
2004-07-05 3:30 ` Hans Ronne
2004-07-09 1:17 ` Henry J. Cobb
[not found] ` <40EDFCDE.9000902@phy.cmich.edu>
2004-07-09 3:37 ` Henry J. Cobb
[not found] ` <40EEAD66.50109@phy.cmich.edu>
2004-07-09 16:02 ` Henry J. Cobb
2004-07-09 16:10 ` Hans Ronne
2004-07-10 4:38 ` Henry J. Cobb
2004-07-12 1:25 ` Carrier groups Henry J. Cobb
2004-07-12 3:27 ` Hans Ronne
2004-07-12 7:00 ` Henry J. Cobb
2004-07-09 16:47 ` Just say no to bungee paratroopers Jim Kingdon
2004-07-09 16:54 ` Elijah Meeks
2004-07-09 17:00 ` Wrecking Issues Elijah Meeks
2004-07-09 17:16 ` Eric McDonald
2004-07-10 21:40 ` Eric McDonald [this message]
2004-07-09 17:45 ` AI Help Elijah Meeks
2004-07-09 18:15 ` Hans Ronne
2004-07-09 18:26 ` Eric McDonald
2004-07-09 19:03 ` Elijah Meeks
2004-07-09 19:45 ` Side Selection Bugs Elijah Meeks
2004-07-09 19:46 ` Hans Ronne
2004-07-11 1:47 ` AWLS: Korea 2006 Eric McDonald
2004-07-11 4:16 ` Elijah Meeks
2004-07-13 2:40 ` More Feedback on " Eric McDonald
2004-07-13 3:48 ` Elijah Meeks
2004-07-13 4:42 ` Eric McDonald
2004-07-13 17:20 ` Elijah Meeks
2004-07-13 17:28 ` Combat result tracking? Elijah Meeks
2004-07-13 17:46 ` Eric McDonald
2004-07-13 18:10 ` Hans Ronne
2004-07-13 18:57 ` Eric McDonald
2004-07-13 19:10 ` Elijah Meeks
2004-07-13 20:23 ` Eric McDonald
2004-07-13 23:08 ` AI Motivation for non-combat units Elijah Meeks
2004-07-14 0:33 ` Hans Ronne
2004-07-13 23:01 ` Combat result tracking? Hans Ronne
2004-07-14 1:04 ` Skeezics Boondoggle
2004-07-14 1:20 ` Eric McDonald
2004-07-14 15:27 ` Counterfire Elijah Meeks
2004-07-15 16:04 ` Counterfire Eric McDonald
2004-07-11 9:44 ` AI Help Jim Kingdon
2004-07-11 10:08 ` Hans Ronne
2004-07-12 18:07 ` Jim Kingdon
2004-07-09 18:09 ` Just say no to bungee paratroopers Hans Ronne
2004-07-11 6:01 ` Jim Kingdon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=40EFF87F.3050203@phy.cmich.edu \
--to=mcdonald@phy.cmich.edu \
--cc=elijahmeeks@yahoo.com \
--cc=xconq7@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).