From: Hans Ronne <hronne@comhem.se>
To: Lincoln Peters <sampln@sbcglobal.net>
Cc: xconq7@sources.redhat.com
Subject: Re: Bug in acp-independent action code
Date: Sun, 13 Jun 2004 21:45:00 -0000 [thread overview]
Message-ID: <l03130301bcf279b5f267@[212.181.162.155]> (raw)
In-Reply-To: <1087022787.12177.9891.camel@odysseus>
>Since the module is more than twice the size of the original knights.g,
>I'll send it directly to you in a separate e-mail.
Thanks. I can now reproduce the bug. It seems that acp-independent units,
at least in your game, have a 20% chance of resetting the run length to 1
for each unit that is completed. Not an easy bug to catch.
Hans
next prev parent reply other threads:[~2004-06-13 21:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-11 6:17 Lincoln Peters
2004-06-11 6:40 ` Hans Ronne
2004-06-12 6:45 ` Lincoln Peters
2004-06-12 9:01 ` Hans Ronne
2004-06-13 21:45 ` Hans Ronne [this message]
2004-06-14 23:34 ` Hans Ronne
2004-06-15 4:55 ` Lincoln Peters
2004-06-15 7:18 ` Hans Ronne
2004-06-15 20:51 ` Lincoln Peters
2004-06-16 4:08 ` New Wreck-Type Options Elijah Meeks
2004-06-16 13:49 ` Eric McDonald
2004-06-16 21:00 ` Bug in acp-independent action code Hans Ronne
2004-06-15 5:19 ` 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='l03130301bcf279b5f267@[212.181.162.155]' \
--to=hronne@comhem.se \
--cc=sampln@sbcglobal.net \
--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).