From: Eric McDonald <mcdonald@phy.cmich.edu>
To: Elijah Meeks <elijahmeeks@yahoo.com>,
xconq7 <xconq7@sources.redhat.com>
Subject: Re: CXP???
Date: Fri, 27 Aug 2004 17:09:00 -0000 [thread overview]
Message-ID: <412F5B74.2040602@phy.cmich.edu> (raw)
In-Reply-To: <20040827050942.5961.qmail@web13122.mail.yahoo.com>
Elijah Meeks wrote:
> 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.
It would seem that someone was a bit sloppy with the code, and
"recycled" the 'chance' variable for determining retreat chance, after
using it for hit chance. So, if the defender's retreat chance is 0% (the
default), then no combat experience is gained. This is a bug by any
other name. I will fix it in my sources. Until you have a new Xconq
release to play with, I would recommend that you set the
'retreat-chance' to 1% for all units (unless you wish them have a higher
retreat chance for other reasons); this weird hack should allow for
combat experience to be gained.
> 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.
This is what I was getting at. However, I plan on leaving things the way
they are for the time being.
Eric
next parent reply other threads:[~2004-08-27 16:04 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040827050942.5961.qmail@web13122.mail.yahoo.com>
2004-08-27 17:09 ` Eric McDonald [this message]
2004-08-28 2:51 ` CXP??? Elijah Meeks
2004-08-28 3:47 ` Multiple Image Use Elijah Meeks
2004-08-28 4:02 ` Eric McDonald
2004-08-28 4:33 ` Elijah Meeks
2004-09-01 7:30 ` Standard Game Graphics Elijah Meeks
2004-09-01 16:18 ` Jim Kingdon
2004-09-01 18:30 ` Eric McDonald
2004-09-02 1:43 ` Elijah Meeks
2004-09-02 4:24 ` Eric McDonald
2004-09-03 2:30 ` Jim Kingdon
2004-09-03 3:01 ` Elijah Meeks
2004-09-03 3:17 ` Eric McDonald
2004-09-03 5:10 ` Elijah Meeks
2004-09-03 5:11 ` Jim Kingdon
2004-09-03 6:10 ` Jim Kingdon
2004-09-03 17:18 ` Changing the Standard Game Elijah Meeks
2004-09-04 2:06 ` Eric McDonald
2004-09-04 17:46 ` Lincoln Peters
2004-09-05 1:48 ` Eric McDonald
2004-09-05 6:02 ` Feature Request: Advance Prohibits Advance Elijah Meeks
2004-09-05 16:25 ` Eric McDonald
2004-09-05 16:41 ` mskala
2004-09-05 16:54 ` Eric McDonald
2004-09-05 17:11 ` mskala
2004-09-05 17:01 ` Elijah Meeks
2004-09-05 16:48 ` Elijah Meeks
2004-09-05 19:43 ` Eric McDonald
2004-09-05 16:50 ` mskala
2004-09-05 16:55 ` Eric McDonald
2004-09-05 16:55 ` Lincoln Peters
2004-09-05 17:01 ` Elijah Meeks
2004-09-05 19:52 ` Jim Kingdon
2004-09-05 20:16 ` Eric McDonald
2004-09-05 19:58 ` Lincoln Peters
2004-09-05 20:15 ` Elijah Meeks
2004-09-05 15:52 ` Changing the Standard Game Lincoln Peters
2004-09-05 16:36 ` Eric McDonald
2004-09-05 20:09 ` Jim Kingdon
2004-09-05 20:14 ` Jim Kingdon
2004-09-05 20:40 ` Elijah Meeks
2004-09-05 22:09 ` Eric McDonald
2004-09-03 23:11 ` Standard Game Graphics Eric McDonald
2004-08-26 19:12 Three thoughts Eric McDonald
2004-08-26 22:08 ` CXP??? Elijah Meeks
2004-08-27 1:50 ` CXP??? Lincoln Peters
2004-08-27 5:10 ` CXP??? Eric McDonald
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=412F5B74.2040602@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).