In a message dated 12/5/01 5:21:36 PM Eastern Standard Time, pbmnoot@yahoo.ca
writes:
GSI then
changed
> the code to disallow an 870 to any hex that was above 12 hexes from
> EITHER the starting hex or the hex in which the army, navy, or
> company ended its movement.
which would mean that I CAN move because the navy STARTS in a hex
that is within 12 of the target hex.
> So now the target hex must be within 12
> of both or the 870 order fails.
You used "OR" above, and now you say "BOTH", which implies "AND"
should have been used above...
My destination hex IS within 1 OR the other, but NOT within
1 AND the other...
Thanks for the response, but could yourself/anyone else please
clarify?
Based on the "confusing" statement: if the destination hex is more than 12
hexes from the origin hex OR more than 12 hexes from the hex the
army/navy/company ends its movement, the 870 order will fail.
Not sure I see where the confusion arises ...
- Dilip
[Non-text portions of this message have been removed]
Based on the "confusing" statement: if the destination hex is more
than 12
hexes from the origin hex OR more than 12 hexes from the hex the
army/navy/company ends its movement, the 870 order will fail.
Not sure I see where the confusion arises ...
- Dilip
I see I've gotten my "ands" and "ors" confused here. I had a
snotty reply all prepared until I went over it slowly...hmmm.
So, in order to:
Leave one army and then
Move to another hex where there is an army and then
Join that army
In this case at least, I am forced to use 2 orders:
Either:
Leave army and Move-Join
or
Move Character and then Join Army next turn.
Okay. I got it. At first, you see, I thought I was getting
ripped off by the game because if I could 810 BEFORE moving
with a navy, then I should bloody well be able to 870 before
moving with the same navy, no? Just a character moving 12
hexes and saying "Commander Loser Reporting Sir", right? But
now I can appreciate the finely balanced nuances built into the
order sequence......damn it.....
