public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: Lincoln Peters <sampln@sbcglobal.net>
To: Elijah Meeks <elijahmeeks@yahoo.com>
Cc: Xconq list <xconq7@sources.redhat.com>
Subject: Re: CXP???
Date: Fri, 27 Aug 2004 01:50:00 -0000	[thread overview]
Message-ID: <1093558240.8185.8596.camel@localhost> (raw)
In-Reply-To: <20040826191225.10275.qmail@web13126.mail.yahoo.com>

On Thu, 2004-08-26 at 12:12, Elijah Meeks wrote:
> Okay, so you don't get cxp from ranged attacks, unless
> the ranged attack is performed against a unit in the
> hex adjacent?  And you only get cxp if the attack
> misses??  I finally took a good look at cxp, after
> assuming that I wasn't paying attention before, but
> now that I have, it looks screwy.  Does anyone have
> any firm rules on how cxp works and whether or not
> it's supposed to work like this?  It seems haphazard.

The behavior you describe certainly sounds wrong to me.  Since so few
games use CXP, I'm not surprised that there are undicovered bugs in the
code.

---
Lincoln Peters
<sampln@sbcglobal.net>

Tell me what to think!!!

  reply	other threads:[~2004-08-26 22:08 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-20 16:22 Three thoughts mskala
2004-08-20 18:34 ` Eric McDonald
2004-08-20 21:17   ` Andreas Bringedal
2004-08-20 21:28     ` Eric McDonald
2004-08-20 23:57       ` Andreas Bringedal
2004-08-21  1:21         ` Eric McDonald
2004-08-21  4:35           ` Jim Kingdon
2004-08-21 20:38           ` Jim Kingdon
2004-08-20 22:03     ` Elijah Meeks
2004-08-20 23:27       ` Eric McDonald
2004-08-21  1:17         ` mskala
2004-08-21  2:31           ` Eric McDonald
2004-08-21  4:33             ` mskala
2004-08-22  3:09 ` Hans Ronne
2004-08-22  6:38   ` Item Units Elijah Meeks
2004-08-22  9:37     ` Eric McDonald
2004-08-24  1:43       ` Lincoln Peters
2004-08-24  2:38         ` Eric McDonald
2004-08-24  2:51           ` Lincoln Peters
2004-08-24  3:32             ` Eric McDonald
2004-08-22 14:00   ` Three thoughts mskala
2004-08-22 18:56     ` Hans Ronne
2004-08-22 19:16       ` Lincoln Peters
2004-08-23  4:31         ` Jim Kingdon
2004-08-23 13:04           ` Elijah Meeks
2004-08-24 18:07             ` Eric McDonald
2004-08-24 20:59               ` Elijah Meeks
2004-08-25  0:54                 ` Unit-Image Bug Elijah Meeks
2004-08-25  4:58                   ` Eric McDonald
2004-08-23 16:48         ` Three thoughts Eric McDonald
2004-08-24  0:55           ` Lincoln Peters
2004-08-24  2:09             ` Eric McDonald
2004-08-24  3:02               ` Lincoln Peters
2004-08-24 18:12                 ` Eric McDonald
2004-08-25  5:34                   ` Jim Kingdon
2004-08-25 17:16                     ` Lincoln Peters
2004-08-25 22:09                       ` Jim Kingdon
2004-08-26  2:15                         ` Eric McDonald
2004-08-26  6:17                           ` Jim Kingdon
2004-08-26 19:12                             ` Eric McDonald
2004-08-26 22:08                               ` CXP??? Elijah Meeks
2004-08-27  1:50                                 ` Lincoln Peters [this message]
2004-08-27  5:10                                 ` CXP??? Eric McDonald
     [not found] <20040827050942.5961.qmail@web13122.mail.yahoo.com>
2004-08-27 17:09 ` CXP??? Eric McDonald
2004-08-28  2:51   ` CXP??? Elijah Meeks

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=1093558240.8185.8596.camel@localhost \
    --to=sampln@sbcglobal.net \
    --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).