public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: Elijah Meeks <elijahmeeks@yahoo.com>
To: Hans Ronne <hronne@comhem.se>
Cc: xconq7@sources.redhat.com
Subject: Re: Withdraw Bug
Date: Fri, 11 Jun 2004 23:31:00 -0000	[thread overview]
Message-ID: <20040611233137.41416.qmail@web13124.mail.yahoo.com> (raw)
In-Reply-To: <l03130302bcef05d1a07c@[212.181.162.155]>

I'm having no luck producing this error in a smaller
game.  It looks like, within Korea 2006, it happens
when a unit is wrecked, and that wreck-type checks and
receives a true from the withdraw-chance table AND the
cell it is supposed to withdraw into is in an enemy
ZOC while it is in a ZOC.  The unit ends up with 1/0
ACP or 5/0 ACP or 7/0 ACP (Why it varies doesn't seem
to be apparent).

I've pulled out the auto-withdraw from Korea 2006, and
it wasn't that big a feature, so this isn't a
high-priority bug.


--- Hans Ronne <hronne@comhem.se> wrote:
> >Units that are forced to retreat with the
> >withdraw-chance-per-attack table can cause a game
> to
> >freeze.  This was the problem with Korea 2006.  I
> >suspect it's a combination of this table with ZOC
> >and/or wreck-typing, and will do some more testing
> to
> >find out.
> 
> Excellent. If you can pin down exactly what
> combination of factors that
> triggers the bug it will be much easier to fix.
> 
> Hans
> 
> 



	
		
__________________________________
Do you Yahoo!?
Friends.  Fun.  Try the all-new Yahoo! Messenger.
http://messenger.yahoo.com/ 

  reply	other threads:[~2004-06-11 23:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-08  1:11 New game by Elijah Meeks Hans Ronne
2004-06-08 23:28 ` Elijah Meeks
2004-06-09 20:04   ` Withdraw Bug Elijah Meeks
2004-06-11  6:50     ` Hans Ronne
2004-06-11 23:31       ` Elijah Meeks [this message]
2004-06-11 23:37         ` Appropriating Abandonware Graphics 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=20040611233137.41416.qmail@web13124.mail.yahoo.com \
    --to=elijahmeeks@yahoo.com \
    --cc=hronne@comhem.se \
    --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).