RE: [NetEpic ML] More brainstorming

From: Peter Ramos <primarch_at_...>
Date: Wed, 28 Mar 2001 12:43:53 -0400

Hi!

Hi guys,

More views from your local E40K heretic.. I mean list observer ;)

Aha! An admitted heretic, you shall be punished!

I have to agree here. Maybe Eldar titans would be agile enough, but if
an
Imperial titan tried to "Stomp" some infantry they'd have plenty of time
to
re-locate and get out of the way. Its a bit like the attack of the
killer
slugs.
"RUN!! They're coming!!"
.......long pause......
"They're still coming!"
........long pause.......
"They're Sti.... Ah Hell - anyone fancy a drink down the pub whilst we
wait
for them?"

I'd prefer to see it go with the bolter arrays but I guess you could put
in
a generic attack to represent either bolter fire OR "Stomping". The
actual
events taking place would be decided by the player depending on their
own
iews and which titan is being used I suppose.

You may get your wish. Although being the way we are we might adopt both
and see what testing determines.

>
> as for the 6 stands... I can live with that, I suppose.. .though
> logically it doesnt make any sense.
>
> "ok, sarge, you take those 30 men and attack it, then when you die
> I'll take my 30 men and attack it. It'll never expect us to charge in
> easily killable waves"
>

Only 6 stands able to attack does make sense to me. No matter how many
men
you have piling in against the war machine, there's only going to be so
many
that can actually make contact with it to do any damage. If you had one
infantry command stand / character and your opponent wanted to charge a
whole company of cheap infantry against it would you not complain saying
only 4 of those could make it into combat?

I agree. The space is limited to engage the titan. One net epic rule was
all units needed to engage the leg, while skimmers and units with jump
packs could engage the base. Units like gargants are in for a bad day
though.

Peter
Received on Wed Mar 28 2001 - 16:43:53 UTC

This archive was generated by hypermail 2.3.0 : Tue Oct 22 2019 - 10:59:33 UTC