From: Eric McDonald <mcdonald@phy.cmich.edu>
To: Elijah Meeks <elijahmeeks@yahoo.com>
Cc: Jim Kingdon <kingdon@panix.com>, <xconq7@sources.redhat.com>
Subject: Re: Standard Game Graphics
Date: Fri, 03 Sep 2004 23:11:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0409031307130.21256-100000@leon.phy.cmich.edu> (raw)
In-Reply-To: <20040903031755.87747.qmail@web13121.mail.yahoo.com>
On Thu, 2 Sep 2004, Elijah Meeks wrote:
> agree that it should be a group decision. The one
> problem, which I believe Jim pointed out and proved
> true, is that it doesn't look so good at the 16
> unit/hex resolution.
Jim brought up a valid point, and I suggested a custom image
family (i.e., one that specifies alternate graphics at lower
resolutions) as a way to deal with it.
> 1. Make specific imf 4 4 definitions that reference
> the old silhouettes, because they're more recognizable
> at that resolution.
This might work.
> 2. Set unit limits per hex at four, which is the max
> amount of Trident units in a hex that are still
> recognizable and look decent.
This could severely alter gameplay. I would lean more towards
option 1 than option 2.
> Eric's Occupant Dialog Box Fix is out... Right,
> Eric?*
We'll see. :-)
I am still getting accustomed to working on the SDL interface, and
building up various tools to help me hack on it more easily. I
haven't yet shifted into high productivity mode with it.
Also, I think I am going to try the unit magnification approach
first, before resorting to a dialog box.
> still think we need a forum. And a better webpage
Can't argue with that.
> And salaries for game designers. And
If you can get me a salary to work on Xconq or some derivative
thereof, that would be great. :-)
Eric
prev parent reply other threads:[~2004-09-03 17:18 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040827050942.5961.qmail@web13122.mail.yahoo.com>
2004-08-27 17:09 ` CXP??? Eric McDonald
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 ` 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.0409031307130.21256-100000@leon.phy.cmich.edu \
--to=mcdonald@phy.cmich.edu \
--cc=elijahmeeks@yahoo.com \
--cc=kingdon@panix.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).