RE: [NetEpic ML] Titan CC

From: Karlsen Rune <rune.karlsen_at_...>
Date: Mon, 17 Apr 2000 08:43:53 +0200

            The titan would still be able to fire its weaponry right? No
matter if it's on FF or AF?
            I think titans should be able to do that at charging units
(unless charged by another
            titan or praetorian, it would have to be on FF to shoot at
these).
            If the charging units win CC, it results in a damage roll,
right? It's not removed
            automatically?
 
            Rune

-----Original Message-----
From: Peter Ramos [mailto:pramos2_at_...]
Sent: 2000-04-15 01:29
To: netepic_at_egroups.com
Subject: Re: [NetEpic ML] Titan CC


Hi!
 
Hmm.... this may generate a lot of rolls, though and the present system
isn't very good since it doesn't fit too well with what we got. I think most
agree it needs changing, the question is what.
 
I am slowly warming to the idea of increased titan CAF's because:
 
1. Its the simplest thing, NO new rules what so ever, no special exceptions
and of course fits with standard rules because ot is the standard rule.
2. Titans would be very strong in close combat, but not invincible. You can
swarm, but you need to swarm with good troops not cannon fooder. Its more of
a tactical decision this way. Also they are finally set apart from all units
in virtue of their CAF, doesn't it bother anyone that a warhound has a CAF
of 8? It IS a titan after all
3. Casualties are already taken out in the standard close ombat with NO
extra rolls
 
I reallly cant see any downside to this. It only requires a minor edit to
the rules, more importanly, it doesn;t need to much playtest, we already
know the standard rules work. Those who have played the game for a while can
easily extrapolate the impact of higher CAF's.
 
Since I got time to kill lets take a look at this.
 
Current rules
 
10 guardsmen swarm one warlord, the warlord with average rolls averages 21 (
a CAF of 14 + 7 on a 2d6).
 
With average rolls the IG have met the average by stand 5 or 6, beyond that
the titan is pretty much toast.
 
Increased CAF
 
In the same example, but with a warlord with an increased CAF at +28, its
average is 35. The IG only meet the average at stand 9 or 10, an even match,
they never get a "sure thing". Of course if the warlord takes close combat
weapons then the IG have not much of a chance.
 
This makes several "good" tactical situations. If players want to take on a
titan they need to compromise better troops and thus more points. Also, it
makes close combat weapons valuable since that extra edge may keep most
opponents away from exercising this options since the odds would be steep.
 
Of course the amount of space to contact the titan is limited and thus their
is usually no more space to accomodate more troops at one go.
 
Of course I'm only doubling the CAF's it could be slightly higher. Some
recommended values could be:
 
+18 for scout class smaller titans
+28 for reaver sized titans
+35 for warlords with gargants having a little more
+50 for the big boyz like the Imperator and mega-gargant, also this means we
can get rid of those fiddly rules regarding infantry and attacking these big
things.
 
Peter

I've thought long and hard about this Titan CC issue, and came to this,
instead of making a bunch of new rules why not? Just use normal rule we
already have for Titan defence, but instead of making this an auto hit let
the Titan make a save when fighting Infantry/ veichals, modifyed by the
models CAF.
 
Example: Titan is attacked by 10 assult marines rolls two 6s so two hits on
the Titan, pick location or roll (I like the roll idea unless you play like
we do where you may only pick from the front) The Titan makes a save roll
mod by attackers CAF in this case 3. So the Titan need to roll 4or under to
exscape damage from the attack. This will show the Titan to be very strong
but not totally invincable to infantry.

  _____

 <http://click.egroups.com/1/2982/3/_/7255/_/955755033/>
  <http://adimg.egroups.com/img/2982/3/_/7255/_/955755033/468x60.gif>

  _____
Received on Mon Apr 17 2000 - 06:43:53 UTC

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