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 ./xconq.texi on 12 June 2005 -->

<TITLE>Xconq - Errors and Warnings</TITLE>
</HEAD>
<BODY>
Go to the <A HREF="xconq_1.html">first</A>, <A HREF="xconq_57.html">previous</A>, <A HREF="xconq_59.html">next</A>, <A HREF="xconq_66.html">last</A> section, <A HREF="xconq_toc.html">table of contents</A>.
<HR>


<H2><A NAME="SEC147" HREF="xconq_toc.html#SEC147">Errors and Warnings</A></H2>

<P>
<A NAME="IDX393"></A>
<A NAME="IDX394"></A>
<A NAME="IDX395"></A>
<STRONG>Errors</STRONG> are fatal flaws.  <I>Xconq</I> must shut itself down in order
to prevent a bad situation from getting worse.  You may be able to save
the game, repair it, and restart it, but you must understand a good deal
about the <I>Xconq</I> Game Design Language (GDL) and about how <I>Xconq</I>
works.  If the error happens during game setup, you will not be able
to save anything.

</P>
<P>
<A NAME="IDX396"></A>
<STRONG>Warnings</STRONG> are advice that something is amiss, but that there is no
obvious reason to quit--yet.  Warnings may indicate either mistakes in
a game design or bugs in <I>Xconq</I>.  If you <EM>know</EM> that a warning
does not indicate a serious problem, you can keep playing, but be wary.

</P>
<P>
If the warning happens during game setup, you will not be able to save.
Otherwise you can save, and the game can usually be restored as-is,
although the problem causing the warning may still exist, and you'll
see the warning again when you restore the game.

</P>
<P>
Any error or warning not listed below is almost certainly a bug, most
likely in a game design, but maybe in <I>Xconq</I>, and should be reported.

</P>
<DL COMPACT>

<DT><CODE>Can't find module <VAR>name</VAR> anywhere</CODE>
<DD>
This means that <I>Xconq</I> searched in the library locations it knows
and found no modules named <VAR>name</VAR>.

<DT><CODE>Module <VAR>name</VAR> could not be opened</CODE>
<DD>
This typically means that although the module was found, it could
not be opened; for instance, it might have been read-protected.

<DT><CODE>Too many players</CODE>
<DD>
Some game designs limit the number of players, and you asked for
more than that.  Ask for fewer.

<DT><CODE>Requested advantage is too low / high</CODE>
<DD>
<A NAME="IDX397"></A>
The game design limits the range of advantages that you may request,
and you went outside that range.

<DT><CODE>Only <VAR>n</VAR> of the requested displays opened</CODE>
<DD>
(not the most useful message in the world - only document the
"xyz could not be opened" message?)

<DT><CODE>Need at least one display to run</CODE>
<DD>
<I>Xconq</I> is an interactive game; a game with no displays at all is sort
of pointless, eh?

<DT><CODE>Images were not found</CODE>
<DD>
<A NAME="IDX398"></A>
A game design may not have had graphical images defined for all types of
units and terrain.  <I>Xconq</I> will warn about this, then make up some
(ugly) default images itself.  Actual game play will be unaffected,
although the default images really are ugly and will want to make you
stop playing...

<DT><CODE><VAR>name</VAR> color is way off on display <VAR>yyy</VAR></CODE>
<DD>
It may be that a particular display and its software will not have set
up a color that matches what was requested (this can happen in X11, for
instance).  This has no direct effect on game play, but you may have
difficulty if, say, your display shows several different terrain types
as having the same color.

<DT><CODE>Memory exhausted</CODE>
<DD>
<A NAME="IDX399"></A>
Some <I>Xconq</I> games are exceedingly large and complex, and it is not
unusual that they will need more than that available RAM or swap space.
This will typically occur during game setup, since <I>Xconq</I>
preallocates nearly all of the space it will need.  If you have no way
to get more memory, you must choose a smaller game.  You can make a
given game smaller by choosing the <SAMP>`See All'</SAMP> variant if it is
available (no need to record views for each side) or by having fewer
players and/or fewer AIs.  For instance, instead of playing against 7
AIs, you can play against one AI with an initial advantage of 7.

<DT><CODE>Can't open statistics file <VAR>name</VAR></CODE>
<DD>
(Obvious)

<DT><CODE>Can't open score file <VAR>name</VAR></CODE>
<DD>
(Obvious)

<DT><CODE>Sides have undesirable locations</CODE>
<DD>
<A NAME="IDX400"></A>
Many game designs can specify how close and how far away each randomly
placed side should be from all the others, and the kind of terrain each
will start on.  If the world is too small, or doesn't have the right
kinds of terrain, then <I>Xconq</I> will warn about this.  The game will
still play normally, but it may be grossly unfair, and if the sides
start out hidden from each other, it may be a while until it becomes
obvious how unfair it really is.

</DL>

<HR>
Go to the <A HREF="xconq_1.html">first</A>, <A HREF="xconq_57.html">previous</A>, <A HREF="xconq_59.html">next</A>, <A HREF="xconq_66.html">last</A> section, <A HREF="xconq_toc.html">table of contents</A>.
</BODY>
</HTML>