RE: [FT PBeM] question
From: "Bell, Brian K" <Brian_Bell@d...>
Date: Wed, 16 Feb 2000 12:23:40 -0500
Subject: RE: [FT PBeM] question
Seems complicated for a PBeM game.
This would mean that you have 4 reports per turn.
1. After Fighter and Ship movement.
2. After Intercepts and non-intercepted 2nd movement.
3. After Interception by fighters that did not move.
4. Damage Report.
Step 3 still leaves you with the "what if the target
I am trying to intercept moves out of range" problem.
I would suggest 4 types of movement for fighters:
1. Screen Ship (moves with ship) must be within 6tu.
2. Shadow Ship (moves with ship) must be within 6tu.
3. Move to X,Y coordinates (or move Xtu on course Y).
4. Intercept target. If using initiative, the
fighters must win initiative to intercept.
If the target wins initiative, and moves out
of range, it is safe. The fighters end their
movement at max movement on a course that is
on a direct line from the fighter's starting
point and ends at the target's ending point.
Intercepting fighters may declare if they
are willing to spend endurance to reach the
target when orders are written.
All movement orders would be written at the same time
ship movement is written.
-----
Brian Bell
bkb@beol.net
-----
> -----Original Message-----
> From: Roger Books [SMTP:books@mail.state.fl.us]
> Sent: Wednesday, February 16, 2000 11:08 AM
> To: gzg-l@CSUA.Berkeley.EDU
> Subject: Re: [FT PBeM] question
>
>
> We've decided to deal with fighter movement in the following manner.
>
> Fighters and ships move as per normal. After movement intercepts
> occur, any fighter group may declare an intercept if within 6 MU
> or may burn an endurance and declare an intercept if within 12.
>
> Non-intercepted fighters may move their 6/12 inches, this one is
> plotted with ftmap.
>
> fighters that did not move may now declare intercepts which are
> done before moving fighters do combat. 6/12 rules same as before.
>
> Sound reasonable?
>
> The one weakness would be multiple intercepts, but we'll just do
> a furball for that.
>
> Roger