public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: Jim Kingdon <kingdon@panix.com>
To: hronne@telia.com
Cc: xconq7@sources.redhat.com
Subject: Re: Important changes in the Xconq API
Date: Sun, 22 Jun 2003 04:24:00 -0000	[thread overview]
Message-ID: <200306220257.h5M2vjU07318@panix5.panix.com> (raw)
In-Reply-To: <l03130302bb1a9c45ec8b@[212.181.162.155]> (message from Hans Ronne on Sun, 22 Jun 2003 03:08:00 +0200)

> There used to be "extra" space for units available in cells that had
> connections, since the connections also could store
> units. Unfortunately, this caused serious problems

Getting rid of this is probably right.

A long time ago I remember some kind of bug in the standard game
whereby I had a ship and would then click on a river (where the river
was between two land cells), and the ship would just disappear rather
than sailing down the river (I was new to xconq, so I'm sure there was
plenty I didn't understand - not least of which that ships are a poor
use of construction points in the standard game, but I digress.  So I
don't really know exactly what I did, but I'm pretty sure that the
ship really did disappear).

I don't know if your fix would be related, but the fix does sound
right.  Seems like games should use mp-to-enter-terrain rather than
the extra space you describe.

  reply	other threads:[~2003-06-22  2:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-22  2:59 Hans Ronne
2003-06-22  4:24 ` Jim Kingdon [this message]
2003-06-22 20:22   ` Eric McDonald
2003-06-22 20:35     ` Jim Kingdon
2003-06-22 20:44       ` Hans Ronne
2003-06-24  5:14         ` Jim Kingdon
2003-06-24 17:30           ` Patch: tkmap.c Eric McDonald
2003-06-24  4:23       ` Important changes in the Xconq API Eric McDonald
2003-06-22 21:02 ` Lincoln Peters
2003-06-22 21:05   ` Hans Ronne

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=200306220257.h5M2vjU07318@panix5.panix.com \
    --to=kingdon@panix.com \
    --cc=hronne@telia.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).