public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: "Erik Jessen" <ejessen@adelphia.net>
Cc: <xconq7@sources.redhat.com>
Subject: Xconq testing: Win2K
Date: Mon, 24 Nov 2003 01:25:00 -0000	[thread overview]
Message-ID: <000501c3b222$aecd05d0$6401a8c0@Win2k> (raw)
In-Reply-To: <l03130301bbe6c1c17025@[212.181.162.155]>

I did some testing with a very simple map, where I actually had some
terrain listed on the map, that hadn't been declared.

Effects:
1) warning that the game might not be able to continue.
    I chose 'continue'
2) internal error, followed by hang, when I attempted to place a unit in
the topmost hex row.

Recommendations:
1) somehow ignore the invalid terrain cleanly; new users are bound to
mess things up, and internal errors will throw them for a loop.

Notes/thoughts:
1) since (I think) all games are supposed to be stored in 'lib', have
the 'open file' button default to starting there.

2) I am working on the model of:
   a) a 'standard config' file that declares all terrain types & unit
types
      and their interactions.  This is normally hand-typed.
   b) a map file.  This is normally entered via gui, and saved "binary".
   c) a unit placement file (scenario, if you will).  This is normally
       entered via gui, but might be hand-edited, and saved "binary".
   d) a 'game' is a small file that pulls all of the above together.
      This permits a map of W. Europe to be used for various eras, and
      Set of standard "modern" units to be used in various campaigns.

   This allows the following to be done:
   - create a single config file that describes Ancient Rome.
   - create maps for each battlefield
   - create various unit deployments for each battle

   I would really, really like an easy way to save off the map &
unit-placement as separate files in the GUI; it's been a while, but I
recall that it was really complicated to save off just what one wanted
to each file.

I would also like to be able to strip out a specific terrain-type, in
case I bungled the job & created an extra few early on, and would like
to clean things up.  Maybe the ability of the map-save function to not
list any terrain for which there were no placements would do this
perfectly?

I am hoping that the approach listed in (2) will encourage newcomers to
build new games: the normal game will be pretty small (because it'll
just include in 3 larger files), so the user will only have to edit one
or two
Of the file to create new games from existing ones.

For power users, it would be nice if there was an easy way to do
things like:
- shift a particular region of the map up/left/right/down/mirror.
- enlarge the map on any side(s)
- shrink the map (deleting terrain that fell off the face of the earth)

Erik


  parent reply	other threads:[~2003-11-24  0:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-05 21:47 Xconq output files Hans Ronne
2003-10-06  2:24 ` Peter Garrone
2003-10-06  3:42 ` Jim Kingdon
2003-10-07  3:28   ` Hans Ronne
2003-10-06 22:04 ` Eric McDonald
2003-11-23 20:12 ` Eric McDonald
2003-11-23 21:54   ` Hans Ronne
2003-11-24  0:26     ` Eric McDonald
2003-11-26 21:53       ` Hans Ronne
2003-11-26 22:56         ` Eric McDonald
2003-12-01  1:38           ` Hans Ronne
2003-11-24  1:25     ` Erik Jessen [this message]
2003-11-24  2:16       ` Xconq testing: Win2K Hans Ronne
2003-11-24  2:27         ` Erik Jessen
2003-11-25  1:47           ` 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='000501c3b222$aecd05d0$6401a8c0@Win2k' \
    --to=ejessen@adelphia.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).