Sophie: xconq-7.5.0-1.20050612.5mdv2009.1 i586

xconq-7.5.0-1.20050612.5mdv2009.1.i586.rpm

<HTML>
<HEAD>
<!-- This HTML file has been created by texi2html 1.39
     from ./xcdesign.texi on 12 June 2005 -->

<TITLE>Designing Games with Xconq - Unit Movement</TITLE>
</HEAD>
<BODY>
Go to the <A HREF="xcdesign_1.html">first</A>, <A HREF="xcdesign_10.html">previous</A>, <A HREF="xcdesign_12.html">next</A>, <A HREF="xcdesign_61.html">last</A> section, <A HREF="xcdesign_toc.html">table of contents</A>.
<HR>


<H2><A NAME="SEC40" HREF="xcdesign_toc.html#SEC40">Unit Movement</A></H2>

<P>
Movement is the most important action type.  There are actually two distinct
types of actions; one to enter a cell, and one to enter a unit.

</P>
<P>
Each unit has a speed which is determined at the beginning of the turn
and determines how many cells it can enter during the turn.
However, terrain, borders, and other obstacles can consume extra
movement points.

</P>

<UL>
<LI><A HREF="xcdesign_11.html#SEC41">Unit Speed</A>
<LI><A HREF="xcdesign_11.html#SEC42">Movement Costs</A>
<LI><A HREF="xcdesign_11.html#SEC43">Entering Transports</A>
<LI><A HREF="xcdesign_11.html#SEC44">Border Slides</A>
<LI><A HREF="xcdesign_11.html#SEC45">Leaving the Area</A>
<LI><A HREF="xcdesign_11.html#SEC46">Free Moves</A>
<LI><A HREF="xcdesign_11.html#SEC47">Zone of Control</A>
</UL>



<H3><A NAME="SEC41" HREF="xcdesign_toc.html#SEC41">Unit Speed</A></H3>

<P>
Units have a base speed <CODE>speed</CODE> which is the ratio of mp to acp.
You can set damaged units to move more slowly.
You can also allow occupants to add to the speed, up to the
<CODE>speed-max</CODE> limit.

</P>
<P>
You can define wind-affected units by defining speed in each direction
(max-speed only, do others proportionally).  Would need 4 distinct mp costs
plus a formula to relate to wind strength.  Wind speed defined as "how
far a particle of air moves in a turn".  Unit examples include balloons,
dirigibles, sailing ships, floating cities.

</P>


<H3><A NAME="SEC42" HREF="xcdesign_toc.html#SEC42">Movement Costs</A></H3>

<P>
Typically the cell entry cost will be the most useful to adjust,
although the departure cost can be useful in representing units
mired in jungle mud
and taking a long time to escape onto clear terrain.

</P>
<P>
Be aware that complicated entry/exit costs are confusing to players,
and AIs may not take them into account very well either.
Using <CODE>free-mp</CODE> helps players use up all their acp.

</P>


<H3><A NAME="SEC43" HREF="xcdesign_toc.html#SEC43">Entering Transports</A></H3>

<P>
Different kinds of transports have different ways for units
to get on and off.  For instance,
ships can dock, or use their boats to enable land units to get on and off.
The tables <CODE>ferry-on-entry</CODE> and <CODE>ferry-on-departure</CODE>
specify how much terrain units will have to cross on their own.

</P>
<P>
[example]

</P>
<P>
Observe that enter/leave costs can be used to make one-way trips.
For instance, paratroops jumping out of a plane should be able
to leave cheaply, but have an entry cost so high that they can
only reboard in a later turn.

</P>


<H3><A NAME="SEC44" HREF="xcdesign_toc.html#SEC44">Border Slides</A></H3>

<P>
One of the problems with <I>Xconq</I> borders and connections is that
neither works exactly like a sea strait.  Consider the Straits of
Gibraltar.  They are so narrow that one can see the other side,
but nevertheless impose a formidable barrier to landlubbers.
At the same time, ships can pass through readily, if
not secretly.  If cells in the world are 60 miles across, then
making an all-sea cell is a gross exaggeration.
However, adding a water border only prevents both land and sea movement!
To get around all this, <I>Xconq</I> allows a special kind of
move called a "border slide".
Basically, if both the destination cell and the border whose endpoints
touch the start and end cells are allowable terrain for a unit,
then the unit can move to the destination cell in one move.
However, it incurs a special cost in addition to the normal entry
and leave costs for the terrain in the two cells (but <I>not</I> the border
crossing cost, since the border is not being crossed, exactly).
This cost is in the table <CODE>mp-to-traverse</CODE>.
Border sliding should usually be somewhat expensive, both because
of the distance (the unit ends up two cells away after only one move),
and because of the real-life difficulties of passing through a narrow
strait.  Note that border sliding does not escape the units on either
side of the border, since the unit doing the sliding will still be
adjacent to the cells on each side of the border it slid through.

</P>


<H3><A NAME="SEC45" HREF="xcdesign_toc.html#SEC45">Leaving the Area</A></H3>

<P>
This feature can be useful in allowing a non-disbandable unit type
to escape capture or otherwise retire from action.

</P>


<H3><A NAME="SEC46" HREF="xcdesign_toc.html#SEC46">Free Moves</A></H3>

<P>
This is most useful in emulating some board games,
or to prevent clever players from exploiting a mess of move costs.
The default of <CODE>-1</CODE> is the most playable,
since player will always be able to use all of their mp.
Otherwise, there may be situations in which a unit has
a few acp left, but not enough to go anywhere,
and so they end up being wasted.
The free move does not actually get subtracted from the unit's acp,
it just doesn't let lack of acp forbid the move.

</P>


<H3><A NAME="SEC47" HREF="xcdesign_toc.html#SEC47">Zone of Control</A></H3>

<P>
Sometimes a unit can by its presence alone affect the movement of unfriendly
units in the vicinity, perhaps by requiring them to hide or to move
carefully in order to pass by, or even to prevent entry altogether.
This is called the "zone of control" or ZOC.

</P>
<P>
Exerting a ZOC requires no action, nor any particular capability on
on the part of the unit exerting the ZOC.  For instance, a toothless
fort could still cause raiders to sneak by carefully (at least if they
didn't know that it was toothless).

</P>
<HR>
Go to the <A HREF="xcdesign_1.html">first</A>, <A HREF="xcdesign_10.html">previous</A>, <A HREF="xcdesign_12.html">next</A>, <A HREF="xcdesign_61.html">last</A> section, <A HREF="xcdesign_toc.html">table of contents</A>.
</BODY>
</HTML>