From: Eric McDonald <mcdonald@phy.cmich.edu>
To: Robert Goulding <Goulding.2@nd.edu>
Cc: xconq7@sources.redhat.com, <xconq-players@lists.sourceforge.net>
Subject: Re: Net Game Showstopper (was Re: Net game on Saturday?)
Date: Thu, 20 Jan 2005 16:28:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0501201111420.17228-100000@leon.phy.cmich.edu> (raw)
In-Reply-To: <F1BCB73F-6AF2-11D9-B62F-000A9589320A@nd.edu>
On Thu, 20 Jan 2005, Robert Goulding wrote:
> I'd like to join in, but I had a couple of problems with the latest
> build on Windows, all seeming to do with multiple units in a single
> cell. I was playing time.g, and found that when I loaded a third
> phalanx onto a trireme, the third phalanx occupied the whole of the
> cell, effacing the trireme.
Right. My fault for not communicating the unit display changes
better.
The idea is that if you are a fairly close map magnification, such
as the default one (cells are 44x44 and units are generally
32x32), then about the smallest an unit image can be shrunken is
to 16x16 before it becomes hard to identify. In a transport's
32x32 grouping box, 2 16x16 images may fit in the lower portion.
If three units are placed in the transport, then the occupant
sizes must be rescaled to 8x8, making them hard to see. So, as a
counter to this, I made it so that one such occupant is the
current unit, it fills up the transport's grouping box so that it
stands out more. Similarly, occs did not show up at all in the
isometric view. To counter this, I likewise made it so that the
current unit, if an occ, would fill the same region that its
transport would. I had thought this was an aid to game play to
make it so.
But, like I said, my fault for not more directly communicating
such change and its rationale.
Another change that I made was that if a transport is in a cell
with other units, then the transport will still have a grouping
box drawn around it, even if its occs cannot be displayed at the
shrunken view. This is done so that there is still some indication
that it has occs. Perhaps you noticed this as well.
> When I woke up all the contained phalanxes in a trireme with a W
> command, one of the phalanxes on board never got the focus; I had to
> switch to survey mode to manually give it orders.
This sounds odd. If you can attach a saved game demonstrating the
bug, it would be quite helpful.
> Finally, I had a multitude of phalanxes on the shore, 4 to a cell, all
> asleep. When I switched to survey mode and selected one in order to
> wake it up, the program crashed.
That is not good. If you have a saved game that allows easy
reproduction of the bug, it would helpful.
Thanks,
Eric
prev parent reply other threads:[~2005-01-20 16:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-27 4:37 Net game on Saturday? tsbvc
2004-08-28 3:55 ` Jim Kingdon
2004-08-28 4:16 ` Eric McDonald
2004-08-28 4:32 ` Jim Kingdon
2004-08-28 4:53 ` Eric McDonald
2004-08-28 16:24 ` Jim Kingdon
2004-08-28 18:03 ` Eric McDonald
2004-08-28 19:31 ` Net Game Showstopper (was Re: Net game on Saturday?) Eric McDonald
2005-01-17 23:36 ` Eric McDonald
2005-01-18 0:00 ` Elijah Meeks
2005-01-20 1:41 ` Eric McDonald
2005-01-20 14:53 ` Robert Goulding
2005-01-20 16:28 ` Eric McDonald [this message]
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=Pine.LNX.4.44.0501201111420.17228-100000@leon.phy.cmich.edu \
--to=mcdonald@phy.cmich.edu \
--cc=Goulding.2@nd.edu \
--cc=xconq-players@lists.sourceforge.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).