The patch I just checked in documents the order of indices
for the mp-to-{enter,leave,traverse}-zoc tables, which was
unclear. If you want to describe the movement costs
associated with unit foo moving through the ZOC of unit bar,
you need to set the entry (foo bar), not the entry (bar foo),
even though (bar foo) would be the correct order of indices
for the zoc-range table when setting the size of bar's ZOC as
applied to foo. It would arguably be better to use the same
order of indexes for all four tables, but I was inclined to just
document it rather than changing it, because some existing
games depend on the current behaviour.
However: the online help indexes the mp-to- tables the same
way it indexes the zoc-range table, and produces confusing
text as a result. A fix could either consist of changing the
online help code to use the order of indexes used
everywhere else, or changing the order of indexes (in the
kernel, the documentation, and the library games) to be more
intuitive and match the online help code. The latter might be
nicer, but would be more work.
Logged In: YES
user_id=1158352
I would probably vote for the latter. Maybe I'll fix it when
I get around to working on the movement and pathfinding
code. You're welcome to take care of it before then.