public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: Elijah Meeks <elijahmeeks@yahoo.com>
To: xconq7@sources.redhat.com
Subject: Fwd: Re: CXP???
Date: Fri, 27 Aug 2004 16:04:00 -0000	[thread overview]
Message-ID: <20040827051002.57684.qmail@web13123.mail.yahoo.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 180 bytes --]


Note: forwarded message attached.



		
__________________________________
Do you Yahoo!?
Yahoo! Mail - 50x more storage than other providers!
http://promotions.yahoo.com/new_mail

[-- Attachment #2: Type: message/rfc822, Size: 1390 bytes --]

From: Elijah Meeks <elijahmeeks@yahoo.com>
To: Eric McDonald <mcdonald@phy.cmich.edu>
Subject: Re: CXP???
Date: Thu, 26 Aug 2004 22:09:42 -0700 (PDT)

I have yet to see a unit gain experience from a
fire-action, except in cases where the unit it's
firing on is adjacent.

> P.S. It should be noted that the defender can gain
> cXP just being 
> attacked or fired upon, and it gains the same amount
> as if it was the 
> attacker. Defenders also gain experience from being
> captured and 
> resisting capture (as seen in the above code). Both
> of these cases seem 
> a bit odd to me.
> 

I think, barring seperate tables for cxp-per-attack,
cxp-per-hit, cxp-per-defend, cxp-per-capture and
cxp-per destruction, I say keep it all as cxp for each
attack and keep it two-way.  You should get experience
for surviving certain attacks but, of course, it would
seem more realistic if you were able to tailor them. 
Surviving an assault may not be as much experience as
making it, and in some cases it may be more.

> 



		
__________________________________
Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish.
http://promotions.yahoo.com/new_mail 

                 reply	other threads:[~2004-08-27  5:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20040827051002.57684.qmail@web13123.mail.yahoo.com \
    --to=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).