From: Stan Shebs <shebs@apple.com>
To: Eric McDonald <mcdonald@phy.cmich.edu>
Cc: Hans Ronne <hronne@comhem.se>, xconq7@sources.redhat.com
Subject: Re: Clearing the Air (long)
Date: Fri, 20 Aug 2004 15:26:00 -0000 [thread overview]
Message-ID: <4125702A.1030009@apple.com> (raw)
In-Reply-To: <412556EF.80401@phy.cmich.edu>
It's almost never a good idea to guess that there must be secret evil
intent, and react as if that were really the case. There are about a
half-dozen interconnected ideas being kicked around, and I think
everybody is operating with different assumptions, some of which have
probably not been written down yet.
To put things in perspective, this is a depth of modelling that the
professional game designers don't even want to get into; if you
"deconstruct" an A-list game, you'll see that they carefully restrict
the rules, for instance to avoid stacks of units entirely by making
each unit have a physical size in a fine-grained coordinate system.
And of course the rules themselves have minimal variability. One of
Xconq's attributes is a high degree of flexibility, but as we've
seen many times, it can be difficult to take advantage of it; try
something really exotic in a game module, and interfaces are
unintelligible, the AI doesn't know what to do, etc.
So the goal is to find a set of parameters that model the kinds
of games you want to be able to play, but that means that you
need to start with an agreement about what those games are.
Just a "might want to" or "would be nice" is not enough; Xconq
is littered with stubbed-out code that started with that thought
and was never finished. Do we want to enhance the standard
game, add new tactical possibilities to the panzer game, design
new games that weren't possible before, what? After all, this
whole discussion started with Hans just trying to fix bugs...
Stan
next prev parent reply other threads:[~2004-08-20 3:29 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-16 21:53 Major bug and what to do about it (long) Hans Ronne
2004-08-16 22:14 ` Eric McDonald
2004-08-16 22:43 ` Hans Ronne
2004-08-17 0:33 ` Hans Ronne
2004-08-17 1:13 ` Eric McDonald
2004-08-17 1:39 ` Hans Ronne
2004-08-17 2:21 ` Eric McDonald
2004-08-17 4:28 ` Jim Kingdon
2004-08-17 5:17 ` Hans Ronne
2004-08-17 18:00 ` Eric McDonald
2004-08-18 5:26 ` Jim Kingdon
2004-08-18 11:11 ` Hans Ronne
2004-08-17 16:14 ` Eric McDonald
2004-08-17 0:35 ` Eric McDonald
2004-08-17 1:16 ` Hans Ronne
2004-08-17 1:46 ` Eric McDonald
2004-08-17 3:03 ` Hans Ronne
2004-08-17 3:56 ` Eric McDonald
2004-08-17 1:30 ` Eric McDonald
2004-08-17 2:52 ` Hans Ronne
2004-08-17 2:53 ` Eric McDonald
2004-08-17 4:42 ` Jim Kingdon
2004-08-17 16:37 ` Eric McDonald
2004-08-17 4:48 ` Hans Ronne
2004-08-17 16:42 ` Eric McDonald
2004-08-18 10:56 ` Jim Kingdon
2004-08-17 11:06 ` Stan Shebs
2004-08-17 15:29 ` Hans Ronne
2004-08-17 16:01 ` Hans Ronne
2004-08-17 18:57 ` Eric McDonald
2004-08-17 20:38 ` Hans Ronne
2004-08-17 21:55 ` Eric McDonald
2004-08-17 23:42 ` Hans Ronne
2004-08-18 0:49 ` Eric McDonald
2004-08-18 4:59 ` Hans Ronne
2004-08-18 15:28 ` Eric McDonald
2004-08-19 6:37 ` Elijah Meeks
2004-08-19 12:46 ` Hans Ronne
2004-08-19 16:46 ` Eric McDonald
2004-08-19 13:09 ` Hans Ronne
2004-08-19 16:05 ` Eric McDonald
2004-08-19 20:09 ` Hans Ronne
2004-08-19 23:37 ` Eric McDonald
2004-08-20 1:42 ` Hans Ronne
2004-08-20 3:29 ` Clearing the Air (long) Eric McDonald
2004-08-20 15:26 ` Stan Shebs [this message]
2004-08-18 5:30 ` Major bug and what to do about it (long) Jim Kingdon
2004-08-18 12:52 ` Hans Ronne
2004-08-17 18:23 ` Eric McDonald
2004-08-17 18:47 ` Hans Ronne
2004-08-17 18:59 ` Eric McDonald
2004-08-17 19:39 ` Hans Ronne
2004-08-17 21:14 ` 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=4125702A.1030009@apple.com \
--to=shebs@apple.com \
--cc=hronne@comhem.se \
--cc=mcdonald@phy.cmich.edu \
--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).