From: Eric McDonald <mcdonald@phy.cmich.edu>
To: Elijah Meeks <elijahmeeks@yahoo.com>
Cc: xconq7 <xconq7@sources.redhat.com>
Subject: Re: New Windows Installer and Source Tarballs
Date: Mon, 11 Oct 2004 01:45:00 -0000 [thread overview]
Message-ID: <4169BED8.6090903@phy.cmich.edu> (raw)
In-Reply-To: <20041010225159.62809.qmail@web13126.mail.yahoo.com>
Elijah Meeks wrote:
>> There are a number of bugfixes in the new
>>prelease. Also, there are
>
> It doesn't seem like looks-like and see-mistake-chance
> do what they're supposed to? Is this the case or are
> my tables still screwy?
Your 'see-mistake-chance' looks fine. Technically, you don't need to
crank the weight up so high in 'looks-like', but it shouldn't matter.
If you want to see the bugfix at work, start up the 'battle-bug.xcq'
game that you sent me. You will (should) see the markers instead of the
ships for the two furthest out Fed vessels.
Eric
next prev parent reply other threads:[~2004-10-10 22:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-10 22:52 Eric McDonald
2004-10-10 22:56 ` Elijah Meeks
2004-10-10 22:59 ` Lincoln Peters
2004-10-11 1:45 ` Eric McDonald [this message]
2004-10-11 2:06 ` Elijah Meeks
2004-10-11 2:49 ` Eric McDonald
2004-10-11 6:26 ` Lincoln Peters
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=4169BED8.6090903@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).