public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: Eric McDonald <emcdonal@cps.cmich.edu>
To: Jim Kingdon <kingdon@panix.com>
Cc: xconq7@sources.redhat.com
Subject: Re: Important changes in the Xconq API
Date: Sun, 22 Jun 2003 20:22:00 -0000	[thread overview]
Message-ID: <Pine.GSO.4.53.0306220017570.3650@cps201.cps.cmich.edu> (raw)
In-Reply-To: <200306220257.h5M2vjU07318@panix5.panix.com>


Here is another doc patch that reflects Hans' recent changes, plus removes a
redundancy from the game design manual.

The patch does the following to doc/refman.texi:
* Removes a duplicate entry of the UnitProperty, size, in the section on
advanced unit types.
* Makes some new notes regarding the unit-size-in-terrain table.
* Remarks that the capacity-negation table has been pulled from GDL.

Patch below:

--- orig-refman.texi	Sat Jun 21 23:30:43 2003
+++ refman.texi	Sun Jun 22 00:10:43 2003
@@ -2936,10 +2936,6 @@
 This property is true if the type is an advanced type.
 @end deffn

-@deffn UnitProperty @code{size} n
-This property is the size of the advanced unit.
-@end deffn
-
 @deffn TableUA @code{size-limit-without-advance} u a -> n
 This table indicates the maximum size of a unit of type @var{u} if the
 advance @var{a} has not been achieved.  Defaults to a large number.
@@ -3410,8 +3406,17 @@

 @deffn TableUT @code{unit-size-in-terrain} u t -> n
 This table is the ``size'' of a (full-sized) unit @var{u} when it is
-in/on the terrain @var{t}.  Defaults to @code{1}.  (Note that this is
-not the same as the size property of an advanced unit.)
+in/on the terrain @var{t}.  Defaults to @code{1}.@*
+NOTE: This is not the same as the size property of an advanced unit.@*
+NOTE: As of Xconq 7.5, this property is ignored for connection terrain
+types. Connectors (roads, for example) now refer to @var{u}'s size in the
+terrain that contains the connector rather than @var{u}'s size in
+connector @var{t}.@*
+NOTE: If you wish to prevent a unit's entry into @var{t}, then use the
+@code{mp-to-enter-terrain} table, and not this one. The implication of
+using @code{unit-size-in-terrain} to prevent entry is that the unit will
+not be able to enter any connectors in @var{t} if @var{n} is set too
+large.
 @end deffn

 @deffn TableUT @code{terrain-capacity-x} u t -> n
@@ -3425,6 +3430,7 @@
 unit in a cell to override any capacity due to connections in that cell.

 @deffn TableUT @code{capacity-negation} u t -> t/f
+@i{This table has been removed and is no longer available.}
 @end deffn

 @deffn UnitTypeProperty @code{stack-order} n

  reply	other threads:[~2003-06-22  4:24 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
2003-06-22 20:22   ` Eric McDonald [this message]
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=Pine.GSO.4.53.0306220017570.3650@cps201.cps.cmich.edu \
    --to=emcdonal@cps.cmich.edu \
    --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).