Re: does the tutorial lie?

[Eric McDonald <mcdonald@phy.cmich.edu>]

On Thu, 2004-05-27 at 18:48, mskala@ansuz.sooke.bc.ca wrote:
> I have not specifically tried the case you're talking about, but a couple
> thoughts: First of all, the tutorial probably *does* lie.  So does most of
> the rest of the documentation.  I've written things that the documentation
> said would work, and had them not work, quite often.  You have to solve
> these things by experiment, and preferably report it so the documentation
> and/or code can be fixed.

I'm not going to sit here and get defensive about the manuals since I
didn't write them, and have certainly been frustrated by them a number
times as well.

However, I am not sure that it is fitting to describe the manuals as
"lying". I doubt that Stan wrote them with an intent to deceive. Rather,
it seems that features and code changes have accumulated over time, and
those that added the features or made the changes didn't bother to
document their work in a way that was accessible to users or game
designers. So, I would say that they are outdated but not intentionally
deceiving. I suppose this might be an issue of semantics though.

I think a valid question is: should they be marked as such on the Xconq
Web site? These manuals also do contain up-to-date information, so maybe
they should simply have a caveat lector note next to their links.

> On your specific problem, I imagine that it's probably a zone of control
> issue.  I've faced something similar in one of my projects.  Units exert a
> zone of control that by default covers their entire hex, and units from
> enemy sides cannot enter that zone without attacking and defeating the
> controlling unit.  Look up zone of control (ZOC) in the manual, and try
> changing the zoc-range table to -1 for rubble piles versus all units.

I believe that is what Stan was just suggesting. Alternatively, one
might also be able to adjust the 'mp-to-enter-zoc' and 'mp-to-leave-zoc'
tables to make the ZOC non-blocking.

Eric